Video Screencast Help

Moving NetBackup master server to new server.

Created: 20 Dec 2009 • Updated: 06 Jul 2010 | 7 comments
Amin123's picture

Hi,
I have a master server NBU 6.5 in windows 2003 platform, if I need to move NetBackup master server to new server with the same paltfrom windows 2003. what is the best stpes of doing so.
I will keep the same host name.
Also if I need to move to new platform windows 2008. Also what is the steps needed for that.

Thanks,
Amin

Comments 7 CommentsJump to latest comment

Marianne's picture

Hi Amin
Have a look at Chapter 7 (Dissaster Recovery) in the Troubleshooting Guide. As the new server will have a fully functional O/S, look at the section in this chapter called 'Recovering the master server with Windows intact'.
The process for moving to 2008 will be pretty much the same - just take note that NBU server is only supported on x64 O/S. There is a new 64-bit NBU 6.5.4 version. Have a look at this thread for more info: https://www-secure.symantec.com/connect/forums/nbu...

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

g_man's picture

I just did a similar upgrade -- going from W2k3 to 64 bit W2k8.

My process went something like this:
1. Present tape library and drives to new server
2. Setup persistent binding for tape drives
2. Run catalog backup on master
3. Unjoin master from domain, change name, and IP
4. Assign new server IP and name from old master - and join domain
5. Install Netbackup master server
6. Restore catalog

It was really a lot easier than I was thinking. The only mistake I made was not identifying all the SAN media servers when doing the iniital Netbackup master install. I only identified the media servers. Once I realized what I had done, this was easily fixed.

I did not change Netbackup versions during this hardware upgrade -- I wanted to keep the number of changes to a minimum.

SteveYu's picture

Gman is correct. Just wanted to add a small note that you should also make sure that you install netbackup in the same place as the original install. Ie if you installed NBU on c:\ you should do so in the exact same path c:\ on the new host

Stuart Green's picture

Steve Jobs masquerading as Symantec Employee with his One More Thing?
Happy New Year :-)

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

stu@symantec's picture

All of the above are decent methods of doing a hardware migration. 

Please keep this in mind, the more you change the more unknown you added to your project, and therefore more risk.  Technically speaking Symantec's Support does not provide 'support' and official procedures to do this migration because of all the variables and unknowns.  If you need to perform the move and reduce risk, Professional Services should be considered.

The highest probability of success on a migration is to go from like hardware to like hardware, version to same version, and like O/S to like O/S -- including 32bit versus 64bit O/S.  The more you change from this, the higher the risk.  Although there are more risk involve, it is possible to migrate NBU or parts of NBU such as the catalog, from 1 machine to another, of different O/S versions, types, etc (Professional Services from Symantec can help with this too).   It is best to test these scenario on lab machines before performing on a production system on your own.

The minimal risk you need to be aware of is any integrety issues when copying files (or restoring files) from 1 host to another.  This is rare, but it can happen.  The part you will care the most is obviously your catalog.   If you have some advance scripting knowlege you can script a utility to get a recursive md5 sums of all files under your database area on both target and original master server and ensure they are the same.  Nearly everything else outside of database/catalog can be rebuild by re-installing NBU in 1 form or another.

As far as copying over the database from 1 machine to another; the basic tool available to you would be the catalog backup and recovery.  This works only on same O/S type.

However, if you have access to a SAN, or NAS, it is possible to also copy the files over as well.  For example, in windows, if the OS type is exactly the same and the drive letter is to remain the same, you can pretty do this (highlevel), install NBU into the same drive letter and same folder as the original machine.  Then disable NBU services from starting, reboot.  Next copy the entire VERITAS folder off the original master to the new master.  Re-enable the NBU services, and start them up.  This has been known to work IF the 2 machines/hardware are 99% binary/registry compatible!  This means if your original machine is 32bit windows 2003, your new machine cannot be windows 2008 64bit for this method to work without complications.

1 more thing people fail to do, your hostname/IP for the most part cannot be changed.  Usually you can change the IP, but the master's hostname should not be changed. 

Do not be tempted to ever spoof the hostname via drivers\etc\hosts file!  I've seen customer tried this from NBU 4.5, where it work without issues, then about 5 years later, all sorts of issues occurs. 

Stuart Green's picture

How to move NetBackup from one drive letter to another
http://seer.entsupport.symantec.com/docs/325722.htm
(Applicable to Master Server on Windows only)

This might be handy if after all the changes and the move to a new server you decide to move the software from C drive to another (larger) drive.

Thanks for the steps g_man

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

badri's picture

 Hi before migrating you should always do a catalog consistency check using NBCC to find all bad images.