Solved!
Go to SolutionD2
DeaconZ28-2015
1 Rookie
•
252 Posts
0
976
January 7th, 2009 17:00
starting over
If I wanted to build a brand new Networker server instead of just upgrading my current one, what is the best practice?
I don't need to save any of my custom schedules or notifications (I only have a few anyway).
I just need to make sure the client data I have on tape and disk can still be read.
Can I just add a new server to my console and copy over the indexes, then gracefully take down and remove the old server from my enterprise?
What about the clients themselves? What's the best way to move them over?
I don't need to save any of my custom schedules or notifications (I only have a few anyway).
I just need to make sure the client data I have on tape and disk can still be read.
Can I just add a new server to my console and copy over the indexes, then gracefully take down and remove the old server from my enterprise?
What about the clients themselves? What's the best way to move them over?
- I am presuming that you want the following;
1. existing configuration from the old server
2. client file indices from the old server
3. media database from the old server
Question is will your new server have the same OS and host name as the old one? If so, the whole thing is quite simple.
1. Install NW on the new server.
2. Stop services on both servers.
3. Copy across the mm, index and res directories from the old server to the new one. These directories would be in /nsr if your server is on Unix or Linux and in \nsr if your server is on windows (for eg., C:\Program Files\Legato\nsr)
If your are changing either the OS or the hostname, you would need to do a full bootstrap and index restoration from tape.
1. Backup the bootstrap and indices from the old server. You could use savegrp -O to do this.
2. Use mmrecov to restore the bootstrap from the tape on the new server.
3. Use nsrck -L7 to restore the client file indices from the tape on the new server.
As for the clients, all you might need to do is to change the entry in the servers file on the client (this will be in the res directory) and restart the services on the client. Goes without saying that you need to ensure that network lookup between the clients and the new server using hostname is ok. DeaconZ28-2015
1 Rookie
•
252 Posts
500
0
Posted January 8th, 2009 04:00
Thank you for your replies.
Basically what's happening is that the server I am using is being decommissioned soon and I am replacing with a new Win 2008 server.
I will use the same network name for the new one.amediratta
2 Intern
•
2014 Posts
500
0
Posted January 8th, 2009 18:00
When you change the hardware, the server host ID would change and therefore you need new authorization codes. Doing this is simple. You can either go to Powerlink and rehost your LAC No. or write a mail to licensing@emc.com with your base enabler code, old host ID & new Host Id and thye will provide you with new auth codes.
pgerke
35 Posts
500
0
Posted January 8th, 2009 12:00
On the original server:
--Before shutting down the old server and removing software, run a full backup.
--Run a full backup of the indexes and bootstrap to a tape in the Default pool.
--Printout the bootstrap information to use in restoring to the new server.
--Shutdown the old server.
On the new server:
--Connect the needed devices (it was a fibre channel tape library for me) to the new server.
--EMC then recommended a reboot of the server, but I think I neglected to do that step. Since everything was already connected and working in the OS, it wasn't a problem for me.
--Install NetWorker Server and add drives. The instructions called for configuring at least one device, but I configured the entire tape library and got it working.
--I then manually mounted the Default tape with the bootstrap and indexes. I couldn't use the normal mount because the new server didn't know about any volumes yet. I used the nsrjb -nlv -S slot -f device to mount it.
--I then recovered the bootstrap save set using mmrecov.
--I then stopped NetWorker on the new server and moved /nsr/res to /nsr/res.old and renamed the /nsr/res.R to /nsr/res, and then restarted NetWorker.
--Then I was able to recover the index by editing the client resource to all the new server to recover files from the old server. I used the recover command and the SSIDs of the indexes on the Default tape.
--Run nsrck -L6 to rebuild the indexes.
The only other thing I think I had to do was get the licenses moved over. i don't remember exactly how I did this, but I know I talked to EMC NetWorker licensing and the asked me for what they needed to get the information for what was licensed on the old server, and then sent me the code or codes I needed to authorize everything on the new server.
I hope that helps a little,
Paul