For restoring that is all you need.
For backing up you'd need to point your policy to the storage unit associated with the other media server. Also some operations will be slow due to timeouts trying to connect to the media server that is down even though you're not really directing traffic there. We do the FORCE_MEDIA_RESTORE option all the time to restore our PROD BCV backups to alternate servers for database refreshes. It works fine. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hindle, Greg Sent: Tuesday, March 27, 2007 12:54 PM To: NB List Mail Subject: [Veritas-bu] force restore option nb 5.0 mp7 Solaris 9 I have a media server that is down at the moment for maint and I have to run a restore. Both media servers connected to the same master. All I need to do is add the force restore statement to the master bp.conf file and then have the master rereads its bp.conf right? add FORCE_RESTORE_MEDIA_SERVER option in master bp.conf. FORCE_RESTORE_MEDIA_SERVER = <original media/master> <target media/master>. You then have to run bpadm g (global) m (modify) d (notify request daemon) to reread the bp.conf - this is done on the master server. Greg >>> This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu