Central scheduling is a procedure your administrator defines to automatically process ADSM tasks. The administrator associates clients with one or more schedules which are part of the policy domain maintained in the ADSM database. The schedule start time is based on the server clock, not the workstation clock.
Start the client scheduler on your workstation to connect you to the schedule on the server. An ADSM administrator sets up central scheduling on the server, and you start the client scheduler on your node. After you start the client scheduler, further intervention is not necessary.
With client scheduling, you can also:
| Note: | Install the ADSM command-line client to use the client scheduler. |
Windows 95: Enter the schedule command to start the client scheduler on your client node:
dsmc schedule
You can also include the schedule command in your startup folder so that every time you start Windows, the client scheduler starts. When you start the client scheduler, it runs continuously and processes scheduled events until you close the window, end the process, or log off your system.
Windows NT: Use the central scheduling service.
Tape prompting does not occur during a scheduled event regardless of the setting for the tapeprompt option in your options file.
| Note: | The ADSM command-line client must be installed, and the communication software must be running before you start the client scheduler. |
Use the query schedule command to determine what schedules are defined for your client node:
dsmc query schedule
ADSM displays detailed information about all scheduled work for your client node. The figure below displays 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: e: f:
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, ADSM 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 e: and f: drives.
Windows 95: 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 current directory unless you change the path and file name with the schedlogname option.
Windows NT: When you run the schedule command as a service, output from scheduled commands displays in the Windows NT application event log. Output is also directed to the dsmsched.log file in the current directory unless you change the path and file name with the schedlogname option.
After scheduled work is performed, check the schedule log to ensure all work completed successfully. The schedule log continues to grow unless you prune it with the schedlogretention option. See "Specify Scheduling Options" for more information.
You can modify scheduling options in the client options file or in the graphical user interface if you do not like the values that are set. If your administrator specifies a value for these options, it overrides what you have in the client options file.
For more information about scheduling options, changing the scheduling mode, TCP/IP address or port number, or running commands before or after a schedule, see "Scheduling Options".