|
Should TSA's be loaded on my NetWare* 4.x server[s]?
Yes.
There are two TSA NLMs that need to be loaded for proper file backup and one TSA NLM that needs to be loaded to back up the NDS.
TSANDS.NLM
TSANDS.NLM allows access to the NetWare NDS for backup. Only load this NLM on the Master NDS server. When this NLM is loaded, the StorageExpress™ system is able to backup information in the servers NDS Tree.
A StorageExpress system running Central Console is only able to perform complete backups/restores of the NDS Tree, and will automatically attempt to do so if TSANDS.NLM is loaded. A StorageExpress system running ARCserve* 6.x for NetWare is capable of partial or full backups/restores of the NDS Tree. Neither versions of software will backup partition information.
TSA4xx.NLM and SMDR.NLM:
TSA4xx.NLM is the Target Service Agent which is responsible for the maintenance of the file trustee and object ID information. The object ID links the file to the NetWare file system and the NDS. When the TSA4xx.NLM is loaded, the backup removes the old object ID and backs up only the file. When the file is restored, the TSA creates a new object ID for the file and links it to the file system and NDS.
SMDR is the Storage Management Data Requester. It provides transparent communication between local and remote SMS modules via RPC's (Remote Procedure Calls). In short, SMDR on the StorageExpress system talks to SMDR on the remote target. In turn, SMDR's talk to the TSA's.
If TSA and SMS are not loaded during the backup, the object ID is backed up with the file. When that file is restored the old object ID is also restored. What you end up with is a file that you cannot access because the file system and NDS is not aware it. This is because it does not have a valid object ID.
Note: Make sure that you are loading the updated versions of the TSA modules on the target NetWare 4.x servers and the StorageExpress system. The latest versions of patches for NetWare* servers can be found at Novell's Patch List
†.
What to copy for NetWare 4.1x targets:
| TSA410.NLM |
TO |
SYS:\SYSTEM |
| TSANDS.NLM |
TO |
SYS:\SYSTEM |
| SMDR.NLM |
TO |
SYS:\SYSTEM |
| TSA410.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
| TSANDS.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
| SMDR.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
What to copy for NetWare 4.0x targets:
| TSA400.NLM |
TO |
SYS:\SYSTEM |
| TSANDS.NLM |
TO |
SYS:\SYSTEM |
| SMDR.NLM |
TO |
SYS:\SYSTEM |
| TSA400.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
| TSANDS.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
| SMDR.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
|
What to copy for NetWare 3.12 targets:
| TSA312.NLM |
TO |
SYS:\SYSTEM |
| SMDR.NLM |
TO |
SYS:\SYSTEM |
| TSA312.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
| SMDR.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
What to copy for NetWare 3.11 targets:
| TSA311.NLM |
TO |
SYS:\SYSTEM |
| SMDR.NLM |
TO |
SYS:\SYSTEM |
| SMDR.MSG |
TO |
SYS:\SYSTEM\NLS\4 |
What else is needed to properly backup my NetWare 4.x server[s]?
The following is the proper user setup for backing up a NetWare server and its NDS from the StorageExpress system.
- A backup user must be created as an NDS user object and must exist in the same container as the target server.
- In order to backup the NDS properly, the backup user should be made a trustee of the [Root] object with the Supervisor Object Right. For fault tolerance reasons, it is preferable not to create the backup user as an Admin equivalent. (i.e.:If the Admin object becomes unusable, so have your Admin equivalents.)
- The target server must have Bindery Context set to the container it resides in. Note: In order to set Bindery Context make sure there is a read/write replica of the NDS on the target server.
For more information on backing up and restoring NetWare* 4.x servers, refer to the October 1996 Novell* Research Application Notes. These can be found on the Novell Support Connection CD.
† This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.
This applies to:
| 
