This section shows how to start TSM schedules that you have defined and how to verify that they are running correctly.
You must start the scheduler on each client node that is scheduled for TSM operations:
Install the Tivoli Storage Manager Scheduler on each client or agent for which you want to schedule TSM operations. The Scheduler runs as a Windows service and is installed with a program named DSMCUTIL in the Windows NT backup-archive client directory. The following example assumes that you have installed the backup-archive client on your machine in the directory: c:\program files\tivoli\tsm\baclient.
Click on the Command Prompt icon to open a window and do the following:
cd "c:\program files\tivoli\tsm\baclient" dsmcutil list
If you receive a message stating that the client services registry key could not be opened or that scheduler services were not located, the scheduling service is not installed.
Note: | You must abbreviate any directory names with spaces using the Windows short name, as shown in the following example. |
To install the scheduler service, issue the following commands:
dsmcutil inst /name:"TSM Scheduler" /node:client /password:client /clientdir:d:\progra&similar.1\tivoli\tsm\baclient
where the node and password are the installation defaults: client. You can replace these with a registered node name and password. The node name is the one to be associated with a defined schedule.
net start "TSM Scheduler"
Issue the following command from an operating system command line:
dsmc schedule
![]() | To help ensure that the scheduler is running, the clients should include the SCHEDULE command in their system start-up commands. |
You can verify that the automation is working as it should on the day after you define the schedule and associate it with clients. If the schedule runs successfully, the status indicates Completed.
Note: | The include-exclude list (file on UNIX clients) on each client also affects which files are backed up or archived by the two schedules defined in the preceding steps. For example, if a file is excluded from backup with an EXCLUDE statement, the file will not be backed up when the schedule runs. |
From the administrative Web interface, do the following:
Schedules that did not complete successfully have a status of Failed, Missed, or Severed.
Check the results of the schedule on one of the clients that was associated with that schedule. For most clients, scheduling information is stored in the file dsmsched.log.