388
IBM Tivoli Storage Manager Implementation Guide
administrators who have policy rights for the domain or system rights can
control these schedules.
Schedule name: The schedule name can be any unique name you choose,
up to 30 characters long. It should represent the function it performs.
Start time: The time of day that you want the schedule to trigger your action.
Startup duration: The period in which the scheduler will initiate the schedule
after the start time.
Client schedules are very dependent on site requirements, but we have some
recommendations that are applicable for a wide range of environments.
Our recommended policy configuration includes two policy domains, one for
servers and one for workstations. We must therefore define a client backup
schedule for each domain. The parameters for each schedule are very similar
except for the domain name. The schedules start at 10 p.m. with a startup
window of three hours. The commands and output are shown in Example 12-14.
Example 12-14 Defining client schedules
tsm: LOCHNESS_SERVER1>
define schedule server server_nightly action=incremental
starttime=22:00 duration=3 durunits=hours period=1 perunits=days
description="Nightly backup schedule for SERVER domain"
ANR2500I Schedule SERVER_NIGHTLY defined in policy domain SERVER.
tsm: LOCHNESS_SERVER1>
define schedule workstn workstn_nightly action=incremental
starttime=22:00 duration=3 durunits=hours period=1 perunits=days
description="Nightly backup schedule for Workstation domain"
ANR2500I Schedule WORKSTN_NIGHTLY defined in policy domain WORKSTN.
tsm: LOCHNESS_SERVER1>
q sched
Domain
* Schedule
Name Action Start
Date/Time
Duration
Period
Day
------- - --------------- ------ -------------------
--------
------
---
SERVER
SERVER_NIGHTLY
Inc Bk 02/21/2006 22:00:00
3 H
1 D Any
WORKSTN
WORKSTN_NIGHTLY
Inc Bk 02/21/2006 22:00:00
3 H
1 D Any
Note that we do not specify a type or style of schedule. If we omit the type,
client
is assumed. If we omit the SCHEDStyle,
classic
is assumed.
12.3.2 Defining an enhanced client schedule
An enhanced client schedule performs the same actions as a classic client
schedule, but allows you to be more specific with repetition intervals.
Summary of Contents for E16RMLL-I - Tivoli Storage Manager
Page 2: ......
Page 23: ...Figures xxi 22 6 AIX lab environment 708...
Page 24: ...xxii IBM Tivoli Storage Manager Implementation Guide...
Page 32: ...2 IBM Tivoli Storage Manager Implementation Guide...
Page 44: ...14 IBM Tivoli Storage Manager Implementation Guide...
Page 94: ...64 IBM Tivoli Storage Manager Implementation Guide...
Page 96: ...66 IBM Tivoli Storage Manager Implementation Guide...
Page 126: ...96 IBM Tivoli Storage Manager Implementation Guide...
Page 298: ...268 IBM Tivoli Storage Manager Implementation Guide...
Page 354: ...324 IBM Tivoli Storage Manager Implementation Guide...
Page 356: ...326 IBM Tivoli Storage Manager Implementation Guide...
Page 423: ...Chapter 12 Scheduling 393 Week of Month Expire Never tsm quit...
Page 424: ...394 IBM Tivoli Storage Manager Implementation Guide...
Page 510: ...480 IBM Tivoli Storage Manager Implementation Guide...
Page 552: ...522 IBM Tivoli Storage Manager Implementation Guide...
Page 554: ...524 IBM Tivoli Storage Manager Implementation Guide...
Page 594: ...564 IBM Tivoli Storage Manager Implementation Guide...
Page 612: ...582 IBM Tivoli Storage Manager Implementation Guide...
Page 618: ...588 IBM Tivoli Storage Manager Implementation Guide...
Page 720: ...690 IBM Tivoli Storage Manager Implementation Guide...
Page 752: ...722 IBM Tivoli Storage Manager Implementation Guide...
Page 758: ...728 IBM Tivoli Storage Manager Implementation Guide...
Page 780: ...750 IBM Tivoli Storage Manager Implementation Guide...
Page 802: ...772 IBM Tivoli Storage Manager Implementation Guide...
Page 823: ...Index 793 Z z OS tape management 58 zOS 200...
Page 824: ...794 IBM Tivoli Storage Manager Implementation Guide...
Page 825: ...IBM Tivoli Storage Manager Implementation Guide...
Page 826: ......
Page 827: ......