Defining A Client Backup Schedule - IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

part is integrated into the Tivoli Storage Manager process and is responsible for
managing the schedules and notifying clients. The client scheduler is a separate
process on the Tivoli Storage Manager client and provides communication
between the server and client. See "Scheduling" in IBM Tivoli Storage
Management Concepts, SG24-4877, for further information about the client
portion of the client scheduling system.
A Tivoli Storage Manager client with an active scheduler process can be
scheduled to perform any of the following actions:
Back up (either incremental or selective)
Archive
Restore
Retrieve
External command or script
Macro
Image backup or restore (UNIX)
The most common use of client schedules is to for an automatic incremental
backup process for a group of machines.
At this point in the configuration of Tivoli Storage Manager, you should have
installed the Tivoli Storage Manager client software on your clients and defined
them to a policy domain. You should also have activated the scheduler service
on the client so that it is ready to accept schedules. The remaining activities are
performed on the server. To complete a client schedule you need to perform the
following operations on the server:
1. Define a client schedule.
2. Associate a client with the schedule.
3. Verify the client schedule.

12.3.1 Defining a client backup schedule

In 1.1.1, "Our support material" on page 5, we show how to load a predefined
macro into Tivoli Storage Manager. The macro mac.schedules, which we provide
to define schedules for our book environment, are shown in "Define schedules"
on page 735.
The define schedule command defines a schedule to the Tivoli Storage Manager
server. You then use the define association command to associate each client
with the schedule.
To define a client schedule, specify the following information:
Policy domain name: The schedule will be created within this policy domain
and can only be associated with nodes within that domain. Only
Chapter 12. Scheduling
387