User manual NOVELL IFOLDER 3 ADMINISTRATION

[. . . ] Novell iFolder 3. x Administration Guide novdocx (ENU) 01 February 2006 Novell iFolder 3. x August 15, 2006 ® www. novell. com ADMINISTRATION GUIDE novdocx (ENU) 01 February 2006 Legal Notices Novell, Inc. , makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. , makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. [. . . ] This does not work with TSAIF because iFolder puts files in a SimiasFiles directory. -r, --restore-to="backup_path new_path" Restores by replacing backup_path with new_path. This does not work with TSAIF because iFolder puts files in a SimiasFiles directory. If TSAIF cannot back up or restore a file, it skips the file and returns a warning. When this occurs, nbackup(1) creates a file with a . warn extension that contains a list of each file that was skipped along with the date and time it was skipped and the error code that was returned. If files are skipped, try to resolve the issue, then run the operation again. If you are unable to identify why the file was skipped, try running the operation again when the server is less busy. If files are skipped during a restore, and if relatively few files are skipped, try individually restoring each skipped file. 7. 6. 8 TSAIF and NBackup Examples The following examples show how to perform typical TSAIF backup and restore operations using NBackup. Managing an iFolder Enterprise Server 75 novdocx (ENU) 01 February 2006 Backup or Restore Task Command Full backup Full restore Owner backup Owner restore nbackup -cvf full. sidf -U root -P password --target-type=ifolder / nbackup -xvf full. sidf -U root -P password --target-type=ifolder nbackup -cvf owner. sidf -U root -P password --target-type=ifolder /owner nbackup -xvf owner. sidf -U root -P password --target-type=ifolder nbackup -xvf full. sidf -U root -P password --target-type=ifolder --extract-dir=/owner iFolder backup iFolder restore nbackup -cvf ifolder. sidf -U root -P password --target-type=ifolder /owner/collection nbackup -xvf ifolder. sidf -U root -P password --target-type=ifolder nbackup -xvf owner. sidf -U root -P password --target-type=ifolder --extract-dir=/owner/collection nbackup -xvf full. sidf -U root -P password --target-type=ifolder --extract-dir=/owner/collection If you are restoring an entire iFolder and want to ensure that it is in the exact state it was in when it was backed up, you should first delete the current iFolder from the server using a client or the iFolder 3 plug-in for iManager. Deleting the iFolder is not necessary to restore any or all of the files in the iFolder; the difference is in what metadata is given preference during the restore. If you do not delete the iFolder before restoring, the attributes of the iFolder, such as the owner, members, file type or size restrictions, remain as they are in the current version. Subdirectory restore nbackup -xvf ifolder. sidf -U root -P password --target-type=ifolder --extract-dir=/owner/collection/relative-path nbackup -xvf owner. sidf -U root -P password --target-type=ifolder --extract-dir=/owner/collection/relative-path nbackup -xvf full. sidf -U root -P 7. 6. 9 Additional Information For more information about backup, see the following man pages on your iFolder enterprise server: nbackup(1), sms(7), smdrd(8), smsconfig(1), tsaif. conf(5). 76 Novell iFolder 3. x Administration Guide novdocx (ENU) 01 February 2006 7. 7 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. 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 Managing an iFolder Enterprise Server 77 novdocx (ENU) 01 February 2006 7 Notify users that they can return their saved files to their iFolders for upload to the server. Users should coordinate this with other members of the iFolder to avoid competing updates. 7. 8 Recovering Individual Files or Directories 1 Collect information that uniquely identifies the file or directory to be recovered, such as a combination of the following: · iFolder name, such as MyiFolder · iFolder owner · iFolder member list · Relative path of the file or directory, such as /MyDir1/MyDir2/myfile. txt · Time stamp or approximate time of the version desired · Other files or directories in the iFolder 2 Open a Web browser to iManager, then log in with your Admin username and password. [. . . ] It explains how to tune the cluster unload script to allow enough time to gracefully break connections with users. 142 Novell iFolder 3. x Administration Guide novdocx (ENU) 01 February 2006 E. 1. 5 Managing the SSL Certificate for the Apache Web Server The following change was made to this section: Location Change Section C. 1, "Generating an YaST contains modules for the basic management of X. 509 certificates. SSL Certificate for the This mainly involves the creation of CAs, sub-CAs, and their certificates. Server, " on page 133 For more information about how to manage and update certificates, see Managing X. 509 Certification (http://www. novell. com/documentation/ sles10/sles_admin/data/cha_yast_ca. html) in the SUSE Linux Enterprise Server 10 Installation and Administration Guide (http://www. novell. com/ documentation/sles10/sles_admin/data/bookinfo_book_sles_admin. html). E. 1. 6 Product History The following change was made to this section: Location Change Section D. 4, "Workstation Operating Systems Support for the iFolder Client, " on page 138 The iFolder 3. 4 client was released only for the SUSE Linux Enterprise Desktop 10 operating system. It is compatible with Novell iFolder 3. 2 servers. E. 2 May 24, 2006 Updates were made to the following section. [. . . ]