Anonymous_User Absent Member.
Absent Member.
1449 views

"Recovering" from a catastrophic loss of the iFolder Server

Has anyone out there tested this information from the iFolder 3
Documentation?

->->

Use your normal file system backup procedures to back up the following
data:

* Simias store directory
The default location is /var/opt/novell/ifolder3/simias.

* Simias configuration file
The default locations are
/var/lib/wwwrun/.local/share/simias/Simias.config or
/home/wwwrun/.local/share/simias/Simias.config

7.8 Recovering from a Catastrophic Loss of the iFolder Server

If the iFolder server configuration or data store becomes corrupted, use
your iFolder backup files to restore the database to its last good backup.
Restoring the iFolder server to the state it was in at the time of the
backup also reverts the iFolders on any connected iFolder clients to that
same state.

IMPORTANT:All changes made since the time of the backup will be lost on all
connected clients.

Consider the following implications of restoring iFolder data:

* Any new file or directory is deleted if it was added to an iFolder
since the time of the backup.
* Any file that was modified is reverted to its state at the time of the
backup.
* Any file or directory is restored if it was deleted since the time of
the backup.

Before restoring the iFolder server, consider notifying all users to save
copies of any files or directories they might have modified in their
iFolders since the time of the last backup. After the iFolder server is
restored, they can copy these files or directories back into their
respective iFolders

1. Notify users to save copies of iFolders or files that have changed
since the time of the backup you plan to use for the restore.

2. Stop the iFolder server by entering the following command as root
user:

/etc/init.d/apache2 stop

3. Remove the following corrupted data:
* Simias store directory

The default location is /var/opt/novell/ifolder3/simias.
* Simias configuration file

The default locations are
/var/lib/wwwrun/.local/share/simias/Simias.config or
/home/wwwrun/.local/share/simias/Simias.config.

4. Use your normal file system restore procedures to restore the
following data to its original locations:
* Simias store directory

The default location is /var/opt/novell/ifolder3/simias.
* Simias configuration file

The default locations are
/var/lib/wwwrun/.local/share/simias/Simias.config or
/home/wwwrun/.local/share/simias/Simias.config.

5. Delete all files in the Simias log directory.

The default location is /var/opt/novell/ifolder3/simias/log/*.

IMPORTANT:Be careful not to modify anything else under the Simias
store directory.

6. Start the iFolder server by entering the following command as root
user:

/etc/init.d/apache2 start

<-<-

I just went through this procedure in a test environment and it does NOT
work. After backing up the proper files, corrupting the system, restoring
the files and deleting the old log files per the documentation, you still
can not connect via the client or the web portal. The only difference is my
simias dir is located under /ifolder/data/ which is a valid location per the
installation documentation. Running OES (Linux) sp2 and iFolder 3.2.5347.1
Did I miss something or is there another step that is not included in the
documentation?
Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: "Recovering" from a catastrophic loss of the iFolder Server

Ben,

It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at http://support.novell.com in both the "free product support" and "paid product support" drop down boxes.
- You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)

If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Recovering" from a catastrophic loss of the iFolder Server

Ben Lewis wrote:

> Has anyone out there tested this information from the iFolder 3
> Documentation?


Actually, I have not - but can try it out later in the week. I just got
iFolder 3 working on my OES server, and I'm the only user on it thus far 🙂
- so it will be rather easy and painless for me to try it. I can back it
up, just change one file, and see what happens. It will probably be a bit
later today or even later in the week before I can get to this though!

Danita


--
Danita Zanre
Novell Support Forums Volunteer
GroupWise 7 Upgrade Guide!
www.caledonia.net/gw7upg.html
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Recovering" from a catastrophic loss of the iFolder Server

That would be great. Let me know what you find out. I actually have a support incident open on this, and the Novell guy says he got it to work. Thus far, I've been unsuccessful, but I'm thinking it may be a rights issue.......

Ben
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.