An ADSM administrator can set up schedules to perform ADSM tasks automatically. Central scheduling is a cooperative effort between the server and your client node. An ADSM administrator sets up central scheduling on the server, and you are responsible for starting the client scheduler on your client node. After you start the client scheduler, no further intervention is necessary.
You must have the ADSM command-line client installed in order to start the client scheduler. You cannot start the client scheduler from the ADSM graphical user interface.
You can also:
To start the client scheduler, you issue the dsmc SCHEDULE command. You can choose to start the client scheduler when you start your operating system, or start it at any other appropriate time.
When you issue the dsmc SCHEDULE command, it starts the client scheduler, which runs continuously until you close the window in which you initiated the command, kill the process, or log out of your system.
To run the SCHEDULE command in the background and to keep the client scheduler running even if you log out of your system, you can enter the SCHEDULE command as follows:
nohup dsmc schedule 2> /dev/null &
If an ADSM password is required for your workstation and you want to run the SCHEDULE command in the background, you must supply the password with the command.
ROOT USER
If you want to start the client scheduler when you start your operating system, ensure that the PASSWORDACCESS option is set to GENERATE in your client system options file, and include one of the following commands in the /etc/inittab file:
adsm::once:/usr/lpp/adsm/bin/dsmc sched > /dev/null 2>&1 # ADSM scheduler
adsm::once:/usr/opt/adsm/dsmc sched > /dev/null 2>&1 # ADSM scheduler
adsm::once:/usr/bin/dsmc sched > /dev/null 2>&1 # ADSM scheduler
adsm::once:/usr/adsm/dsmc sched > /dev/null 2>&1 # ADSM scheduler
| Note: | You must include the redirection to /dev/null in the
command. The scheduler must be started through the /etc/inittab file on
any operating system. Another startup, for example through
/sbin/rc2.d/xxx, is not possible.
ADSM does not recognize changes to the dsm.opt or dsm.sys files while the client scheduler is running. If you make changes to those files while the client scheduler is running, and you want ADSM to begin using the new values immediately, you must stop the client scheduler and then restart it. For example, if you change the INCLEXCL option in your dsm.sys file to point to a different include-exclude options file, you must stop the client scheduler, and then restart it before ADSM can begin using the new file you specified. |
To manually stop the client scheduler, use the KILL command if it is running in the background, or use Ctrl+C if it is running in the foreground. To restart the client scheduler, reissue the SCHEDULE command.
| Note: | Tape prompting does not occur during a scheduled operation regardless of the setting for the TAPEPROMPT option in your client user options file. |
To see what schedules are defined for your client node, use the QUERY SCHEDULE command:
dsmc query schedule
ADSM displays detailed information about all scheduled work for your client node.
Figure 2 shows sample QUERY SCHEDULE output.
Figure 2. 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: /proj
Priority: 1
Next Execution: 60 minutes
Duration: 8 Hours
Period: 7 Days
Day of Week: Friday
Expire: Never
|
The schedule named DAILY_INC starts an incremental backup every day. The next incremental backup is due to 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 named WEEKLY_INC starts an incremental backup in the /proj file system every Friday.
When you run the SCHEDULE command in the foreground, output from scheduled commands appears on your screen. It is also directed to a file called dsmsched.log in the current directory unless you change the path and file name using the SCHEDLOGNAME option. When you run SCHEDULE in the background, output is directed to dsmsched.log in the current directory or to the path and file name you specified.
After scheduled work is performed, you can check the schedule log to find out whether all work completed successfully.
The schedule log continues to grow unless you prune it using the SCHEDLOGRETENTION option. See "Specifying Scheduling Options" for more information.
You can modify scheduling options in the client system options file if you do not like the current values.
For more detailed information about each scheduling option, see Chapter 6. "Setting Common Options".
The following options determine how the scheduler runs on your workstation.
If your administrator specifies values for these options, those values override what you have in the client system options file.
If you use the client-polling mode (see "SCHEDMODE"), you can set the maximum number of hours the client scheduler waits between attempts to contact the server for scheduled work.
In the following example, the client scheduler waits for 5 hours:
queryschedperiod=5
Use this option to indicate the maximum number of times the client scheduler can retry a scheduled command that fails.
In the following example, the client scheduler tries 3 times:
maxcmdretries=3
Use this option to set the number of minutes the client scheduler must wait between retry attempts for a scheduled command that fails or unsuccessful attempts to contact the server.
In the following example, the client scheduler waits for 15 minutes:
retryperiod=15
Use this option to specify where you want ADSM to store the schedule log. The default is the current directory with a file name of dsmsched.log.
In the following example, ADSM puts the log in the /etc directory with a file name log.info:
schedlogname /etc/log.info
Use this option to set the number of days to keep log file entries from the schedule log before pruning it, and whether to save pruned entries.
In the following example, ADSM keeps entries for 7 days, and then prunes them and discards the pruned entries:
schedlogretention 7,D
The following options change the scheduling mode, TCP/IP address, or TCP/IP port number.
Use this option to indicate whether you want to use the client-polling mode or the server-prompted mode.
In the client-polling mode, the client scheduler queries the server for scheduled work at prescribed time intervals. This is the default schedule mode.
In the server-prompted mode, the client scheduler waits for the server to contact your client node when scheduled work needs to be done. This mode provides an ADSM administrator with more control and flexibility in processing scheduled work. For example, if you normally run a scheduled, system-wide incremental backup in the evening, but your host system is scheduled to be down for maintenance work, your ADSM administrator can choose to initiate a backup at an earlier time.
Your administrator can specify that either mode is supported by the server, or only one mode is supported. If your administrator specifies only one mode, you must specify that same mode in your client system options file. Otherwise, scheduled work is not processed.
In the following example, the mode is polling:
schedmode polling
Use this option to specify a TCP/IP address if your client node has more than one address, and you want the server to contact a different address than the one used to make initial contact with the server.
You can use this option only if you are using the server-prompted schedule mode.
In the following example, the address is dsclnt.sanjose.ibm.com:
tcpclientaddress dsclnt.sanjose.ibm.com
Use this option if you are using the server-prompted schedule mode. You can specify a TCP/IP port number if you want the server to use a different port than the one used to make initial contact with the server.
If the default or specified port is busy, ADSM attempts to use any other available port.
In the following example, the port number is 1503:
tcpclientport 1503
The following options let you run commands before and after a schedule.
Use this option to run a command before the schedule runs. For example, use PRESCHEDULECMD to quiesce a database before starting a schedule that runs an incremental backup of the database. Then, use POSTSCHEDULECMD to restart the database.
Use this option to run a command after running a schedule. For example, after the schedule runs, use a post-schedule command that runs an exec to scan the schedule log and send the results to your administrator.