migrating NBU clients to new master server?
Hi gang,
I'm planning to implement a new NBU environment (the old one is messy and needs to be migrated). I don't care to keep the catalog, so I'm planning on just building a new Master (cluster) and new (non-clustered) media servers. i will migrate the clients from the old one to the new one and eventually shutdown the old one.
I was wondering if there is an easy way to migrate clients to the new master server without having to touch each one?
is this something that can be scripted via registry edits or something? is it as simple as just editing:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Server
? (assuming the new server is configured much as the old one in terms of ports and so on)?
suggestions? ideas?
thanks,
ADDODD
Comments
Yes thats basically it
And recycle the NetBackup Client Service
Media Servers you have to do a bit more editing of registry.
EMM Server entry etc.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
cool!
i'll be building new master and media servers so they'll all be clean. i just want to repoint the existing clients to the new master and media servers... so i expect that if:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Server = old-master1 old-media1
then all i have to do is change it to:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Server = new-master1 new-media1 new-media2
* restart the NBU client service
and that's it?
cheers,
ADDODD
One word of caution
I've done this before & have ran into problems difficult to pinpoint. Here's an example:
Moving 1 windows media server from 1 NBU master to another.
On the new NBU master I created the entries on the (Unix Master) bp.conf file - like normal.
Got the windows media server backing up as a network client - Great!
Ran the nbemmcmd addhost blah-blah-blah to creat an entry for the Windows media server on the new NBU EMM (& master in this case).
Did the registry hack to set the correct EMM server.
Cycled NBU on the Windows media server
Used the java console Drive configuration wizzard to scan for devices - all confiugred correctly - Great!
Did some small file system backup tests, all worked perfectly.
Now when the trouble starts.
At anytime during a DB or file system backup, I started seeing status 40's popping up & the backups failing.
Everything looked okay, but I/O errors were causing all kinds of issues when trying to use the media servers own tape drives.
I can tell you I opened a case with Symantec about this. The basic deal was while the steps I did might work, there's a bunch of other little checks going on and this was not the "preferred" way to move a Windows media server from 1 Master/EMM server to another. The correct way was to remove the NBU software & reinstall it using the correct NBU master & EMM server during the install. I did this and the issues were gone. Moving Unix media servers is a bit easier by editing the bp.conf file.
Don't cheat yourself a few minutes of doing the removal/reinstall for the NBU software only to spend hours hacking things around and trying to figure out why your having goofy issues not explainable with good logic.
I hope this helps you.
if you're migrating just
if you're migrating just clients, then its easy. As there are no critical information stored on clients that could prevent a successful migration.
This is completely different if you're doing a MEDIA SERVER. Often you need to decomission one from the old master, then recomission it.
Then process to recomission involves hunting down configuration, and deleting any references to point it to the old master and old media servers. This often takes so long that it's simply NOT WORTH IT. It often (10-out-of-10) FASTER to just remove the media server application, delete the registry, and delete the directories, then re-install to ensure a CLEAN configuraiton.
Also if you install NBU media server under master it automatically connects to that master and setup EMM for you. The 10-15 minutes it takes for you to remove the media server, and re-install would proft you hours of cleanup and messing with EMM on the new master. At the end, you'd wish you'd just remove and re-install.
Additional, BEFORE YOU even remove the application MAKE SURE you properly decomission that media serve. most commands to decomission requires that original media server to be alive to run commands against. Once you remove it and recomissioned it, these commands will fail for obvious reasons.
Sure you can contact support to clean up, but this clean would also cost you a few days utilizing nbcc and nbccr. If you do it right to begin with, it saves you this much time.
Just load Client Properties in Old Master and Add New Server
Just Select All Client in Old Master and load their Properties; in the properties goto Servers->Additional Servers->Add New Master server
Select that New server in the additional server frame; and make that server as Master Server. that's it :-)
Check and let us know if you face any issues.
This is Very Easy Way, Only one step Process :-)
Thanks, Karthikeyan Sundaram.
meida server
if you are going to have a new media server you need to add it in the media server window as well.
so if your new master is also a media server.
open the client properties on the clients ( you can do 10 or so at once) add the media server name in the top server window and click make master. Then add it to the bottom for the media server, apply, OK,
rinse and repeat for all the other clients doing 10 at a time.
I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows
Would you like to reply?
Login or Register to post your comment.