2. Running Scheduled Backups

In order to run automatic scheduled backups unattended the TSM password, the Netware password to login to the NDS tree and the Netware password to login to the Server need to be stored encrypted locally on the disk. The procedure for ensuring this is detailed in the instructions for installing and running the HFS TSM Client for Netware. If you can run the queries detailed in that section without being prompted for a TSM or Netware password, then these passwords have been correctly stored in encrypted form to disk.

To run the TSM Scheduler simply run the following:


After a small delay, the TSM Scheduler will have written an entry in the dsmsched.log file similar to below.

These lines show a connection to a TSM server and a query for the next scheduled backup window. If there are lines similar to "ANS1029E Communications have been dropped" then it is likely that either the node name and/or the password have been incorrectly entered or the password has expired. You will need to start the TSM client (LOAD DSMC) manually and enter the correct password, or obtain a new password from IT Services Registration if yours has expired, before restarting the TSM Scheduler. Further help on reasons for the TSM Scheduler failing to start can be found by examining the dsmerror.log file.

The TSM Scheduler will start at a time within its allotted schedule window overnight and report the results in the schedule log dsmsched.log. This should be examined as described in the Checking the Scheduled Backups section.

The TSM Scheduler process will not stop once a scheduled backup has been performed but will continue to count down to the next schedule window. To stop it, just run:


Note that IBM recommend that clients restart the scheduler periodically to free system resources previously used by system calls.

Up: Contents Previous: 1. Introduction Next: 3. Checking the Scheduled Backups