Tivoli Header

Tivoli Storage Manager for NetWare Backup-Archive Client Installation and User's Guide

Example 2c Multiple-Server Network (Replica not present)

This example can be used in a situation in which the SYS volume (or entire server) is lost and partitions contained on the server were not replicated. In this example, you must restore any partitions that were not replicated, NDS objects which referenced the failed Server object and failed Volume object(s), and the volume data (including trustee data). The following steps are necessary for recovery:

  1. If the failed server contains any Master partitions which was replicated, reassign the master to another server using the DSREPAIR utility.
  2. Replace the failed hard disk(s).
  3. Reinstall the NetWare OS and NDS on the server. If a backup copy of the server specific information is available, install the NetWare OS. See Server Specific Information for more information. If a backup copy of the server specific information is not available, use the NWCONFIG.NLM utility on NetWare, with the following precautions:
  4. Ensure that the NetWare OS has the correct patches for Tivoli Storage Manager to function properly. Refer to the client readme.1st file shipped with the Tivoli Storage Manager client for more information about dependencies on NetWare OS patches.
  5. If the server had volumes other then SYS, and these volumes were not affected by the failure, run DSREPAIR to purge the file system of invalid trustees on those volumes. This step cleans-up the volume DETs and FETs so that the trustee assignments can be restored correctly. At the server console, LOAD DSREPAIR and choose the Unattended Full Repair option. (This automatically purges invalid trustee assignments).
  6. Install Tivoli Storage Manager and reestablish the communications protocol. Use the NWCONFIG.NLM utility to reinstall the Tivoli Storage Manager code on the NetWare server. Reconfigure the communications protocol so that the Tivoli Storage Manager client can communicate with the Tivoli Storage Manager server.
  7. Load the necessary SMS target service agents. At the target NetWare server console enter:
    load tsands
    load tsa500 (NetWare 5)  or
    load tsa600 (NetWare 6)
    
  8. Delete any objects which had server specific references. See Server Centric IDs for more information about objects which reference the server object.
  9. Restore the replicas. You can do this by issuing a restore at the replica root. For example, if the replica root was:
    OU=Islands.O=Greece
    

    you must issue the command:

    load dsmc restore nds:/.o=greece/.ou=islands.o=greece -replace=yes 
    

    Since this is a partial restore, you may decide to restore the entire NDS by entering the following command at the NetWare console:

    load dsmc restore nds -replace=yes
    

    This eliminates the need for the next step while ensuring a consistent restore of the NDS tree. See Object References for more details about partial restore limitations.

  10. Replace the objects which contained references to the failed Server and Volume objects. You can do this by restoring the entire NDS using the following command at the NetWare console:
    load dsmc restore nds -replace=yes
    

    The -replace=yes option ensures that place-holders created by the restore process are properly replaced by real NDS objects. If you are not comfortable with replacing the entire NDS, you can selectively restore each object or manually recreate the objects with NWADMIN or NETADMIN.

  11. Restore the volume(s) using Tivoli Storage Manager. Use the following NetWare console command for each volume you want to restore:
    load dsmc restore sys:\* -subdir=yes -replace=all -volinfo
    

    Where SYS: is the name of the failed volume.

  12. Verify restoration of the NDS, file data, and trustee data.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]