How to Move 160 backup policies from one networker server 7.6 to other
networker server with 8.1
HI!!
I need to move 160 backups policies (and groups) from my ancient 7.6 networker server to my new 8.1 networker server, is there a process that i have to follow? whats about the 160 clients?? they need to be upgraded?? or there isn´t no hope to creat all the new 160 policies in the new server.
The easiest way I would have seen is to add the new NW server with the same name and same NW locations and run the standard DR procedure. I would not expect a general problem except for the auth codes.
Obviously, this option does not exist any more.
The only way I see now is to export the export the resources and to prepare a text file which will create the new resources via the command ...
Copying the /nsr/res/nsrdb over to the new backup server should work as well !! You might have to create the client instance for the new hostname manually using nsradmin command.
Why you don't use the DR procedure, it's easer then manual migrate all clients and policies.
Just grant the consistency state of Networker Database simulate a Hardware failure and then "restore" the database to the new host with same name same IP address.
If you are not bothered about old Backups for clients to be migrated go for creating clients with nsradmin option, If you might want history data to be recovered for clients in question go with Disaster. Choice is yours. All the best do let us know what option u have choosen.
bingo.1
1 Rookie
•
2430 Posts
729
1
Posted December 17th, 2014 12:00
The easiest way I would have seen is to add the new NW server with the same name and same NW locations and run the standard DR procedure. I would not expect a general problem except for the auth codes.
Obviously, this option does not exist any more.
The only way I see now is to export the export the resources and to prepare a text file which will create the new resources via the command ...
nsradmin -i input_file
- delete the resource ID lines
- only create the attributes needed
Test this first before you run a batch job ;-)