Checking the TSM scheduler
Check the Spectrum Protect / TSM scheduler is running on your machine
The TSM scheduler writes to the following log files, each holding 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, which should look similar to the output shown below.
For Windows systems, the TSM scheduler writes log files to C:\Program Files\tivoli\tsm\baclient.
20-07-2011 16:32:07 TSM Backup-Archive Client Version 6, Release 1, Level 2.0 20-07-2011 16:32:07 Querying server for next scheduled event. 20-07-2011 16:32:07 Node Name: JASON-WIN7.OUCS 20-07-2011 16:32:07 Session established with server OX_HFS_B1: AIX 20-07-2011 16:32:07 Server version 6, Release 2, Level 2.30 20-07-2011 16:32:07 Server date/time: 20-07-2011 16:32:07 Last access: 20-07-2011 16:32:03 20-07-2011 16:32:07 --- SCHEDULEREC QUERY BEGIN 20-07-2011 16:32:07 --- SCHEDULEREC QUERY END 20-07-2011 16:32:07 Next operation scheduled: 20-07-2011 16:32:07 ------------------------------------------------------------ 20-07-2011 16:32:07 Schedule Name: WEEKLY_18_00 20-07-2011 16:32:07 Action: Incremental 20-07-2011 16:32:07 Objects: 20-07-2011 16:32:07 Options: 20-07-2011 16:32:07 Server Window Start: 18:00:00 on 21-07-2011 20-07-2011 16:32:07 ------------------------------------------------------------ 20-07-2011 16:32:07 Schedule will be refreshed in 3 hours.
These lines show a connection to a TSM server and a query for the next scheduled backup window.
To check the status of the service, select the Windows Start menu, type Services, run the Services app, then locate the TSM Client Scheduler in the list of services.
To start or restart an existing scheduler service, highlight TSM Client Scheduler in the list, right clicking on it and select Start or Restart.
For Mac systems, the TSM scheduler writes log files to /Library/Logs/tivoli/tsm.
03-12-2013 09:54:48 Schedule will be refreshed in 12 hours. 03-12-2013 09:54:48 TSM Backup-Archive Client Version 6, Release 1, Level 0.2 03-12-2013 09:54:48 Querying server for next scheduled event. 03-12-2013 09:54:48 Node Name: TESTMAC.OUCS 03-12-2013 09:54:48 Session established with server OX_HFS_B3: AIX-RS/6000 03-12-2013 09:54:48 Server version 5, Release 5, Level 1.1 03-12-2013 09:54:48 Server date/time: 03-12-2013 09:54:48 Last access: 03-12-2013 09:53:57 03-12-2013 09:54:48 --- SCHEDULEREC QUERY BEGIN 03-12-2013 09:54:48 --- SCHEDULEREC QUERY END 03-12-2013 09:54:48 Next operation scheduled: 03-12-2013 09:54:48 ------------------------------------------------------------ 03-12-2013 09:54:48 Schedule Name: WEEKLY_23_45 03-12-2013 09:54:48 Action: Incremental 03-12-2013 09:54:48 Objects: 03-12-2013 09:54:48 Options: 03-12-2013 09:54:48 Server Window Start: 23:45:00 on 09-12-2009 03-12-2013 09:54:48 ------------------------------------------------------------ 03-12-2013 09:54:48 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 Applications > Utilities > Terminal and provide the following text:
ps -ef | grep 'dsmc sched'
If a TSM scheduler is running then you will see output that includes a line like the following:
0 5508 1 0 2:40pm ?? 0:00.13 /usr/bin/dsmc sched
If the terminal returns you to a prompt without listing any /usr/bin/dsmc sched service, then you do not have a TSM scheduler running. In this case please see our page on Restarting the TSM scheduler.
For Linux systems, the TSM scheduler writes log files to /var/log (unless the variable DSM_LOG is set at run time to specify an alternative location).
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.
For Solaris systems, the TSM scheduler writes log files to /var/log (unless the variable DSM_LOG is set at run time to specify an alternative location).
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 Restarting the TSM scheduler.
Get support
If you cannot find the solution you need here then we have other ways to get IT support