Your administrator can schedule TSM to perform tasks automatically on a regular basis. For example, you can automatically back up files at the end of each day, or archive some of your files every Friday. This procedure, known as central scheduling, is a cooperative effort between the server and your client node. Your administrator associates clients with one or more schedules that are part of the policy domain maintained in the database. The administrator defines central scheduling on the server, and you start the client scheduler on your workstation. Once you start the client scheduler, further intervention is not necessary.
Note: | The schedule start time is based on the server clock, not the workstation clock. |
Note: | Install the command line client and ensure the communication software is running before you start the client scheduler. |
You can modify scheduling options in the client options file or in the graphical user interface. However, if your administrator specifies a value for these options, that value overrides what you have in the client options file.
For more information about scheduling options, changing the scheduling mode, specifying the TCP/IP address or port number, or running commands before or after a schedule, see "Scheduling Options".
To start the client scheduler on your client node and connect to the server schedule, change to the TSM directory and enter the following command:
load dsmc schedule
When you start the client scheduler, it runs continuously until you close the window, end the process, log off your system, or enter this command at the NetWare console prompt:
unload dsmc
.
. You can also include the schedule command in your autoexec.ncf file so that every time you start NetWare, the client scheduler starts.
Tape prompting does not occur during a scheduled event regardless of the tapeprompt option setting in your options file.
To view schedules that are defined for your client node, enter:
load dsmc query schedule
TSM displays detailed information about all scheduled work for your client node. The figure below displays sample query schedule output.
Figure 1. Sample Query Schedule Output
Schedule Name: DAILY_INC Description: Daily System-wide backup Action: Incremental Options: QUIET Objects: Priority: 1 Next Execution: 30 minutes Duration: 4 Hours Period: 1 Day Day of Week: Any Expire: Never Schedule Name: WEEKLY_INC Description: Weekly backup for project files Action: Incremental Options: QUIET Objects: BINDERY SYS: Priority: 1 Next Execution: 60 minutes Duration: 8 Hours Period: 7 Days Day of Week: Friday Expire: Never |
The schedule name, DAILY_INC, starts a daily incremental backup. The next incremental backup will start in 30 minutes. Because no objects are listed, TSM runs the incremental backup on your default domain. The schedule has no expiration date.
The schedule name, WEEKLY_INC, starts a weekly incremental backup on the bindery and SYS: volumes.
When you run the schedule command in the foreground, output from scheduled commands displays on your screen. Output is also directed to the dsmsched.log file in the installation directory unless you change the directory and file name using the schedlogname option.
After scheduled work is performed, check the schedule log to verify that all work completed successfully.
When a scheduled command is processed the schedule log may contain the following entry:
Scheduled event eventname completed successfully
This is merely an indication that TSM successfully issued the scheduled command associated with the eventname. No attempt is made to determine the success or failure of the command. You should assess the status of the command by evaluating the return code from the scheduled command in the schedule log. The schedule log entry for the command's return code is prefaced with the following text:
Finished command. Return code is:
The schedule log continues to grow unless you prune it using the schedlogretention option. See "Specifying Scheduling Options" for more information.