Re: [Veritas-bu] Netbackup 7.1 Migration
Sri, Make sure you keep both old and new on same version and patch level. Word of advice, 7.5 upgrade is not so simple it involves a stage call image migration. > To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU > From: nbu-fo...@backupcentral.com > Date: Wed, 11 Jul 2012 23:27:43 -0700 > Subject: [Veritas-bu] Netbackup 7.1 Migration > > Here's the plan, please correct me if wrong: > > 1. Install NBU on new server and configure all the policies,devices from > scratch. > 2. take catalog backup on old master server and stop NBU services. > 3. Use recover without import option and import all data tapes from old > master to new master. > 4. The NBU services are not running on old master server, but since that is a > production server we need to backup the data on it. So configure old master > as client in new master. > > Versions: > --- > Old master server: NBU 7.1 Standard > New master server: NBU 7.5 Enterprise > > Please advice, will there be any compatibility issues? > > Thanks & Regards > Sri > > +-- > |This was sent by st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 7.1 Migration
This option will work, technically speaking, but you may need to buy additional licenses to be in compliance. Thank you, Rusty -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Monday, July 09, 2012 10:05 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Netbackup 7.1 Migration Thank You all for your replies. I have to change the hostname and IP address, there is no other option. We currently have installed the master server on a production server. Its not a dedicated backup server. The new server we are planning is a dedicated NBU master server. So the hostname will change from the current server :-( I think i would go with Jeff' idea of building new server from scratch and importing media from old server to new server in case of restore requests. Can we use the option of keeping current server and as well as new server till the data on the current tapes expire? Remove all the tapes from current server and keep it write protected. Stop the NBU services on current server. Whenever a restore request comes, stop the services on new server and restore data from old server. Thanks Sri +-- |This was sent by st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 7.1 Migration
Just to be clear - we kept the old master running so it could continue to do vaulting reports to recall media from offsite as they expired. If you're not doing vaulting this may not be a consideration for you. We didn't do the 1 year Jonathan suggests - our intent was to do 3 months since most of our monthlies expire in that time frame. In actuality it ended up being more than 6 months but that was just because we were slammed. In our case we wanted to make the old master a media server for the new environment due to disk replications/backups we did there. (It was HP-UX and we couldn't do the replications to Linux owing to filesystem/volume manager used on HP-UX and not on Linux.) My question would be if the existing server is a "Production" server how are you backing up that "Production" stuff after you switch to the new master? That is to say, in our case we didn't have to keep any other app running on the old master and were able temporarily to move the disk replication to another HP-UX server. In your case however you need to be concerned with this other "Production" stuff. You can't run the old master as a master for the old environment AND as a client/media server for the new environment as well. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Tuesday, July 10, 2012 8:47 AM To: Kalusche, Dan; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup 7.1 Migration We used a variation on this here. We stood up a new master, then waited 1 year for 99% of our images to expire. Then we imported the old media (SLT) on the new master and duplicated them to new media (LTO). Just keep in mind that when you do this, you need to make sure the retentions match on the old and new masters. If retention 10 on your old master is infinity and retention 10 on the new master is 1 year, the images will only be kept for 1 year on import. Good luck! -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kalusche, Dan Sent: Tuesday, July 10, 2012 8:18 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup 7.1 Migration I would think that keeping the current server would be an option for you. I would have done the same if we didn't have a multitude of images saved to infinity... Our old master would have been around forever, so I just did the migration... Good Luck! -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Monday, July 09, 2012 10:05 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Netbackup 7.1 Migration Thank You all for your replies. I have to change the hostname and IP address, there is no other option. We currently have installed the master server on a production server. Its not a dedicated backup server. The new server we are planning is a dedicated NBU master server. So the hostname will change from the current server :-( I think i would go with Jeff' idea of building new server from scratch and importing media from old server to new server in case of restore requests. Can we use the option of keeping current server and as well as new server till the data on the current tapes expire? Remove all the tapes from current server and keep it write protected. Stop the NBU services on current server. Whenever a restore request comes, stop the services on new server and restore data from old server. Thanks Sri +-- |This was sent by st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu 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 immediatel
Re: [Veritas-bu] Netbackup 7.1 Migration
We used a variation on this here. We stood up a new master, then waited 1 year for 99% of our images to expire. Then we imported the old media (SLT) on the new master and duplicated them to new media (LTO). Just keep in mind that when you do this, you need to make sure the retentions match on the old and new masters. If retention 10 on your old master is infinity and retention 10 on the new master is 1 year, the images will only be kept for 1 year on import. Good luck! -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kalusche, Dan Sent: Tuesday, July 10, 2012 8:18 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup 7.1 Migration I would think that keeping the current server would be an option for you. I would have done the same if we didn't have a multitude of images saved to infinity... Our old master would have been around forever, so I just did the migration... Good Luck! -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Monday, July 09, 2012 10:05 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Netbackup 7.1 Migration Thank You all for your replies. I have to change the hostname and IP address, there is no other option. We currently have installed the master server on a production server. Its not a dedicated backup server. The new server we are planning is a dedicated NBU master server. So the hostname will change from the current server :-( I think i would go with Jeff' idea of building new server from scratch and importing media from old server to new server in case of restore requests. Can we use the option of keeping current server and as well as new server till the data on the current tapes expire? Remove all the tapes from current server and keep it write protected. Stop the NBU services on current server. Whenever a restore request comes, stop the services on new server and restore data from old server. Thanks Sri +-- |This was sent by st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 7.1 Migration
I would think that keeping the current server would be an option for you. I would have done the same if we didn't have a multitude of images saved to infinity... Our old master would have been around forever, so I just did the migration... Good Luck! -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Monday, July 09, 2012 10:05 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Netbackup 7.1 Migration Thank You all for your replies. I have to change the hostname and IP address, there is no other option. We currently have installed the master server on a production server. Its not a dedicated backup server. The new server we are planning is a dedicated NBU master server. So the hostname will change from the current server :-( I think i would go with Jeff' idea of building new server from scratch and importing media from old server to new server in case of restore requests. Can we use the option of keeping current server and as well as new server till the data on the current tapes expire? Remove all the tapes from current server and keep it write protected. Stop the NBU services on current server. Whenever a restore request comes, stop the services on new server and restore data from old server. Thanks Sri +-- |This was sent by st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 7.1 Migration
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: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kalusche, Dan Sent: Monday, July 09, 2012 8:09 AM To: mja...@guesswho.com; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU 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: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of mja...@guesswho.com Sent: Saturday, July 07, 2012 4:57 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU 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: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Thursday, July 05, 2012 6:06 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU 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 st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Athena(r), Created for the Cause(tm) Making a
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: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of mja...@guesswho.com Sent: Saturday, July 07, 2012 4:57 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU 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: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Thursday, July 05, 2012 6:06 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU 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 st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of srikanth09 Sent: Thursday, July 05, 2012 6:06 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU 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 st.sr...@gmail.com 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 7.1 Migration
I think you need a new plan. Cheers, Wayne ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
