|
Re: [Veritas-bu] "Maintenance Mode"
2010-07-15 13:06:25
On Thu, Jul 15, 2010 at 11:24 AM, Donaldson, Mark <Mark.Donaldson AT staples DOT com> wrote:
In the past, if a client was down due to maintenance during a backup, I
just closed the ticket. Using DP on their side, they've got a method to
put a backup client into "maintenance mode" before the backup and take
it out after.
Yesterday I tried setting "max jobs per client" to zero for a client but
that didn't work. "0" in max jobs means "not defined", not "zero".
The only way I can think is to either: make one policy per client and
deactivate the policy - which I don't want to do, or write a script to
pull the client from its policies and then add it back in 24 hours with
an "at" job. Not impossible, just kludgy.
It's actually not kludgy - just different. There are some of who really like this approach and I'm one of them. Not only do you get to de-activate the client temporarily but you can automatically have it come back (set the "Go into effect at:" date/time) and it's a lot easier to script adding new clients.
In NetBackup 7.0.1, Symantec introduced a "client offline" feature that allows you to put the client in maintenance mode. I don't know how that really works yet. I'm going to guess that since clusters are tolerated but not really supported that this feature is not going to work very well for clusters either (or other hosts with virtual server names).
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|
