User Guide

Overview 37
Storage Management Services Administration Guide
103-000134-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
5. Restore the file system. (See “Restoring Data” on page 62 and “Custom
File System Restore” on page 74.)
6. Restore any replicas that were removed from the server.
Loss of the Entire eDirectory Tree
If all servers on a network are destroyed because of a disaster, you must
perform a complete restore of NetWare, eDirectory, and file system data.
IMPORTANT: We recommend that you document your eDirectory tree structure;
the location of Server objects, partitions, and replicas; and record bindery context
settings and other relevant information.
Use the following general steps to restore the eDirectory tree structure:
1. Repair or replace the failed hardware.
2. Reinstall NetWare on the first server.
3. Install NetWare on remaining servers to create a skeleton of the tree.
4. Restore eDirectory. (See “Restoring eDirectory” on page 69.)
5. Restore the file system to all servers. (See “Custom File System Restore”
on page 74.)
6. Re-establish partition boundaries and distribute replicas.
Restoring Cluster-enabled Pools
Restore of cluster-enabled pools is similar to a normal restore session (see
“Restoring Data” on page 62.)
NOTE: Auto recovery of the restore session on failover or failback is currently not
supported.
Session Files
Whenever you back up or restore files/directories, a log and corresponding
error files are created for that particular session on the server on which you are
executing the job. The .LOG file is the session file for that particular job.
The need to create a session file arises when you are restoring the data on a
server other than the one you backed up from. The server should possess the
session ID of all the jobs that are present on the tape so that the SME can
restore it. These session IDs are created from the .LOG files. See “Creating
Session Files” on page 98.