Unit 6:

Central Scheduler
 2

Objectives
Upon the completion of this course, you will be able to:

• Describe the Tivoli Storage Manager scheduling modes available.

• Set server and client schedule options.
• Build a client schedule.
• Build an administrative schedule.
• Manage the event log.
 3

Schedules

Intelligent management by central scheduling

11 12 1
10 2
9 3
8
7 6 5
4 TSM Server

WAN/SAN • Two types of scheduling

• Client scheduling
– Backup/Restore and
Archive/Retrieve
– Client OS commands and scripts
– One-time scheduled commands
• Administrative scheduling
– Administrative commands
– Scripts to automate series of events
 4

Central Scheduler Mode – Client Polling

Client Polling

Client Scheduling function

2
Schedule time
TSM
SERVER
1 Query for Schedule

WAIT

3 Start Backup/Archive
12

10
11 1
2
3
TSM
9
8
7
6
5
4
DB
Schedules
All Communications Methods
 5

Central Schedule Mode – Server Prompted

1 Register address
Client 10
11
12
1
2 TSM
2 Schedule function 9 3

SERVER
8 4
7 5
6

3 Start Backup/Archive

TCP/IP Protocol Only TSM

DB
Schedules
 6

Selecting Schedule Methods

SET SCHEDMODes
ANY/POLLing/PRompted
TSM
SERVER
Prompted

Administrative
SYSTEM
Privilege Client
Client Options File (All Schedule Modes) Polling

SCHEDMOD POlling/PRompted Client

SCHEDLOGname file.name Log File
SCHEDLOGRETENTION value
MAXCMDRETRIES value
RETRYPERIOD minutes
PRESCHEDULECMD cmd
POSTSCHEDULECMD cmd
 7

Pre and Post Schedule Processing

• PREschedulecmd=command string or PRENschedulecmd=command string

• POSTschedulecmd=command string or POSTNschedulecmd=command

12
11 1
10 2
9 3
8 4
7 5
6

1 Server prompts client 2 PRE command string executes first

to begin scheduled Quiesce DB
backup. Onarchive DB
TSM scheduled action executes
Backup resultant files from
onarchive
TSM Post command string executes last
SERVER
Check result
Start DB
TSM
Client
3 Backup
 8

Consistent Client Return Codes from dsmc.exe

Return Meaning
code

0 Operation completed successfully

4 Operation completed successfully, except for one or more

skipped files

8 Operation completed with one or more warning messages

issued

12 Operation failed with one or more error messages (except for

skipped files) issued
 9

Additional Server Prompted Options

CLIENT

Client Options File

SCHEDMODe PRompted

COMMmethod TCPip

TCPCLIENTAddress domain_name/dot_address

TCPCLIENTPort 1501
 10

Additional Client Polling Options

CLIENT

Client Options File

QUERYSCHedperiod How often to contact the

Server (HOURS)

QUERYSCH 12 (Default)
 11

Managing Client/Server Sessions

Administrators with system privilege can set:

MAXSCHedsessions • Percentage of Maxsession that can be used for

centralized scheduling.

MAXCMDRetries • How many retries of a failed scheduled command.

RETRYPeriod • Duration between client/server retries.

QUERYSCHedperiod • If in client polling mode:

RANDomize – How often to contact the server
– The degree of start time randomizing
 12

Scheduler Options Summary

12
11 1
Client Polling 10 2
Options File DSM.OPT 9 3
8 4
SCHEDMODE POLLING 7
6
5

COMMMETHOD any method CLIENT

SCHEDLOG SCHED.LOG
SCHEDLOGRENTENTION 5
MAXCMDRETRIES 2
RETRYPERIOD 15
QUERYSCHedperiod 12

TSM Server

DSM.SYS (UNIX) SET SCHEDMODE ANY

SET MAXSCH NN%
Server Prompted (Above plus these) SET MAXCMDR 2
SET RETRYP 15
Options File DSM.OPT
OR
SCHEDMODE PROMPTED
COMMMETHOD TCP/IP SET SCHEDMODE POLLING
TCPCLIENTA domain_name/dot_address SET QUERYSCH 12
TCPCLIENTPORT 1501 SET RANDOMIZE 50%

DSM.SYS
(UNIX)
 13

Passwordaccess Generate
• Encrypted client password
stored on client workstation.
• Automatically picked up by TSM clien.t
• New password regenerated automatically
when old expires.
• New support for
passwordaccess generate
• Novell NetWare
• Macintosh
• Win32 GUI passworddir C:\SECRET
• PASSWORDACCESS
DSM.OPT Encrypted TSM password
GENERATE option
• DSM.OPT file on singleuser clients.
• DSM.SYS on multiuser clients.
• PASSWORDDIR option C:\SECRET\TSM.PWD
• Specifies location of encrypted node
password.
• Win32 client store encrypted password in
Registry.
 14

Managing Schedules

Policy Domain: Dept. Chocolate

SCHEDULE NODES POLICY
MILK DAILY
MILK
Priority 1 DARK MC1
WHITE
MKT1
DARK SCHEDULE MKT2 MC2
WEEKLY

Priority 3

WHITE • Schedule defined for specific policy

domain.
• Multiple schedules for a policy domain.
• Clients associated with one or more
Admin with schedules.
SYSTEM/POLICY
• Administrator defined and maintained.
• May prioritize schedules.
• Copy across policy domains.
 15

Instructor Demonstration
 16

Defining Schedules – Relative Date and Time

• Can specify date and time relative to the execution of the
command.
• Useful for the scheduled commands.
• Relative date
12
• DATE=mm/dd/yyyy 11 1

• DATE=TODAY + number of days 10 2

• DATE=TODAY - number of days 9 3

• DATE=TODAY 8 4

7 5
• Relative time 6

• TIME=hh:mm:ss
• TIME=NOW + number of hours : number of minutes
• TIME=NOW - number of hours : number of minutes
 17

Define Schedule – Command Line

DEFine SCHedule domainname schedulename

Type=Client DESCription=description
ACTion=action OPTions=optionstring
OBJects=objectstring PRIority=priorityvalue
STARTDate=startdate STARTTime=starttime
DURation=durationvalue DURUnits=durunitsvalue
PERUnits=perunitsvalue PERiod=periodvalue
DAYofweek=dayofweekvalue
EXPiration=expirationvalue

UPDATE Schedule...
DELETE Schedule...
 18

Query Schedule – Command Line

q sched
Domain Schedule Name Action State Date/Time Duration Period Day
STANDARD DAILY_INCR Inc Bk 01/10/2000 23:05:27 2H 1D Any
STANDARD WEEKLY_INCR Inc Bk 01/10/2000 23:05:27 1H 1W Fri
q sched daily_incr f=d

Policy Domain Name: STANDARD

Schedule Name: DAILY_INCR
Description: Daily incremental backup
Action: Incremental
Options:
Objects:
Priority: 5
Start Date/Time: 01/10/2000 23:05:27
Duration: 2 Hour (s)
Period: 1 Day (s)
Day of Week: Any
Expiration:
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 01/10/2000 23:05:27
 19

DEFine ASSOCiation Command Line

DEFine ASSOCiation domainname schedulename nodename(s)

Schedule
 20

Instructor Demonstration
 21

Schedule Example

Backup Backup
24:00 Start Start

actual backup time

startup window

01:00 01:00
M T W T F

Startup window: Starttime = 01:00 Function: Action = Incremental Backup

Time between windows: Period = 2 days Duration = 6 hours

• Action must start within startup window.

• Action may not complete within window.
• Schedule operations run serially on client.
• Event log maintained on server.
 22

Randomizing Example

NODE A NODE B NODE B NODE A NODE C NODE C

01:30 03:01 05:00 05:45

Randomize Period RP
22:00 01:00 04:00 05:00 06:00 07:00
Polls Startup Window
Starts
Randomize% = 50 • Scatter schedule start time across window.
• Balance network/server loads.
• % specification
Defines fraction of the window over which start
times distributed.
• Randomization period based on time client polls.
• Client polling mode only.
 23

Server Prompted Example

Register

Schedule
TSM Server Client
Start

DSM.OPT DSM.SYS (UNIX)

SET MAXSESSIONS 100
SCHEDMODE PROMPTED
SET MAXSCHEDSESSIONS 90 COMMMETHOD TCPIP
SET SCHEDULE PROMPTED

DEFINE SCHEDULE DOMAIN SCHEDULENAME

ACTION=I, STARTT = 23:30
DUR=6, PERIOD=1
DURU=HOURS, PERU=DAYS
DAYOFWEEK= WEEKDAY
 24

One-time Scheduled Client Commands

• DEFINE CLIENTACTION command
• Defines a schedule
• Associates schedule with a client
• Wait parameter allows client operation to complete

• Schedule execution
• Commands executed as soon as possible by client, dependent on:
– client scheduling mode
– queryschedperiod for polling mode
• Client must have scheduler running
• SET CLIENTACTDURATION command
• Number of days before action is deleted from database.
 25

Instructor Demonstration
 26

Administrative Command Scheduling

• Administrator commands can be handled by TSM
scheduler to:
• Automate server operations.
• Ensure server resources are available to clients.
• Ensure server functions performed with minimal manual intervention.

• Type of schedule (TYPE=Administrative).

• Can view administrative command schedule event status.
• Output sent to the activity log.
• Not associated to a policy domain.

12
11 1
10 2
9 3 TSM
8 4
7
6
5 SERVER

Administrator
Schedule Commands
 27

Administrator Scheduling Commands

EXAMPLES
• Lower threshold to immediately start migration.
• Lower threshold to immediately start reclamation.
• TSM server database backup.
• Inventory expiration.
• Storage pool backup.

All administrative commands except QUERY ACTLOG

12
11 1
10 2
9 3 TSM
8 4
7 5 SERVER
6
 28

Instructor Demonstration
 29

Managing Database Events

• Each scheduled operation is
an event.
• All events are recorded in
the database.
• Provides an audit trail of DATABASE
completed or missed events
• Event records purged based
on retention period

Event Log

Schedules

SET EVENTRETENTION 10
 30

Query Event Command

• Display information on scheduled and completed events.
• All administrators can query events.
• Two types of query
• All events (general reporting)
• Failed events (exception reporting)

• Can select subset of a report by

• Policy domain, schedule name, node name, date
• Two report formulas
• Standard or detailed
 31

Standard Event Report

Schedule Start Actual Start Scheduled Name Node Name Status

07/11/2000 01:00:00 07/11/2000 01:12:00 DAILY BACKUP MILK COMPLETED

07/11/2000 01:15:00 07/15/2000 01:30:20 DAILY BACKUP DARK FAILED

07/11/2000 02:00:00 07/11/2000 02:01:55 WEEKLY BACKUP WHITE STARTED

07/11/2000 02:02:00 07/11/2000 02:05:25 MONTHLY BACKUP MKT1 COMPLETED

07/15/2000 01:20:00 07/15/2000 01:20:25 RESTORE MKT2 COMPLETED

07/15/2000 01:24:00 INCRTAL BACKUP PKG1 MISSED

Command: Query EVent DOMAIN1 *

 32

Detailed Event Report

Policy Domain Name: DOMAIN1

Schedule Name: DAILY BACKUP
Node Name: MILK
Schedule Start: 07/11/2000 01:00:00
Actual Start: 07/11/2000 01:12:00
Completed: 07/11/2000 01:13:07
Status:
Result: COMPLETED
0

Command: Query EVent DOMAIN1 * Format=Detailed

 33

Student Exercise
 34

Summary
You should now be able to:

• Describe the TSM scheduling modes available.

• Set server and client schedule options.
• Build a client schedule.
• Build an administrative schedule.
• Manage the event log.