User Guide

28 Storage Management Services Administration Guide
Storage Management Services Administration Guide
103-000134-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
Trustee Assignments
Trustee assignments are stored as part of the file system as an ID. They are
backed up by default when the file system is backed up with the SMS TSA
software. If a User object is deleted and then re-created or restored, its object
ID changes. This is why the SMS TSA module uses fully distinguished names
for objects to back up the trustee rights from the file system. If a User object
is deleted and re-created with a new ID, the user's trustee assignments in the
file system can be restored.
As long as an object with the same name on the backup media exists in the
eDirectory tree structure when the file system is restored, the TSA can interact
with eDirectory to rebuild the directory entry table (DET) to reflect new object
ID numbers.
For additional information about object ID and trustee issues, see “Restoring
eDirectory” on page 69.
Server-Specific Information
Server-specific information such as the replica information, ID information,
name spaces loaded, and system configuration is stored on the volume SYS:.
This information is backed up as part of the file system as a single resource.
This resource includes the following five files:
SERVDATA.NDS contains server-specific eDirectory data.
DSMISC.LOG contains a replica list and replica types on the server at
backup.
STARTUP.NCF contains a disk driver, name spaces, and SET
parameters.
AUTOEXEC.NCF contains load modules and the NetWare operating
system configuration.
VOL$INFO.TXT contains volumes on the server, name spaces loaded,
compression, and migration information.
You can also choose to back up this information individually. The information
is not restored unless you specifically choose to restore it. It does not need to
be restored unless you have lost the SYS: volume. In that case, you must
replace the hardware and restore this information. For more information, see
“Restoring the Entire eDirectory Tree Structure” on page 72.