Checking the TSM scheduler

WINDOWS

In order for TSM to perform an automatic scheduled backup, the TSM scheduler must be running on the client machine during the allotted scheduled window.  By default, the TSM Scheduler is installed and set to run during the installation of the TSM software.  However, it may not be working as required for a number of reasons listed below.  This page will help you check the status of the Scheduler service and to troubleshoot some common causes for failure.

  • You have recently changed your TSM node's password and have not updated the TSM scheduler with this new password.
  • You have registered a new nodename for the machine, and updated TSM, but the scheduler is still using the old name.
  • The TSM client scheduler was not set up during the installation because the installer detected that a large amount of data was present, too much for a single backup session.
  • There was a problem during the installation and so the TSM scheduler was not installed correctly.

If your scheduled backups have worked in the past, then the latter two reasons are unlikely.

To view the status of your TSM scheduler, do as follows:

  1. From the Windows Start menu, select Windows Administrative ToolsServices
  2. Browse the list of services for any services beginning with TSM (they are listed in alphabetical order).
  3. Depending on the services which you find, please take the correct action, as listed below.  What you need to do depends on the version of TSM that you are running.
  • If only TSM Client Scheduler is listed then you have the correct TSM service running. Do as follows:
    • Check that the service is Started and that its startup type is set to Automatic, if neccessary double-click the service to fix the problem.  If the scheduler was not previously set to Automatic then the problem is now likely to have been fixed.  If the scheduler was stopped then please continue.
    • Browse to C:\Program Files\Tivoli\TSM\baclient, double-click on dsmerror.log and if you see the following message:
      T02-07-2010 10:09:38 ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE.

      This means that you will need to remove an old TSM setting as follows:

      1. In folder C:\Program Files\Tivoli\TSM\baclient, locate dsm.opt.
      2. To avoid file permission issues, drag dsm.opt to your desktop.
      3. Double-click on dsm.opt.
      4. If prompted for how to open the file, select Notepad.
      5. Check for a line that begins with MANAGEDSERVICES, if it exists delete the entire line.
      6. Save the file and close Notepad.
      7. Drag dsm.opt back to C:\Program Files\Tivoli\TSM\baclient.
  • If no TSM services are listed then this means that the scheduler was not installed or has been removed.  Follow these instructions to set up a new TSM scheduler service.
  • If both TSM Client Acceptor and TSM Client Scheduler are listed then you are probably running an old version of TSM.  Check the version that you are running by selecting Help > About TSM.
    • If it is TSM 5.4 or 5.5:
      • Upgrade to the most recent version of TSM.
      • If there is no current version of TSM for your version of Windows, check that the TSM client acceptor is Started and that its startup type is set to Automatic; the TSM client scheduler should be set to Stopped. Then follow the instructions to update an existing TSM scheduler.
    • If it is TSM 6.1:
      • Check the TSM configuration file for MANAGEDSERVICES, and remove it if present:
        1. In folder C:\Program Files\Tivoli\TSM\baclient, locate dsm.opt.
        2. To avoid file permission issues, drag dsm.opt to your desktop.
        3. Double-click on dsm.opt.
        4. If prompted for how to open the file, select Notepad.
        5. Check for a line that begins with MANAGEDSERVICES, if it exists delete the entire line.
        6. Save the file and close Notepad.
        7. Drag dsm.opt back to C:\Program Files\Tivoli\TSM\baclient.
      • Remove the current TSM services
        1. Download and run the TSM-Delete-Services file.
        2. When prompted, select Unzip.
        3. Follow the on-screen prompts.
        4. You will receive confirmation when the services have been removed.
        5. Now follow the instructions for setting up a new TSM Scheduler Service.

You should now have performed enough troubleshooting to ensure that you know why the scheduled backup was missed and hopefully put corrective measures in place to ensure subsequent scheduled backups are successful.  If you have been unable to determine the likely cause of why the backups are being missed then please follow these steps for Logging calls with the HFS Team with the appropriate amount of data.

If you have not already done so, we recommend that you run a manual backup.

To find out when your next scheduled backup is, please see the FAQ item When is my scheduled backup due to run?.

MACOS / OSX

The TSM scheduler writes to the following log files in /Library/Logs/tivoli/tsm.  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, which should look similar to the output shown below.

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 setting up a new TSM scheduler on the Mac.

LINUX

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.

SOLARIS

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

Get support


Local IT support provide your first line of on-the-spot help

FIND MY LOCAL IT TEAM

 

Common requests and fault reports can be logged using self-service

   USE IT SELF-SERVICE      

   LOG A SUPPORT CALL     

VIEW MY SUPPORT CALLS  

 

The central Service Desk is available 24x7 on +44 1865 6 12345 (check central IT support arrangements over Christmas)

 

If you do not have an SSO account you can use this form to contact the Service Desk