Tivoli Storage Manager for Windows Administrator's Guide


Creating Tivoli Storage Manager Schedules

Administrators can follow these steps to create schedules for client node operations. To later modify, copy, and delete these schedules, see Chapter 14, Managing Scheduling Operations for Client Nodes.

  1. Double-click the TSM Server Utilities icon on the server desktop. The TSM Server Utilities appear.
  2. Click the Scheduler Configuration in the TSM Server Utilities tree. The TSM Scheduler view appears in the right pane.
  3. Click the Start button. The Scheduling Wizard appears.
  4. Follow the instructions in the wizard. When the Define schedules and associate nodes with them dialog appears, click the Add button. The Add Schedules dialog appears. TSM provides two sample schedules: one for daily backups and one for weekly backups. The sample schedules use TSM defaults for many of their values. You can copy and modify them to create customized schedules for own requirements.

Hint: As an alternative to using the TSM Server Utilities, you can define and associate schedules by using the TSM command line interface or the administrative Web interface. Commands used for defining schedules are listed under Scheduling Tivoli Storage Manager Commands.

To tailor your parameters you choose when you create your schedules, see the DEFINE SCHEDULE command in the Administrator's Reference.

Associating Client Nodes with Schedules

Client nodes must be associated with schedules before they can use the TSM 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:

  1. Double-click the TSM Server Utilities icon on the server desktop. The TSM Server Utilities appear.
  2. Click the Scheduler Configuration in the TSM Server Utilities tree view. The Scheduler Configuration view appears.
  3. Navigate to the Define schedules and associate nodes with them dialog, shown in Figure 47. The dialog appears with All Nodes highlighted in the left pane and a listing of all registered client nodes in the right pane. All Nodes is not a schedule; it is a view of all registered nodes.

    Figure 47. Scheduling Wizard Displaying All Registered Schedules and Client Nodes

    Scheduling Wizard Displaying All Registered Schedules and Client Nodes

  4. Click All Nodes in the left pane. All registered client nodes appear in the right pane.
  5. Click a schedule in the left pane. All client nodes associated with the schedule appear in the right pane.
  6. With All Nodes selected, drag and drop a client node (right pane) onto a schedule (left pane). For example, if you want to associate the CLIENT node with the DAILY_INCR schedule, drag and drop the client node onto the DAILY_INCR schedule. The node that you drop on a schedule is associated with the schedule. You do not see the effect of the drag and drop until you select the schedule on which you dropped the node. See Figure 48.

    Figure 48. Scheduling Wizard Displaying node CLIENT Associated with the DAILY_INCR Schedule

    Scheduling Wizard Displaying node CLIENT Associated with the DAILY_INCR Schedule

  7. Click the schedule on which you dropped the node. The associated node appears in the right pane.

Starting the Scheduler

The client scheduler must be started before work scheduled by the administrator can be initiated. Administrators must ensure that users start the TSM Scheduler on the client, application client, or Tivoli Data Protection host server directory and that the scheduler is running at the schedule start time. After the client node starts the client scheduler, it continues to run and initiates scheduled events until it is stopped.

Note:TSM does not recognize changes made to the client option files while the scheduler is running. If you make changes to these files while the scheduler is running, and you want TSM to use these new values immediately, stop the scheduler and restart it.

The way users start the TSM Scheduler can be different, depending upon the platform on which the machine is running.

Starting the TSM Scheduler on Windows NT or Windows 2000

  1. Click Start>Command Prompt. The Command Prompt dialog appears.
  2. Enter the following command at the Command Prompt.
    net start "TSM Scheduler"
    

Starting the TSM Scheduler on Windows 95/98

  1. Click Start>Programs> Tivoli>TSM Command Line. The TSM Backup dialog appears.
  2. Enter the following command at the dsmc> command prompt.
    > dsmc schedule
    

Creating Command Files to Run on Schedules

Application clients and Tivoli Data Protection host servers require schedules that can run command files. The command files, also known as a macros or batch files on other operating systems, contain sequences of commands that are run at a scheduled start date and time. The default schedules are not set up to support command files.

To use command files, administrators must create schedules with the DEFINE SCHEDULE command using the ACTION=COMMAND parameter. For example, by using the DEFINE SCHEDULE command, you can define a schedule called daily_incr that will process a command file with any set of commands you choose. For example:

define schedule standard daily_incr description="daily incremental file" 
action=command objects="c:\incr.cmd" starttime=18:00 duration=5 
durunits=minutes period=1 preunits=day dayofweek=any 

Assuming that the scheduler is started on the client, application client or Tivoli Data Protection host server directory, the schedule runs the file called c:\incr.cmd once a day at 6:00 pm, any day of the week.

Displaying Scheduling Information

You can verify the status of scheduled operations by displaying scheduling information. This includes information about schedules and information about scheduled operations called events. You can check whether the schedule ran successfully by using the QUERY EVENT command.

When you request information about schedules, the server displays the following information:

The following sample 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 |
|                                                                                |
+--------------------------------------------------------------------------------+

Checking whether the Schedule Completed Successfully

A scheduled client operation, called an event, is tracked by the server. You can get information about projected and actual scheduled processes by using a general query. You can get information about scheduled processes that did not complete successfully by using exception reporting.

For example, you can issue the following command to find out which events were missed 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.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]