Instead of disablesched yes in the dsmserv.opt file, you can run
disable sessions from an admin client. Then again, this would prevent any
new backup sessions from starting. Not just those in a particular
schedule. Updating the schedule to some future start date is the best
solution.
For question # 2. A somewhat more elegant way of preventing a single
client from running a schedule is to lock the client using the lock node
command.
John Johnson
"Thomas A. La
Porte" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
MWORKS.COM> Subject: Re: How Best to Suspend a
Schedule
Sent by: "ADSM:
Dist Stor Manager"
<[EMAIL PROTECTED]
DU>
04/19/2002 10:51 AM
Please respond to
"ADSM: Dist Stor
Manager"
That would involve recycling the server, wouldn't it? I'm
guessing from Paul's e-mail that he's looking for something he
can do online.
What I've done in the past is update the start date of the
schedule to the following day, that way it won't run in the
coming evening, but will pick up again the next day without me
having to intervene.
On Fri, 19 Apr 2002, Edgardo Moso wrote:
>For #1 you can set , "disablesched Yes" in the dsmserv.opt file.
>
>
>
>
>
>From: "Kilmer, Paul" <[EMAIL PROTECTED]> on 04/19/2002 09:02 AM
>
>Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>To: [EMAIL PROTECTED]
>cc:
>Subject: How Best to Suspend a Schedule
>
>As a relative newbie to TSM, I'd be interested to hear what is the easiest
>way to temporarily:
>1- Suspend a backup schedule from running.
>2- Suspend an individual client's participation in a backup schedule.
>
>I've accomplished #2 by removing the client schedule association, though I
>don't regard this method to be particularly elegant.
>
>Thanks in advance.
>
>Paul E. Kilmer
>Lead Technical Architect
>New World Pasta
>[EMAIL PROTECTED]
>(717) 526-2431
>
>|********************************|
>|* <http://www.eteamz.com/cdboys> www.eteamz.com/cdboys *|
>|********************************|
>| |
>
>
