Solarisx86 only client released. NW server not release yet.
Below are the some step which you will help in future.
I have recommended to you, as the only safe method for moving the indexes, that you backup the /nsr part of the directory tree on the old machine and then recover it on the new machine. This will be a "disaster recovery" using mmrecov. The reason for this is that many copy programs do not handle the database (index) files correctly. These files have empty places, where old records have been deleted andmany copy programs will insert blanks or nulls or compress the files, etc. resulting in index corruption. Keep in mind that the name of the new machine must be the same as the old machine, at least at first. After the transfer is done, you can go through the process of changing the name. The best way I've found to move from UNIX==>UNIX is to do this:
A.savegrp -O on the server. This will backup all the indexes and bootstrap to one tape.
B.shut down the current nsr server
C.Move the tape devices to the new server
D.Give the new server the same name as the old server. This may require them to disconnect the new server from the network
E.do a mmrecov on the new server using the tape from step 1
F.recover all indexes for all the clients (If the new server is going to have the same name of the old server skip to step 17.)
G.shutdown networker
H.Rename the server to it's new name
I.Reboot the server -- Networker should start
J.Update any client's servers files or nsrexecd -s options to reflect the new servers name. If the new server will not be having the indexes as the old server skip to step 17. If the old server will be a client of the new server, skip to step 17.
K.Delete the old server from the new server's client list.
L.Make the old server an alias of the new server.
M.Stop networker.
N.Rename the /nsr/index/ directory to /nsr/index/ NOTE: You will need to delete the /nsr/index/ directory before renaming. NOTE: DO NOT copy the index from one directory to the other use move or rename.
O.Restart Networker.
P.When the indexes are finished cross-checking you can delete the aliases for the old server.
Q.Complete the host transfer procedure from Customer Service to get a new authorization code if the IP address of the new server is different from the old server.
Actually, the quickest way is to export nsrdb and import it on new server. You do the same for index and mdb (I believe index you can just copy as it is endian agnostic). Since both Linux and Solaris x86 are small endians, copy only of mdb should be possible too. Of course, it should be tested first. If all works, some slight adjustments will be needed for paths eventually and license host transfer.
This turns out to be many of the steps above are correct and will work. EMC lists this activity as a "migration" and to be supported we have to contract EMC to perform. Otherwise you use a Disaster Recovery procedure after installing Networker on the new hardware following their Disaster Recovery guide.
bingo.1
2.4K Posts
0
December 5th, 2013 07:00
Are you sure ?
To the best of my knowledge, a NW server for Solaris x86 has never been released.
Besides that, you may work - i do not know whether the NetWorker Procedure Generator will tell you details.
For sure you need to do some adjustments.
At least you need new license and authorization codes.
MoinMansuri
2 Intern
•
147 Posts
1
December 9th, 2013 04:00
Hi,
I have recommended to you, as the only safe method for moving the indexes, that you backup the /nsr part of the directory tree on the old machine and then recover it on the new machine. This will be a "disaster recovery" using mmrecov. The reason for this is that many copy programs do not handle the database (index) files correctly. These files have empty places, where old records have been deleted andmany copy programs will insert blanks or nulls or compress the files, etc. resulting in index corruption. Keep in mind that the name of the new machine must be the same as the old machine, at least at first. After the transfer is done, you can go through the process of changing the name. The best way I've found to move from UNIX==>UNIX is to do this:
A. savegrp -O on the server. This will backup all the indexes and bootstrap to one tape.
B. shut down the current nsr server
C. Move the tape devices to the new server
D. Give the new server the same name as the old server. This may require them to disconnect the new server from the network
E. do a mmrecov on the new server using the tape from step 1
F. recover all indexes for all the clients (If the new server is going to have the same name of the old server skip to step 17.)
G. shutdown networker
H. Rename the server to it's new name
I. Reboot the server -- Networker should start
J. Update any client's servers files or nsrexecd -s options to reflect the new servers name. If the new server will not be having the indexes as the old server skip to step 17. If the old server will be a client of the new server, skip to step 17.
K. Delete the old server from the new server's client list.
L. Make the old server an alias of the new server.
M. Stop networker.
N. Rename the /nsr/index/ directory to /nsr/index/ NOTE: You will need to delete the /nsr/index/ directory before renaming. NOTE: DO NOT copy the index from one directory to the other use move or rename.
O. Restart Networker.
P. When the indexes are finished cross-checking you can delete the aliases for the old server.
Q. Complete the host transfer procedure from Customer Service to get a new authorization code if the IP address of the new server is different from the old server.
ble1
4 Operator
•
14.4K Posts
0
December 9th, 2013 12:00
Actually, the quickest way is to export nsrdb and import it on new server. You do the same for index and mdb (I believe index you can just copy as it is endian agnostic). Since both Linux and Solaris x86 are small endians, copy only of mdb should be possible too. Of course, it should be tested first. If all works, some slight adjustments will be needed for paths eventually and license host transfer.
gmsmith1
4 Posts
0
February 5th, 2014 10:00
This turns out to be many of the steps above are correct and will work. EMC lists this activity as a "migration" and to be supported we have to contract EMC to perform. Otherwise you use a Disaster Recovery procedure after installing Networker on the new hardware following their Disaster Recovery guide.