Mike Allmen posted (16 May
2000) the following procedure from Legato:
We recommend, 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:
-
savegrp -O on the server. This
will backup all the indexes and bootstrap to one tape.
-
shut down the current nsr server
-
Move the tape devices to the
new server
-
Give the new server the same
name as the old server. This may require them to disconnect the new server
from the network
-
do a mmrecov on the new server
using the tape from step 1
-
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.)
-
shutdown networker
-
Rename the server to it's new
name
-
Reboot the server -- Networker
should start
-
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.
-
Delete the old server from the
new server's client list.
-
Make the old server an alias
of the new server.
-
Stop networker.
-
Rename the /nsr/index/<old_server>
directory to /nsr/index/<new_server> NOTE: You will need to delete the
/nsr/index/<new_server> directory before renaming. NOTE: DO NOT copy
the index from one directory to the other use move or rename.
-
Restart Networker.
-
When the indexes are finished
cross-checking you can delete the aliases for the old server.
-
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.
You have 15 days from the time
of the move to do this or Networker will disable its self.
Registering New Server:
-
Shut down NetWorker on the source
server.
-
Start the NetWorker daemons
on the target server. The following messages appear on the destination
server:
new_server syslog: NetWorker Server: (notice) started
new_server syslog: NetWorker Registration: (notice) invalid auth
codes detected.
new_server syslog: The auth codes for the following licenses enablers
are now invalid.
new_server syslog: The cause may be that you moved the NetWorker
server to a new computer.
new_server syslog: You must re-register these enablers within 15
days to obtain new codes.
new_server syslog: License enabler # xxxxxx-xxxxxx-xxxxxx (NetWorker
Advanced/10)
Register your new NetWorker
server. After moving NetWorker from one computer to another, you have 15
days to register the new server with Legato.
To register the new NetWorker
server, follow these steps:
-
Start the GUI version of the
NetWorker Administrator program using the following command: # nwadmin
-
Open the Registration window
by selecting registration from the Administration pull-down menu of the
main Administration window.
-
Select Tabular from the View
pull-down menu to display the tabular view of the window.
-
Select print from the File pull-down
menu to send a copy of the Registration window to a printer, or select
Save from the File pull-down menu.
-
Fax this printout along with
your name, company and telephone number to Legato at (650) 812-6220.
-
Legato will send you a NetWorker
Host Transfer Affidavit which you must complete and return to Legato. When
Legato receives the completed affidavit, you will receive a new authorization
code. You must enter the new authorization code into the Authorization
field of the Registration window.