Administrators can follow these steps to create schedules for client node operations. To later modify, copy, and delete these schedules, see Chapter 14, Managing Scheduling Operations for Client Nodes.
Hint: As an alternative to using the TSM Server Utilities, you can define and associate schedules by using the TSM command line interface or the administrative Web interface. Commands used for defining schedules are listed under Scheduling Tivoli Storage Manager Commands.
To tailor your parameters you choose when you create your schedules, see the DEFINE SCHEDULE command in the Administrator's Reference.
Client nodes must be associated with schedules before they can use the TSM Scheduler. You can associate client nodes with schedules using the scheduling wizard. An individual node can be associated with more than one schedule. To associate the client nodes with a schedule:
Figure 47. Scheduling Wizard Displaying All Registered Schedules and Client Nodes
Figure 48. Scheduling Wizard Displaying node CLIENT Associated with the DAILY_INCR Schedule
The client scheduler must be started before work scheduled by the administrator can be initiated. Administrators must ensure that users start the TSM Scheduler on the client, application client, or Tivoli Data Protection host server directory and that the scheduler is running at the schedule start time. After the client node starts the client scheduler, it continues to run and initiates scheduled events until it is stopped.
Note: | TSM does not recognize changes made to the client option files while the scheduler is running. If you make changes to these files while the scheduler is running, and you want TSM to use these new values immediately, stop the scheduler and restart it. |
The way users start the TSM Scheduler can be different, depending upon the platform on which the machine is running.
Starting the TSM Scheduler on Windows NT or Windows 2000
net start "TSM Scheduler"
Starting the TSM Scheduler on Windows 95/98
> dsmc schedule
Application clients and Tivoli Data Protection host servers require schedules that can run command files. The command files, also known as a macros or batch files on other operating systems, contain sequences of commands that are run at a scheduled start date and time. The default schedules are not set up to support command files.
To use command files, administrators must create schedules with the DEFINE SCHEDULE command using the ACTION=COMMAND parameter. For example, by using the DEFINE SCHEDULE command, you can define a schedule called daily_incr that will process a command file with any set of commands you choose. For example:
define schedule standard daily_incr description="daily incremental file" action=command objects="c:\incr.cmd" starttime=18:00 duration=5 durunits=minutes period=1 preunits=day dayofweek=any
Assuming that the scheduler is started on the client, application client or Tivoli Data Protection host server directory, the schedule runs the file called c:\incr.cmd once a day at 6:00 pm, any day of the week.
You can verify the status of scheduled operations by displaying scheduling information. This includes information about schedules and information about scheduled operations called events. You can check whether the schedule ran successfully by using the QUERY EVENT command.
When you request information about schedules, the server displays the following information:
The following sample output shows an example of a report that is displayed after you enter:
query schedule engpoldom
+--------------------------------------------------------------------------------+ |Domain * Schedule Name Action Start Date/Time Duration Period Day | |------------ - ---------------- ------ -------------------- -------- ------ --- | |ENGPOLDOM MONTHLY_BACKUP Inc Bk 07/21/1998 12:45:14 2 H 2 Mo Sat | |ENGPOLDOM WEEKLY_BACKUP Inc Bk 07/21/1998 12:46:21 4 H 1 W Sat | | | +--------------------------------------------------------------------------------+
A scheduled client operation, called an event, is tracked by the server. You can get information about projected and actual scheduled processes by using a general query. You can get information about scheduled processes that did not complete successfully by using exception reporting.
For example, you can issue the following command to find out which events were missed in the ENGPOLDOM policy domain for the WEEKLY_BACKUP schedule in the previous week:
query event engpoldom weekly_backup begindate=-7 begintime=now enddate=today endtime=now exceptionsonly=yes
For more information about managing event records, see Managing Event Records.