1. Starting the TSM Scheduler
Running the TSM Scheduler requires that the TSM password has been stored encrypted on the local machine and so the TSM client must have authenticated to the TSM server before the scheduler is run. Additionally, it is strongly recommended that clients perform a full manual incremental backup of their local filestore before running the scheduler.
- The CAD launches the scheduler only when necessary.
- As a consequence of the above, client options and file excludes may be added without having to stop/restart the scheduler.
- The CAD is memory-light and therefore resolves the problem of running the memory-hungry TSM client scheduler permanently in the background.
ManagedServices Scheduleadding it to the end of the file if necessary.
dc:2:once:/usr/bin/dsmcad > /dev/null 2>&1 # run dsmcad wrapper for TSM scheduler
/usr/bin/dsmcad > /dev/null 2>&1 # for Bourne-like shells /usr/bin/dsmcad >& /dev/null # for C-like shells
For systems that start programs from init level command
files, it is simplest to add a command file that starts and stops the TSM
Scheduler at the appropriate run levels (2, 3, 4, 5).
To this end, OUCS includes a file in the directory
This script includes the appropriate headers for addition via specific tools on some systems.
- Add the following symlinks:
- /etc/rc0.d/K05dsmcad-init -> ../init.d/dsmcad-init
- /etc/rc1.d/K05dsmcad-init -> ../init.d/dsmcad-init
- /etc/rc6.d/K05dsmcad-init -> ../init.d/dsmcad-init
- /etc/rc2.d/S95dsmcad-init -> ../init.d/dsmcad-init
- /etc/rc3.d/S95dsmcad-init -> ../init.d/dsmcad-init
- /etc/rc4.d/S95dsmcad-init -> ../init.d/dsmcad-init
- /etc/rc5.d/S95dsmcad-init -> ../init.d/dsmcad-init
- /etc/rcS.d/K05dsmcad-init -> ../init.d/dsmcad-init
- dsmwebcl.log - the logfile of the CAD output.
- dsmsched.log - the log of the all scheduled backups. This file lists the details of each file processed in the most recent scheduled backups, the summary results of the most recent scheduled backups and the time of the next scheduled backup.
- dsmerror.log - lists any errors encountered in any manual or scheduled backup.
Once started, the TSM Scheduler will contact the TSM server for the next schedule window and count down to that. If the next schedule window is more than 24 hours away the process will count down for 24 hours and then re-contact the TSM server. This window can be checked manually by running the command:
dsmc query schedule