The only supported method for moving a client index to another location is uasm. A word of warning to those who are not familiar with uasm...uasm is difficult to use! The uasm command is log 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 haw to move an index is with an example. IN the example, we will move the following index:
Step 1: Run an "nsrck -F client_name" command on the client index you are preparing to move. This will ensure that the client index is "clean".
Step 2: 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 ffrom a command prompt on the NetWorker server:
Step 3: Make sure thet NetWorker server is idle, then shutdown the NetWorker processes. To stop NetWorker services on a Windows 200 NetWorker server, click on Start > Programs > Administratiive Tools > Services. Right-click on the "NetWorker Backup nd Recover Server" entry, then click on Stop.
Step 4: From the NetWorker server, start a command prompt
Step 5: Change directories to the directyory where the NetWorker binaries are located, for example:
cd \Program Files\Legato\nsr\bin
Step 6: Enter the following command very carefully:
uasm -si "c:\program files\legato\nsr\index\alpha99" | uasm -rm "c\\program files\legato\nsr\index\alpha99=d:\index\alpha99"
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.
Step 7: Using Windows explorer, browse to the new index directory and make sure the files were actually copied.
Step 8: Using Windows explorer, rename the "old" directory. In this example, we entered the following commands to rename the old index directory:
Step 9: Restart the NetWorker service
Step 10: From the NetWorker Administration program, edit the client configuration for the client whose index was moved. CHange the "Index Path" entry to point to the new index location.
Step 11: Run an "nsrck -F client_name" command on the client index you just moved to make sure all is well. The nsrck command should reflect the new location.
Step 12: After you run the next backup of the affected client, you can delete the old (renamed) client index directory.