If it is just migrating the existing NW server to a new hardware, a very simple process could be followed:
1. Stop NW on old hardware. 2. Make a copy of /nsr folder on any disk...just copy-paste. 3. Shutdown this server. 4. Power on the enw hardware with same OS(including SP etc.), IP & hostname as existing server. 5. Install same NW version as was used on the earlier hardware. 6. Stop NW services on new hardware. 7. Copy the old servers nsr folder to the new server overwriting the nsr folder here. 8. Start services. All resources, media & index entries would be there as it is. 9. All you might need to redo is configure your backup devices.
It is recommended to maintain the same OS & NW versions when doing anything of this type & also the same IP & hostname. If you want to change hostname as well, I would suggest first complete the above with same hostname for the backup server & then use the change host name process to change the hostname.
Also, you can have a savegrp -O kind backups from the original hardware as a precaution. I find this as the simplest way and it works. All Networker actually needs is the existing /nsr/res,/nsr/index & /nsr/mm folders i.e. resources, indexes and media database. You can even selectively copy only these.
Be sure about OS etc. sicne if you plan to change OS, you need to follow some other processes.
Just remember to rehost your licenses once you move to the new hardware. What Anuj mentiones will work if you are not changing the hostname. If the host name is changing, you might want to do a bootstrap recovery using the mmrecov command.
For the error with nsrck, was the bootstrap that you restored backed up after the index backup? You might also want to ensure that the system time and timezone on both boxes are in sync.
Copying across the indices is fine as long as Networker is shutdown on both ends while you are copying.
I agree - since this is the same OS just copy over dbs. Most likely you will need to reconfigure library or in best case just adjust control port if order of devices is the same, but reconfiguring it is the safest bet.
I have some concern on this. My situation also lies in the same way. The existing setup is solaris 8, networker 7.3.2 network edition, with all proper licenses. The requirment is to have Redhat enter prise linux 4 update 5 with networker 7.3.2 power edition on a new server.
1. What are the procedures i should follow for the new server, after getting re-host for licenses. will the licenses on the solaris server, will work if i want to do some restoration ?
2. Is it possible, to do the restoration from the newly configured setup ie,networker on Linux platform?
amediratta
2 Intern
•
2K Posts
1
December 6th, 2008 00:00
1. Stop NW on old hardware.
2. Make a copy of /nsr folder on any disk...just copy-paste.
3. Shutdown this server.
4. Power on the enw hardware with same OS(including SP etc.), IP & hostname as existing server.
5. Install same NW version as was used on the earlier hardware.
6. Stop NW services on new hardware.
7. Copy the old servers nsr folder to the new server overwriting the nsr folder here.
8. Start services. All resources, media & index entries would be there as it is.
9. All you might need to redo is configure your backup devices.
It is recommended to maintain the same OS & NW versions when doing anything of this type & also the same IP & hostname. If you want to change hostname as well, I would suggest first complete the above with same hostname for the backup server & then use the change host name process to change the hostname.
Also, you can have a savegrp -O kind backups from the original hardware as a precaution. I find this as the simplest way and it works. All Networker actually needs is the existing /nsr/res,/nsr/index & /nsr/mm folders i.e. resources, indexes and media database. You can even selectively copy only these.
Be sure about OS etc. sicne if you plan to change OS, you need to follow some other processes.
Hari5
443 Posts
1
December 6th, 2008 01:00
For the error with nsrck, was the bootstrap that you restored backed up after the index backup? You might also want to ensure that the system time and timezone on both boxes are in sync.
Copying across the indices is fine as long as Networker is shutdown on both ends while you are copying.
ble1
4 Operator
•
14.4K Posts
0
December 7th, 2008 12:00
I agree - since this is the same OS just copy over dbs. Most likely you will need to reconfigure library or in best case just adjust control port if order of devices is the same, but reconfiguring it is the safest bet.
vijayscsa
77 Posts
0
December 9th, 2008 22:00
I have some concern on this. My situation also lies in the same way. The existing setup is solaris 8, networker 7.3.2 network edition, with all proper licenses. The requirment is to have Redhat enter prise linux 4 update 5 with networker 7.3.2 power edition on a new server.
1. What are the procedures i should follow for the new server, after getting re-host for licenses. will the licenses on the solaris server, will work if i want to do some restoration ?
2. Is it possible, to do the restoration from the newly configured setup ie,networker on Linux platform?
Thanks in Advance....
ble1
4 Operator
•
14.4K Posts
0
December 11th, 2008 14:00