If you're planning on leaving the daemons up on the temp. decommissioned
media server anyway, why not just set the max concurrent jobs for each
of its STUs to 0, run "bpschedreq -read_stunits" and "bpschedreq
-read_stu_config", and be done with it ? 

No bounces required, no policy modifications, and no new jobs will be
sent to those STUs until you want them to. You also won't have any SSO
communication issues like if you shutdown some of the daemons. 

- John Nardello

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Bob Stump
Sent: Tuesday, March 14, 2006 6:27 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] only temorarily de-commissioning a mediaserver

Thank you to all who replied to this thread. The media server is a SAN
media server so no policies will need to be changed.
The intent of this thread was to minimize the consequences of the
inter-relationships between all of the other media servers.
I want to minimize timeouts with SSO, and device monitor, etc... What
can be done for this?


>>> "Bob Stump" <stumpb AT michigan DOT gov> 3/13/2006 10:20:13 AM >>>
How can I minimize the effect of a media server temporarily ( 1 week)
being out of commission in an SSO SAN environment?
I do not want to take any action that would require stop/starting
netbackup. Perhaps I could change some timeouts??



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


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