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 scheduled backup method recommended by OUCS is to run the Client Acceptor Daemon (CAD) to manage the TSM client scheduler. Managing the TSM client scheduler this way has the following benefits:

  • 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.

To run the CAD, check that the file /opt/tivoli/tsm/client/ba/bin/dsm.sys contains the line 

  ManagedServices    Schedule
adding it to the end of the file if necessary.

1.1. inittab method

If your flavour of Unix employs the /etc/inittab file to launch processes at system startup then you can add a line similar to one below: 

  dc:2:once:/usr/bin/dsmcad > /dev/null 2>&1			# run dsmcad wrapper for TSM scheduler

Then run the following command as the root user. 

  /usr/bin/dsmcad > /dev/null 2>&1	# for Bourne-like shells
  /usr/bin/dsmcad >& /dev/null 		# for C-like shells

1.2. SysV init scripts (/etc/init.d or /etc/rc.d) method

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 /opt/tivoli/tsm/client/ba/bin/ called dsmcad-init This script includes the appropriate headers for addition via specific tools on some systems.

1.2.1. SuSE 10, Fedora Core and Redhat-Based systems

To install the TSM scheduler on SuSE 10, Fedora Core and Redhat-Based systems:

  1. Copy dsmcad-init to /etc/init.d

  2. Ensure script is executable with: chmod 755 /etc/init.d/dsmcad-init

  3. Add script to system start up with: /sbin/chkconfig --add dsmcad-init

  4. Check script with: /sbin/chkconfig --list dsmcad-init

  5. Reboot box to check execution or start with /etc/init.d/dsmcad-init start

To remove the TSM scheduler:

  1. /sbin/chkconfig --del dsmcad-init

  2. Remove dsmcad-init from /etc/init.d/

1.2.2. Debian-based systems

To install the TSM scheduler on Debian systems (on Ubuntu remember to preface the commands with sudo) :

  1. Copy dsmcad-init to /etc/init.d

  2. Ensure script is executable with: chmod 755 /etc/init.d/dsmcad-init

  3. Add script to system start up with: update-rc.d dsmcad-init defaults 95 05

  4. Start the service with: invoke-rc.d dsmcad-init start

To remove the TSM scheduler:

  1. Remove dsmcad-init from /etc/init.d/

  2. update-rc.d dsmcad-init remove

1.2.3. Solaris 8/9, other Linux distributions, and other UNIX systems using SysV init scripts

To install the TSM scheduler on Solaris 8/9, and other UNIX systems/Linux distributions using SysV init scripts (/etc/init.d or /etc/rc.d):

  1. Copy dsmcad-init to /etc/init.d

  2. Ensure script is executable with: chmod 755 /etc/init.d/dsmcad-init

  3. 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
(NB: Some of the above links will not apply on some systems)
To remove the TSM scheduler:

  1. Remove dsmcad-init from /etc/init.d/

  2. Remove dsmcad-init symlinks from /etc/rc{0,1,2,3,4,5,6,S}.d/

1.3. Log files

The CAD and TSM scheduler write to the following log files in /var/log (unless the variable DSM_LOG is set at run time to specify an alternative location):

  • 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

You can check that the CAD is managing the scheduler by examining the latest entry in the dsmwebcl.log file. It should look similar to below.

Note that there is a Schedule Name - usually starting WEEKLY_ or WEEKDAILY_ followed by a shortened department or college name. The latest entries will look similar to below.

Note that the last line 'Scheduler has been stopped' is normal and refers to the TSM scheduler being managed (stopped and started) by the CAD.

Up: Contents Next: 2. Checking the Scheduled Backups

Sections in this document: