The most effective way to not run a schedule on a certain recurring day is
to build an admin schedule which runs a TSM script - The name of your
scheduled backup will be different than mine which in this case is
"powkarpr2":
tsm: AFCOPS2>q sched updatemontly type=a f=d
Schedule Name: UPDATEMONTHLY
Description:
Command: run updatemonthly
Priority: 4
Start Date/Time: 03/31/01 10:00:00
Duration: 1 Hour(s)
Period: 4 Week(s)
Day of Week: Saturday
Expiration:
Active?: Yes
Last Update by (administrator): GEORGE
Last Update Date/Time: 03/23/01 13:17:34
Managing profile:
It will run the TSM script "updatemontly"
------------------------------------------------------------
tsm: AFCOPS2>q script updatemontly f=d
Name: UPDATEMONTLY
Line Number: 1
Command: upd sched satdomain powkarpr2 startd=+1
Last Update by (administrator): GEORGE
Last Update Date/Time: 03/23/01 13:12:13
George Lesho
AFC Enterprises
Kent Monthei
<Kent.J.Monthe To: [EMAIL PROTECTED]
[EMAIL PROTECTED]> cc: (bcc: George Lesho/Partners/AFC)
Sent by: Subject: Scheduling a client backup to NOT
"ADSM: Dist occur 1 day a month - how-to
Stor Manager" recommendations needed
<[EMAIL PROTECTED]
IST.EDU>
03/05/02 02:37
PM
Please respond
to "ADSM: Dist
Stor Manager"
We have an NT client that's associated with a Solaris TSM Server's daily
backup schedule. On the 3rd of every month, an application process runs
on the NT client that clashes badly with TSM's scheduled backup, so we've
been asked to disable the TSM backup of this client on the 3rd of each
month.
There's no way to schedule this per-month exception using the Client
Schedule parameters. Could someone recommend a tried/tested method for
accomplishing this?
-rsvp, thanks
Kent Monthei
GlaxoSmithKline
