The TSM scheduler writes to the following log files in /var/log (unless the variable DSM_LOG is set at run time to specify an alternative location). Each holds information going back for the last 30 days.

  • dsmsched.log - the log for all information about scheduled backups. This file lists the details of each file processed during a scheduled backup, summary results, and the time of the next scheduled backup (which it checks every twelve hours).
  • dsmerror.log - this file lists any errors encountered during manual or scheduled backups.

Once the TSM scheduler has been started, it will then contact the TSM server for the next schedule window and count down to that. If the next schedule window is more than twelve hours away then the scheduler will contact the HFS server again after that period has elapsed. You can check that the scheduler is running by examining the latest entry in dsmsched.log. It should look similar to the output shown below.

03-12-2013 08:19:13 --- SCHEDULEREC QUERY BEGIN
03-12-2013 08:19:13 --- SCHEDULEREC QUERY END
03-12-2013 08:19:13 Next operation scheduled:
03-12-2013 08:19:13 ------------------------------------------------------------
03-12-2013 08:19:13 Schedule Name:         WEEKDAILY_ITSERV
03-12-2013 08:19:13 Action:                Incremental
03-12-2013 08:19:13 Objects:
03-12-2013 08:19:13 Options:
03-12-2013 08:19:13 Server Window Start:   00:00:00 on 04-12-2013
03-12-2013 08:19:13 ------------------------------------------------------------
03-12-2013 08:19:13 Schedule will be refreshed in 12 hours.

These lines show a connection to a TSM server and a query for the next scheduled backup window.

If dsmsched.log is not present, or no new entries have still appeared, but at least two minutes have now passed since you started the TSM scheduler service, run the following on the command line:

ps -ef | grep 'dsmc sched'

If a TSM scheduler is running then you will see output that includes a line like the following:

root     30122     1  0 15:06 ?        00:00:00 /opt/tivoli/tsm/client/ba/bin/dsmc sched

If the terminal returns you to a prompt without listing any dsmc sched service, then you do not have a TSM scheduler running. In this case please see our page on setting up a new TSM scheduler on Linux.