Hello,

>From my experience ( from the bad old 6.x days to 7.4.4 presently ) Networker 
>will only remove the client from the resource db. It will not remove the 
>/nsr/index directory containing the clients indexes. It has been debated 
>multiple times over the years whether or not this was a built in safety 
>feature. I have it on good authority ( from an Engineer who has been with 
>Legato/EMC for the past 16 years working exclusively on Networker ) that this 
>was actually an oversight.

There have been several bugs over the years where the presence of a client 
sub-directory in /nsr/index without a corresponding entry in the resource db 
has caused problems of various sorts. Most of those have been cleaned out IIRC. 
The chief problem that still exists is when nsrd runs through the "Enabler" 
checks. Networker verifies licensing/enablers via the resource db client 
entries, but then it uses the total number of sub-directories in /nsr/index to 
determine actual usage. So for every retired client for which a sub-directory 
still exists in /nsr/index, networker is allocating a license even though the 
client isn't being backed up.

In 7.4 they tried to work around this behavior by changing the client license 
model, but in working with the Eng from Legato EMC, I was able to demonstrate 
that networker was still allocating licenses for retired clients and causing 
backups to be skipped in an environment where we have only 284 clients and 325 
licenses.

The way we usually remove the client indexes ( when necessary ) is:

Delete client from the NMC/GUI
verify networker inactivity "prstat -a" ( or the windows equivalent )
nsr_shutdown
cd /nsr/index
rm -rf clientxyz
/etc/init.d/networker start

We have followed this procedure because we have found that in various patch 
iterations, removing the sub-directory before the client is deleted from the 
resourcedb can cause all kinds of mayhem the worst of which would be when nsrd 
determines that it needs to dump the indexes and rebuild everything from 
scratch. ( over 72 hours on a system with a 500GB /nsr/index )

Your mileage may vary based on the patch revision you are currently running.





________________________________
From: Sean Smith <seansmith AT UPS DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Sent: Tue, March 23, 2010 10:31:56 AM
Subject: [Networker] /nsr/index Cleanup?

We're running 7.5.1 on Linux x86.  We have a number of old clients listed as 
directories under /nsr/index, and although we do a little index maintenance on 
a nightly basis, these old client directories aren't cleaned up (deleted) after 
a client is removed from the NetWorker configuration.  Am I missing something 
in the manuals or does this matter at all?

Thanks!
Sean

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
[email protected] you have any problems with this list. 
You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER




To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER