Moving a client index on a NetWorker server (UNIX/Linux)
The only supported method for moving a client index to another location is by using the
uasm command. A word of warning to those who are not familiar with uasm...uasm is difficult to use! The uasm command is long and cryptic. It is very easy to make a mistake when working with the uasm command.
Warning: Legato issued a white paper stating that client index files on NetWorker version 6.x servers could be moved using standard "move" commands rather than using uasm. However, I find that each attempted corrupted our NetWorker 6.01 indexes. The uasm technique described below works for NetWorker version 5.x and 6.x
The best way to show you how to move an index is with an example. In this example, we will move the following index from
- Run an
nsrck -F client_namecommand on the client index you are preparing to move. This will ensure that the client index is "clean".
- Create a new "top level" directory to hold the indexes. This is the location where you wih you move the index to. In this example, we entered the following commands on the NetWorker server:
cd / mkdir index
- Make sure thet NetWorker server is idle, then shutdown the NetWorker daemons. To stop NetWorker, enter the following:
- Enter the following command very carefully:
/usr/lib/nsr/uasm -si /nsr/index/charlie01 | \ /usr/lib/nsr/uasm -rm /nsr/index/charlie01=/index/charlie01Note: You may need to replace the path pointing to
uasmwith the appropiate path in your environment. Note: If he above command works properly, you will see absooltely no output from the command. If you receive any type of error, or prompts to overwrite files, hit CTRL+C to kill the command, then recheck you command syntax.
- Look in the new directory to make sure the files were actually copied.
- Rename the "old" directory. In this example, we entered the following commands to rename the old index directory:
# cd /nsr/index # mv charlie01 clarie01.old
- Restart the NetWorker server by entering:
# /etc/init.d/networker start
- From within the
nwadminutility, edit the client configuration for the client whose index was moved. Click on View > Details. Change the "Index path" entry point to match the new index location.
- Run an
nsrck -F clientcommand on the client index you just moved to make sure all is well. The
nsrckcommand should reflect the new location as shown as follows:
# nsrck -F charlie01 nsrck: checking index for 'charlie01' nsrck: /index/charlie01 contains 16483 records occupying 2750 KB nsrck: Completed checking 1 client(s)