Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How do I properly remove a client to free up index space?

Status
Not open for further replies.

jesseroscoe

Technical User
Jul 14, 2005
26
US
Hi,
I got warning messages over the weekend that my filesystem containing my client file indexes was getting full. Upon inspection, I have several machines that have been removed as clients but their index files remain. I would like to remove all index files pertaining to these ex-clients without disturbing the media database. Is it okay to just delete the /nsr/index/client_name directories to free up space, or do I need to do it through Networker commands? If I have to use commands, what is the syntax I would use that would keep me from having to remove them by ssid, one at a time?

Thanks,
Kevin
 
Hello,

Check indices before with a nsrck -Ln to see if NW knows these clients.

Try also to perform a nsrim -X

And after you can delete directories (I always stop NW before, but it may be not necessary).
 
Everything I have read from Legato regarding how to reduce the size of the client file index says to use the "nsrmm" command. If you pass it a -P, it will not remove entries from the media database, so the indexes will still be recoverable with the command "scanner". I wrote a couple scripts to write all of the SSIDs to a file, then run "nsrmm -d -P -S" against the file. The problem is that the /nsr filesystem doesn't seem to be getting any smaller unless I omit the -P option, which then makes the indexes unrecoverable. Is there something I'm missing? I assumed the client file indexes included the data in /nsr/index/client_name/, which is what is using all of my disk space.
 
nsrmm is not intended to work on CFI, its first action is against the media database : suppressing volumes or savesets...

If you want to suppress indexes of a 'still-in-use' client to gain size, you can perform nsrim -l (which removes the oldest full save set), and so on.

But note that indexes will still be recoverable (or re-buildable) by a 'scanner' command against the volume as long as the volume is not relabelled.

So if you have clients which are not known by NW, you can delete the /nsr/index/xxxx of these clients.
 
Yes, it is save to remove an obsolete CFI directory. This is also necessary to release a client license. However, before you do anything else, carefully investigate the /nsr file system.

This message is a leftover from the very first NW releases - it will pop up because NW can not copy the largest file index anymore to the SAME partition to compress the database. It will even pop up although you still have GBs of empty space on this partition.

Since the new (NW 6.0) database system for the CFI, no compression is necessary any longer - it is not even possible because the CFI files for expired save sets will be deleted immediately. Unfortunately, the message will still appear.

If you really have a space problem, then it is better to relocate a certain CFI directory.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top