Hello,

I'm using this procedure and NetWorker can see new path, but when I want to list content of CFI there is no records.

nsrls

0 records required 0 KB

is currently 100% utilized

When I return to old path (delete new path from Globals 2 of 2), nsrls shows me 586014 records requiring 70 MB. It seems that NetWorker clear my CFI afther I move it to new location.

Regards,

Pawel

Hello!

Per EMC KB article esg66605 ( http://solutions.emc.com/EMCSolutionView.asp?id=esg66605&usertype=C ):

Moving a client file index

You can move a client file index from its current location to a new location. For example, if the size of the client file index is too large, you can move it to a location with more space.

To move an existing client file index:

1. Ensure that no backup is currently running on the NetWorker server.
2. Copy the client file index from its current location to the new location. For example:
   

   • For Windows, copy \index\jupiter to
     \indexes\jupiter.
     

   • For UNIX, type this line at a command prompt:
     cp -rp /nsr/index/jupiter /new_location/indexes
     

3. Update the Index Path attribute of the Client resource to point to the new location of the index. See the "Changing the client file index location for an existing client" section above

I hope this helps!

Mark

OK - try using nrsck L-7 against the new database location and see if that helps.

I

Hi Mark,

nsrck -L7 will restore the Client File Index from Volume

I think you meant to say: nsrck -L6 Client_Name

Followed by: nsrim -X

Regards,

Mustafa