29. KBNTW0001 - Scheduled backups fail due to failure to connect to the NDS

Summary This article will guide you through what to do if TSM for NetWare scheduled backups fail due to failure to connect to the NDS.
Symptom TSM for NetWare scheduled backups fail due to failure to connect to the NDS.
Cause Possible Cause - If a NetWare machine appears to be failing its backup due to a failure to connect to the NDS, then it is possible that the TSM and NetWare ids and passwords that are stored encrypted on disk have failed in some way.
Resolution The easiest solution is to refresh and re-encrypt them in the following manner:
  1. Unload any dsmcad.nlm module loaded.
  2. Close / unload any TSM session open.
  3. Delete all .PWD files in the TSM installation directory.
  4. Reset the TSM and Netware ID's and passwords by starting a new TSM session and running the three queries detailed in section 3 of Running the TSM client for Netware.
  5. Reload the DSMCAD.NLM module, wait until it connects to the TSM server, then examine the latest entry in the dsmsched.log file.
  6. Re-examine the dsmsched.log file after the next overnight scheduled backup to ensure that it was successful.
Status
More Information
Applies To TSM

Up: Contents Previous: 28. KBNIX0007 - "ANS2600S Browser trying to establish connection to client; received socket exception; java.net.ConnectException: Connection refused" (GUI) and/or "/opt/tivoli/tsm/client/ba/bin/dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory" (command line) Next: 30. KBGEN0001 - ANS2622S An invalid ID or password was submitted.