Here is what the documentation says, It's long, happy reading!:

When a server is lost due to a hard disk failure or disaster, the server
object can be replaced by ADSM backup data during the NetWare installation
process by restoring the server specific information resource via ADSM.
Ensure that the server specific information is being backed-up on regular
basis. The server specific information will be backed-up on NetWare 4.11
servers as part of the incremental backup process if the ALL-LOCAL domain is
specified in the ADSM options file, dsm.opt. If the ALL-LOCAL domain is
specified, the incremental process will always backup the server specific
information first, before the SYS: volume. Server specific information can
also be explicitly specified in the domain statement: DOMAIN ALL-LOCAL
(implicit) DOMAIN SERVERSPECIFICINFO (explicit)
You can also selectively backup the server specific information with the
command: LOAD DSMC SELECTIVE SERVERSPECICINFO
You can verify that the server specific information is backed-up by querying
the node's filespaces from the admin or backup client: there should be a
filespace called servername\SERVERSPECIFICINFO associated with the node.
To restore a server which has failed with server specific information
available:
        After the server failure, restore the server specific information to
another server.
                You will need to restore the server specific information to
another location so that it can be used during the server installation
process.
                For example, you have two NetWare servers, SERVER-A and
SERVER-B. SERVER-A experiences a failure and must be restored. You will
restore the server specific information of SERVER-A onto SERVER-B by issuing
the following command from SERVER-B: LOAD DSMC RESTORE
SERVER-A/SERVERSPECIFCINFO SERVER-B/SERVERSPECIFICINFO -REPLACE=YES
                The server specific information for SERVER-A will be restore
to the following location: SERVER-B/SYS:\SYSTEM\SERVER-A
                Note: if the NetWare server name being restore is greater
then eight characters, the directory name created during the server specific
information restore will be truncated to eight characters.
                The following files will be restored during the server
specific information restore:
                SERVDATA.NDS - this file contains the information needed by
the NetWare installation procedure to restore the server object to its
original state.
                DSMISC.LOG - a text file containing various NDS information,
including the server's replica list.
                VOLSINFO.TXT - a text file which contains the full server
name (i.e., if the directory name had been truncated), a list of volumes
present on the server at the time of the last server specific information
backup, the name spaces and extend file formats (e.g., compression) enabled
on the volumes. This file is meant to aid the user during server recovery.
                AUTOEXEC.NCF - the server's autoexec.ncf file.
                STARTUP.NCF - the server's startup.ncf file.
        Re-install the NetWare 4.11 operating system on the failed server.
                You must specify the same FILE SERVER NAME and the same IPX
INTERNAL NET number if you wish to recover the server object properly. This
information can be found in the failed server's autoexec.ncf file, which is
restored with the server specific information (see point above). Follow the
NetWare installation instructions until you are prompted to install NDS.
        Restore the NDS server object from the backup copy.
                At the point where the NetWare installation asks you to "...
choose a directory tree which you want this server to be installed", follow
these steps:
*       Press F5 to Restore NDS
*       Press F3 to specify the path to restore the DS backup file,
SERVDATA.NDS.
*       Specify the path where the server specific information was restore.
In our previous example, the path is: SERVER-B/SYS:\SYSTEM\SERVER-A
After restoring the server object back into the NDS, you can proceed to
restore the rest of the operating system from backup; you will not need to
copy the rest of the files normally copied during the install process.
Please refer to NDS Restore Considerations for more information about
restoring the NetWare servers and NDS in their entireties.


__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / ADSM
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

        -----Original Message-----
        From:   Tom Haddad [SMTP:thaddad AT COLUMBIAENERGYGROUP DOT COM]
        Sent:   Thursday, September 09, 1999 12:29 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Netware client 3.1.0.7 and CLlENT OPTION SETs

        I tested a scheduled backup on a Netware v5 client with ADSM client
level
        3.1.0.7 and using a CLIENT OPTION SET.. All worked successfully. I
was viewing
        the DSMSCHED.LOG for any newer messages and noticed one entry.
Before the
        volume backup began, the first logged entry was


        09/09/1999 00:12:01 Incremental backup of volume 'SRVCHASNW5\SERVER
SPECIFIC
        INFO'
        09/09/1999 00:12:01 Normal File-->         1,048,576 Server Specific
        Info/Server Specific Info [Sent]
        09/09/1999 00:13:45 Successful incremental backup of
'SRVCHASNW5\SERVER
        SPECIFIC INFO'

        Was does this indicate?? Is it server data/info unique to Netware
version 5?


        Also, if I make a change to the CLIENT OPT SET, will the next
scheduled backup
        talk to the ADSM server and load the new option set?
        (since the schedule is inititated by the server, PROMPTED)..