Hi,

What I've done is to bring the recovery server up so that it alone thinks it
is the master, but let the rest of the environment know it by it's real
name.  For example:

Production NetBackup Master:    xxx
Disaster Recovery Master:       yyy

DNS continues to see the Recovery server as yyy, but the target Disaster
Recovery machine thinks that it is xxx.

It's easy to change the system's identity (as long as you can stand a
reboot).  Change the /etc/hosts, /etc/nodename, and /etc/hostname.<network
interface> files to reference xxx and then reboot your system.  On the
NetBackup clients that you want to restore to, make sure you set their
server name to yyy.

There may be better ways to do it but this has worked fine for us.

-Tim Blinsmon
Glaxo Wellcome, Inc.
Worldwide Information Systems Architecture and Technology
Email: tb39759 AT glaxowellcome DOT com    Maildrop: M3134A
Alternate Email: tblinsmon AT techieguy DOT com
Phone/Vmail: 919-483-7057   Pager: 888-368-3814     FAX: 919-483-7624
Internal Webpage: http://ussun4n.glaxo.com/group/tb/index.html

"Your focus determines your reality." - Qui-Gonn Jinn, Master Jedi

> -----Original Message-----
> From: Kyle O'Connor [SMTP:koconnor AT powertel DOT com]
> Sent: Thursday, September 21, 2000 10:36 AM
> To:   veritas-bu AT Eng.Auburn DOT EDU
> Subject:      [Veritas-bu] Re: Recovering NBDB on a different master
> server
> 
> 
> 
> Hello all,
> I am doing disaster recovery testing and am not clear on how to recover
> the
> netbackup database on a new master.
> The DLT 7000 tape drive is attached and the media is inserted, but when I
> ran
> the bprecover command,
> it is trying to restore to the old master.  Any suggestions.
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu