I only need to duplicate the master server and its database on another host and not run concurrent backups, hence the need to change the server name. I need an identical build of the production environment to test upgrades to 6.5 MP4 and note problems and issues that arise after the upgrade.
Lightner, Jeff wrote: > In a DR you'd typically set the name of the DR server to what the > original master had been. The only reason I could see for keeping > original DR server name is that you intend to run whatever was already > on it concurrently with the NetBackup master you're about to load and > that would complicate your life incredibly. > > -----Original Message----- > From: veritas-bu-bounces < at > mailman.eng.auburn.edu > [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of > lookn4me > Sent: Monday, February 22, 2010 2:24 PM > To: VERITAS-BU < at > MAILMAN.ENG.AUBURN.EDU > Subject: [Veritas-bu] Steps to change Master Server Name > > > Yes you correct, I am looking to copy the catalog and its database to > the new host in order to test upgrading and locate break/fix issues > prior to the upgrade. I need to have as much of the master server > functionality as possible. The question I have is what needs to be done > in 5.1 MP4 version to change master server entries in the associated > databases? > > Surprising this is an issue in Netbackup if one had to DR a box to a > different hostname, the inability to name the master something else. > > > mdonaldson wrote: > > > Are you planning to copy your existing backup catalog (image database) > > over to the new environment? If so, then the master server name is > > buried in that database it's a far-from-casual process to rename the > > master server. There is no published process for it and Symantec will > > want to charge you for professional services to do this for you. > > > > If you're just going to create a new master server with it's own > > database, then it's simply a matter of building a new environment. > > > > If you're going to do backups of one client to both environments, > > > change > > > the first SERVER entry in the client's bp.conf file, that's the one > > > that > > > should point to that client's master server. It really should only > > matter, though, for client initiated actions, like restores. > > > > A media server would be more complex, I'd suggest not trying to > > dual-master a media server. > > > > -M > > > > -----Original Message----- > > From: veritas-bu-bounces < at > mailman.eng.auburn.edu > > [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of > > > lookn4me > > > Sent: Monday, February 22, 2010 6:37 AM > > To: VERITAS-BU < at > MAILMAN.ENG.AUBURN.EDU > > Subject: [Veritas-bu] Steps to change Master Server Name > > > > > > I plan to replicate a production environment on a test server, but I > > need to change the master server name as the test environment will not > > be isolated. Anyone out there have success with the process? The > > environment is Netbackup 5.1 MP4 on solaris 9 and 10 OS. > > > > > > > +---------------------------------------------------------------------- > > > |This was sent by btfoy < at > comcast.net via Backup Central. > > |Forward SPAM to abuse < at > backupcentral.com. > > > > > +---------------------------------------------------------------------- > > > > > > > _______________________________________________ > > Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > > > _______________________________________________ > > Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > > > > +---------------------------------------------------------------------- > |This was sent by btfoy < at > comcast.net via Backup Central. > |Forward SPAM to abuse < at > backupcentral.com. > +---------------------------------------------------------------------- > > > _______________________________________________ > Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > Proud partner. Susan G. Komen for the Cure. > > Please consider our environment before printing this e-mail or attachments. > ---------------------------------- > CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential > information and is for the sole use of the intended recipient(s). If you are > not the intended recipient, any disclosure, copying, distribution, or use of > the contents of this information is prohibited and may be unlawful. If you > have received this electronic transmission in error, please reply immediately > to the sender that you have received the message in error, and delete it. > Thank you. > ---------------------------------- > _______________________________________________ > Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu +---------------------------------------------------------------------- |This was sent by bt...@comcast.net via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu