Tivoli Header
Tivoli Storage Manager for NetWare Backup-Archive Client Installation and User's Guide
You can use this example in a situation in which the SYS volume
(or entire server) is lost but replicas of all partitions which were present
on the failed server exist on other servers. You can also use this
example when a failed SYS volume (or entire server) contains no NDS
replications.
In this example, you must restore NDS objects which referenced the failed
Server object and failed Volume object(s), as well as the volume data
(including trustee data). Perform the following steps to ensure
recovery:
- If the failed server contains any Master partitions, reassign the master
to another server using the DSREPAIR utility.
- Replace the failed hard disk(s).
- 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:
- Use the same server name in the install
- Use the same admin parent container and password as the last NDS
backup.
- Ensure all hard disk partitions are at least as large as they were on the
failed server.
- Use the same volume names as on the failed server.
- 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.
- 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).
- 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.
- 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)
- The following steps are necessary if the server specific information was
not restored from a backup:
- Delete any objects which had server specific references. See Server Centric IDs for more information about objects which reference the
server object.
- 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 directory -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.
- 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.
- Verify restoration of the NDS, file data, and trustee data.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]