In regard to: [Networker] /nsr/index Cleanup?, Sean Smith said (at 1:31pm...:
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?
I'm not certain whether you're missing anything in the manuals -- I
wouldn't be surprised if this is not covered, but it has been a while
since I re-read the Admin Guide.
When deleting a client, NetWorker has always erred on the side of caution,
leaving behind the client index directory, in case you want to add the
client back (using the same client id!) at some point.
If you know you don't need the client indexes, just remove the directory
after the client is deleted. Out of habit, I've stopped and restarted
NetWorker after cleaning up client index directories, but I don't think
that's even needed anymore, if it ever was.
A few recent versions of NetWorker have had a rather unfortunate bug,
where nightly processing would sometimes hang when encountering
/nsr/index/<client> directories for clients that don't exist. I don't
know if 7.5.1 had that issue, but I know some of the 7.4.x releases did.
It appears that 7.5.2 has that particular issue fixed.
Tim
--
Tim Mooney Tim.Mooney AT ndsu DOT
edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
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
|
