[Veritas-bu] NBU Server Upgrade
This can be achieved w/o doing a catalog recovery. You can copy/ftp all your policies and images over. You can move the databases over as well. I recently did a Windows 2003 R2 64-bit to Solaris 10 SPARC migration this way. (In fact a catalog recovery was not an option for me due to the architecture change) The library move is trivial. Move all media into a standalone state (not sure if this step is needed although i think its in the documentation - I have done several library moves w/o doing this in the past). I would then do a nbemmcmd -deletealldevices on the source system before moving over the EMM database. Once netbackup is up and running on the new system, attach the library and just configure it as a new library and re-inventory. This procedure requires professional services unless you really understand the internals of netbackup. Support will not give you help with doing this. (at least this is what I was told) Since your going from windows to windows this might not be a requirement in your case. Only thing I suggest is keep the hostname the same, especially if your doing the catalog recovery approach. Also catalog recovery might seem like a daunting task at first glance but its actually pretty reliable. I've done several in my time. As long as your catalog backup competed with a status 0 your good to go. (unless you have media failure) I would make sure and note the media ID's of your last few catalog backups to be safe. +-- |This was sent by chuck.car...@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
Re: [Veritas-bu] NBU Server Upgrade
On Thu, Jun 2, 2011 at 11:13, rhugga nbu-fo...@backupcentral.com wrote: This can be achieved w/o doing a catalog recovery. You can copy/ftp all your policies and images over. You can move the databases over as well. ... This procedure requires professional services unless you really understand the internals of netbackup. Support will not give you help with doing this. (at least this is what I was told) Since your going from windows to windows this might not be a requirement in your case. We recently did a platform migration (Tru64 to Linux) and were informed that not only does Support not do this, but if you do it on your own, they /will not/ support you afterwards. The rational is that strange and subtle things can go wrong, and they don't want to end up troubleshooting problems that are the result of missing a step in the migration. Suggest you ask the question before going that route. - Bluejay Adametz Almost anything is easier to get into than out of. NOTICE: This message, including any attachments, is only for the use of the intended recipient(s) and may contain confidential and privileged information, or information otherwise protected from disclosure by law. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, copying, dissemination or distribution of this message or any of its attachments is strictly prohibited. If you received this message in error, please contact the sender immediately by reply email and destroy this message, including all attachments, and any copies thereof. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU Server Upgrade
Rusty, What do you mean by this: “Use tar and some other OS tricks to do a simultaneous tar and copy to the remote machine”? Does the “Import Images” option not copy all the existing *.info and *.img files over from the old server to the new server? Once the “Recover the Catalog” operation completes, can you just do a simple copy command with the actual images? James McDonald System Administrator SAIC - IISBU 410-312-2232 From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Thursday, May 19, 2011 2:43 PM To: McDonald, James F. II Cc: veritas-bu@mailman.eng.auburn.edu; veritas-bu-boun...@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU Server Upgrade Here's what we do for a UNIX (Solaris) server refresh. -Install NBU and patch to the same level on the new server -Make a final catalog and system backup of the old server -Shut down NBU on old system -Use tar and some other OS tricks to do a simultaneous tar and copy to the remote machine -Swap over library/drive connections and configure in OS (this can be done before if a switched connection) -Swap IPs and hostnames -Reboot both servers, making sure NBU does not start on boot -Reconfigure drives/robot -Test -Resolve any issues Of course this is UNIX, so, IMO, there are some OS tools that make this so much easier than on Windows. Perhaps cygwin could help, or there are some Windows tools you're aware of to achieve the same goal. This has worked extremely well for several migrations, though it can be time consuming. It has taken us most of a day before, but that is dependent on what size pipe you have available when doing the file transfer (100Mb not fun). Here's another idea. What if you setup your new server, then used DoubleTake or something like that to mirror NBU to it? Or, what about pulling the drives (hopefully a mirror set) and putting them in the new server? Yes, there would probably be some hardware differences, but hopefully Windows could get past that. Then you could upgrade Windows to 2008 and be done. Another idea is to upgrade to Win2k8 and then move to the new server via one of the above methods. Whatever you end up doing, I recommend a practice run if you can afford that. Don't do anything to your old system that would prevent falling back. Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information Connected® ▪ http://availability.sungard.com/ http://availability.sungard.com/ P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. McDonald, James F. II james.f.mcdonald...@saic.com Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 05/19/2011 09:43 AM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] NBU Server Upgrade My current NBU server has lost its warranty coverage and instead of paying for more coverage, I was given a new server that has a warranty intact. I need to upgrade to this newer server so I just wanted to get some guidance on the procedure to do so. The current setup is a Dell 2950, running Server 2003 and NBU 7.0. There is tape storage attached to the current NBU server, via a SCSI card. The new setup will be in a newer Dell 2950, running Server 2008 and NBU 7.0. I will need to transfer everything (db’s, images, tape storage, etc.) to the new server. Below are some instructions I found online. Please comment, add or take away. This will be a first-time “recovery” for me, so any guidance would be greatly appreciated. Recovery When Windows is Intact Master Server Disk Recovery for Windows Before starting, verify that you have: NetBackup server software for Windows The latest NetBackup catalog backup on tape or disk Determine the install_path in which NetBackup is installed. By default, NetBackup is installed in C:\Program Files\VERITAS . Recovering the Master Server (Windows intact) To recover the Master server with the operating system intact 1. Partition the disks as they were before the failure. 2. Install NetBackup server software. However, do not configure any NetBackup policies or devices. 3. Install any NetBackup patches that had previously been installed. 4. Update the external mapping files. 5. Enable debug logging by creating the following directories: install_path\NetBackup\logs\tar install_path\NetBackup\logs\bpinetd 6. Start the NetBackup Client service and stop all other NetBackup services. Use the NetBackup Activity Monitor, or the Services application in the Windows Control Panel. 7. Use the bprecover command to recover the NetBackup catalogs: Choose one
[Veritas-bu] NBU Server Upgrade
My current NBU server has lost its warranty coverage and instead of paying for more coverage, I was given a new server that has a warranty intact. I need to upgrade to this newer server so I just wanted to get some guidance on the procedure to do so. The current setup is a Dell 2950, running Server 2003 and NBU 7.0. There is tape storage attached to the current NBU server, via a SCSI card. The new setup will be in a newer Dell 2950, running Server 2008 and NBU 7.0. I will need to transfer everything (db's, images, tape storage, etc.) to the new server. Below are some instructions I found online. Please comment, add or take away. This will be a first-time recovery for me, so any guidance would be greatly appreciated. Recovery When Windows is Intact Master Server Disk Recovery for Windows Before starting, verify that you have: NetBackup server software for Windows The latest NetBackup catalog backup on tape or disk Determine the install_path in which NetBackup is installed. By default, NetBackup is installed in C:\Program Files\VERITAS . Recovering the Master Server (Windows intact) To recover the Master server with the operating system intact 1. Partition the disks as they were before the failure. 2. Install NetBackup server software. However, do not configure any NetBackup policies or devices. 3. Install any NetBackup patches that had previously been installed. 4. Update the external mapping files. 5. Enable debug logging by creating the following directories: install_path\NetBackup\logs\tar install_path\NetBackup\logs\bpinetd 6. Start the NetBackup Client service and stop all other NetBackup services. Use the NetBackup Activity Monitor, or the Services application in the Windows Control Panel. 7. Use the bprecover command to recover the NetBackup catalogs: Choose one of the procedures under http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_558 Recovering the NetBackup Catalogs for http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_558 Windows http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_558 on page 544 http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_558 . 8. When catalog recovery is complete, start the NetBackup services that are not already running. Use the Activity Monitor, or the Services application in the Windows Control Panel. Master Server Disk Recovery for Windows Caution: In step 9 http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_551 , do not restore files to the install_path \NetBackup\db, install_path \NetBackup\var , or install_path \Volmgr\database directories. These directories were recovered instep 7 http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_550 and overwriting them with regular backups will leave the catalogs in an inconsistent state. 9. Restore all other files: a. Start the NetBackup Administration interface on the master server. b. Start the Backup, Archive, and Restore utility. c. Browse for restores and select the partitions that were lost. d. Deselect the install_path \NetBackup\db, install_path\NetBackup\var and install_path\Volmgr\database directories (see the caution above). e. Start the restore. 10. When all partitions are restored, check the debug logs in the directories created instep 5 http://www.scribd.com/doc/51074367/97/Recovery-When-Windows-is-Intact#o uter_page_550 . If there are any ERR or WRN messages, resolve the problems before proceeding. 11. Reboot the system. This replaces any files that were busy during the restore. When the boot process is complete, the system is restored to the state it was in at the time of the last backup James McDonald System Administrator SAIC - IISBU 410-312-2232 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU Server Upgrade
Here's what we do for a UNIX (Solaris) server refresh. -Install NBU and patch to the same level on the new server -Make a final catalog and system backup of the old server -Shut down NBU on old system -Use tar and some other OS tricks to do a simultaneous tar and copy to the remote machine -Swap over library/drive connections and configure in OS (this can be done before if a switched connection) -Swap IPs and hostnames -Reboot both servers, making sure NBU does not start on boot -Reconfigure drives/robot -Test -Resolve any issues Of course this is UNIX, so, IMO, there are some OS tools that make this so much easier than on Windows. Perhaps cygwin could help, or there are some Windows tools you're aware of to achieve the same goal. This has worked extremely well for several migrations, though it can be time consuming. It has taken us most of a day before, but that is dependent on what size pipe you have available when doing the file transfer (100Mb not fun). Here's another idea. What if you setup your new server, then used DoubleTake or something like that to mirror NBU to it? Or, what about pulling the drives (hopefully a mirror set) and putting them in the new server? Yes, there would probably be some hardware differences, but hopefully Windows could get past that. Then you could upgrade Windows to 2008 and be done. Another idea is to upgrade to Win2k8 and then move to the new server via one of the above methods. Whatever you end up doing, I recommend a practice run if you can afford that. Don't do anything to your old system that would prevent falling back. Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information Connected® ▪ http://availability.sungard.com/ P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. McDonald, James F. II james.f.mcdonald...@saic.com Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 05/19/2011 09:43 AM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] NBU Server Upgrade My current NBU server has lost its warranty coverage and instead of paying for more coverage, I was given a new server that has a warranty intact. I need to upgrade to this newer server so I just wanted to get some guidance on the procedure to do so. The current setup is a Dell 2950, running Server 2003 and NBU 7.0. There is tape storage attached to the current NBU server, via a SCSI card. The new setup will be in a newer Dell 2950, running Server 2008 and NBU 7.0. I will need to transfer everything (db’s, images, tape storage, etc.) to the new server. Below are some instructions I found online. Please comment, add or take away. This will be a first-time “recovery” for me, so any guidance would be greatly appreciated. Recovery When Windows is Intact Master Server Disk Recovery for Windows Before starting, verify that you have: NetBackup server software for Windows The latest NetBackup catalog backup on tape or disk Determine the install_path in which NetBackup is installed. By default, NetBackup is installed in C:\Program Files\VERITAS . Recovering the Master Server (Windows intact) To recover the Master server with the operating system intact 1. Partition the disks as they were before the failure. 2. Install NetBackup server software. However, do not configure any NetBackup policies or devices. 3. Install any NetBackup patches that had previously been installed. 4. Update the external mapping files. 5. Enable debug logging by creating the following directories: install_path\NetBackup\logs\tar install_path\NetBackup\logs\bpinetd 6. Start the NetBackup Client service and stop all other NetBackup services. Use the NetBackup Activity Monitor, or the Services application in the Windows Control Panel. 7. Use the bprecover command to recover the NetBackup catalogs: Choose one of the procedures under “Recovering the NetBackup Catalogs for Windows” on page 544. 8. When catalog recovery is complete, start the NetBackup services that are not already running. Use the Activity Monitor, or the Services application in the Windows Control Panel. Master Server Disk Recovery for Windows Caution: In step 9, do not restore files to the install_path \NetBackup\db, install_path \NetBackup\var , or install_path \Volmgr\database directories. These directories were recovered instep 7 and overwriting them with regular backups will leave the catalogs in an inconsistent state. 9. Restore all other files: a. Start the NetBackup Administration interface on the master server. b. Start the Backup, Archive, and Restore utility. c. Browse for restores and select the partitions that were
