Yes, but that was the issue.  In 5.x Windows Admin Console you can no longer
do that.  It gives an error.

You can still do it with CLI or manually editing the config file.


- Scott

-----Original Message-----
From: Jorgen Lie [mailto:jlie AT glasshouse DOT com] 
Sent: Tuesday, November 30, 2004 10:15 AM
To: David Rock; Veritas-Bu (E-mail)
Subject: RE: [Veritas-bu] Can't change tries to zero - need to know how to
stop backups from running.

Change "Maximum Jobs per Client" to zero under the Master Server properties.
This will prevent any new jobs from starting until you change the value
back.  No need to track policies, no need to write scripts.
 
Thanks,
Jorgen

________________________________

From: veritas-bu-admin AT mailman.eng.auburn DOT edu on behalf of David Rock
Sent: Mon 11/29/2004 11:50 PM
To: Veritas-Bu (E-mail)
Subject: Re: [Veritas-bu] Can't change tries to zero - need to know how to
stop backups from running.



* WILLIAMS, KRISTOPHER L <kris.williams AT hp DOT com> [2004-11-29 22:20]:
> De-activating all the policies isn't really that bad, even if you have
many of them.
>
> Here is the windows command I use to do it. I'm sure there is a similar
"for" command that could be used on Unix.
>
> For /f %i in ('bppllist.exe') do bpplinfo.exe %i -modify -inactive

This _is_ bad if you already had policies that were inactive for a
reason. Now you have to worry about keeping track of them so that you
don't inadvertantly re-activate a policy that should _not_ be active.

--
David Rock
david AT graniteweb DOT com



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu