What we did was to simply build a new master with new name/IP and continue to run the old master along side it allowing natural aging of policies/recalls from offsite storage for vaulting for 3-4 months then we shutdown the old server. This means for any older backups we'd want to restore we'd have to import the tape into the new master. We chose to do it this way because old master was controlling a library with LTO1 drives whereas new environment was mostly LTO5 which won't read LTO1s anyway so we also have a couple of LTO3s in case we need to import one of the LTO1s.
The research I did at the time indicated there really is NO good way to use new name/IP with old Catalog without paying ransom to Symantec. I saw comments from some then that they had tried to do it anyway and although it initially appeared to work months later they began having issues related to the attempt. You'll find folks that say they've done it but if you look carefully at those old posts you'll see it was mostly for NBU versions 3.x and nothing newer. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kalusche, Dan Sent: Monday, July 09, 2012 8:09 AM To: [email protected]; [email protected] Subject: Re: [Veritas-bu] Netbackup 7.1 Migration I also followed this path - same name/same IP. The old server was left on the network while the hot catalog ran. When that finished, I removed the old master from the network, plugged in the new master, restored the catalog and away we went. In reality, it was fairly painless. I heard a lot of bad things about changing the name/IP so I didn't want to go there. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Saturday, July 07, 2012 4:57 AM To: [email protected] Subject: Re: [Veritas-bu] Netbackup 7.1 Migration The plan I went with was to build the new hardware 1st and give it the same name and IP address as the original master server. Install the same NetBackup version as the old server. Complete a hot catalog backup on the old server, then take it offline. Bring the new master server online and restore the catalog backup. Then upgrade the NetBackup version. This path is approved by Symantec and does not involve Symantec personnel in any fashion. The media servers will recognize the new master immediately because it has the same DNS name and IP address, and there will be very minimal downtime. Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of srikanth09 Sent: Thursday, July 05, 2012 6:06 AM To: [email protected] Subject: [Veritas-bu] Netbackup 7.1 Migration Hello Everybody. We have implemented Netbackup 7.1 for backups. We have 1 master server(standard) on Solaris-10 and 12 clients(standard). We are going to upgrade the master server to Enterprise and one of the clients to Enterprise. Once this is completed, we have to migrate the master server to another physical server. The physical server has all the hardware same as the existing hardware. The hostname and IP address will change. I read through the below TNs: http://www.symantec.com/docs/TECH31385 http://www.symantec.com/docs/TECH77448 It says, "Moving a Master Server to a new machine involving a host name change" Netbackup master hostname is deeply embedded in each part of Netbackup config and EMM database. Only a trained Consulting Partner can change this hostname. Can anyone please help me perform this migration without involving Symantec consultants. It would be very helpful if anyone could provide the steps needed to perform the migration or if any document is available.These kind of migrations must be done frequently around Netbackup customers so I am hoping there are some Netbackup gurus who has performed the migrations and could provide some good advice. Thanks in advance Regards Sri +---------------------------------------------------------------------- |This was sent by [email protected] via Backup Central. |Forward SPAM to [email protected]. +---------------------------------------------------------------------- _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Athena(r), Created for the Cause(tm) Making a Difference in the Fight Against Breast Cancer --------------------------------- 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 - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
