![]() |
![]() |
To automate client operations, you can define new schedules. To later modify, copy, and delete these schedules, see Chapter 17, Managing Schedules for Client Nodes.
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 |
---|---|
Create client schedules for any policy domain | System or unrestricted policy |
Create client schedules for specific policy domains | System, unrestricted policy, or restricted policy for those domains |
Key information to have when scheduling operations are:
Tivoli Storage Manager provides two sample schedules: one for daily backups and one for weekly backups. The sample schedules use defaults for many of their values. You can copy and modify them to create customized schedules that meet your requirements.
Administrators can follow these steps to create schedules for client node operations. To later modify, copy, and delete these schedules, see Chapter 17, Managing Schedules for Client Nodes.
As an alternative to using the TSM Console, you can define and associate schedules by using the Tivoli Storage Manager command line interface or the administrative Web interface. Commands used for defining schedules are listed under Commands for Scheduling Client Operations.
To tailor the parameters you choose when you create your schedules, 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 must be associated with schedules before they can use the Tivoli Storage Manager 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:
The dialog displays defined schedules in the left pane and a listing of all registered client nodes in the right pane.
Figure 54. Scheduling Wizard Displaying All Schedules and Registered Client Nodes
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