![]() |
![]() |
To automate client operations, you can define new schedules. To later modify, copy, and delete these schedules, see Chapter 13, Managing Schedules for Client Nodes.
When you define a schedule, you assign it to a specific policy domain. You can define more than one schedule for each policy domain.
To set up a client schedule on the server, perform these steps:
The following sections describe how to automate a basic client operation, incremental backup.
Task | Required Privilege Class |
---|---|
Define client schedules for any policy domain | System or unrestricted policy |
Define client schedules for specific policy domains | System, unrestricted policy, or restricted policy for those domains |
Key information to have when scheduling operations are:
To define a schedule for daily incremental backups, use the DEFINE SCHEDULE command. You must specify the policy domain to which the schedule belongs and the name of the schedule (the policy domain must already be defined). For example:
define schedule engpoldom daily_backup starttime=21:00 duration=2 durunits=hours
This command results in the following:
To change the defaults, see the DEFINE SCHEDULE command in the Administrator's Reference.
Task | Required Privilege Class |
---|---|
Associate client nodes with schedules | System, unrestricted policy, or restricted policy for the policy domain to which the schedule belongs |
Client nodes process operations according to the schedules associated with the nodes. To associate client nodes with a schedule, use the DEFINE ASSOCIATION command. A client node can be associated with more than one schedule. However, a node must be assigned to the policy domain to which a schedule belongs.
After a client schedule is defined, you can associate client nodes with it by identifying the following information:
To associate the ENGNODE client node with the WEEKLY_BACKUP schedule, both of which belong to the ENGPOLDOM policy domain, enter:
define association engpoldom weekly_backup engnode
The client scheduler must be started before work scheduled by the administrator can be initiated. Administrators must ensure that users start the Tivoli Storage Manager Scheduler on the client or application client directory, and that the scheduler is running at the schedule start time. After the client scheduler starts, it continues to run and initiates scheduled events until it is stopped.
The way that users start the Tivoli Storage Manager Scheduler varies, depending on the operating system that the machine is running. The user can choose to start the client scheduler automatically when the operating system is started, or can start it manually at any time. The user can also have the client acceptor manage the scheduler, starting the scheduler only when needed. For instructions on these tasks, see Backup-Archive Installation and User's Guide and the appropriate client user's guide.
Task | Required Privilege Class |
---|---|
Display information about scheduled operations | Any administrator |
You can display information about schedules and whether the schedules ran successfully.
When you request information about schedules, the server displays the following information:
The following 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 | | | +--------------------------------------------------------------------------------+
For Tivoli Storage Manager, a schedule completes successfully as long as the command associated with the schedule is successfully issued. The success of the issued command is independent of the success of the schedule.
For example, you can issue the following command to find out which events were missed (did not start) 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.
The schedule log is a file that contains information such as the statistics about the backed-up objects, the name of the server backing up the objects, and the time and date of the next scheduled operation. By default, Tivoli Storage Manager stores the schedule log as a file called dsmsched.log and places the file in the directory where the Tivoli Storage Manager backup-archive client is installed. See the client user's guide for more information.
Search or query the activity log for related messages. For example, search for messages that mention the client node name, within the time period that the schedule ran. For example:
query actlog begindate=02/23/2001 enddate=02/26/2001 originator=client nodename=hermione