Re: [Networker] 7.4.5 nsrck hangs
2009-09-04 18:58:15
On 05/09/2009, at 08:45 , Francis Swasey wrote:
On 9/4/09 5:10 PM, Roberta Gold wrote:
When I remove a client, I also move the client index to a different
directory. Once my advertised retention time is up, I remove any
remaining media index entries for those clients from the volumes
that are onsite. The only remaining entries will be for the DR
volumes that are offsite. I wish NetWorker had a "NUKE CLIENT"
option in the NMC that would totally cleanup after a client.
Yes, I wish that as well. I had seen a post here describing using
nsrmm to delete the client index when deleting a client. So, I also
have removed the /nsr/index directories for these clients that are
causing nsrck to get stuck.
Personal preference of course, but I for one disagree. NetWorker's
entire strategy (e.g., dependency checking, etc.) is about maximal
data protection. If you want a product that just goes and blows away
data, pick a less trustworthy backup product... Working with support
partners as I have been for the last 10+ years, I can honestly say
that I routinely have customers who are told to decommission clients,
go on to also delete the indices, and then have an urgent recovery
request come in for them. I.e., I'd much prefer NetWorker not make
deleting client indices easier than it already is :-)
Cheers,
Preston.
--
Preston de Guise
"Enterprise Systems Backup and Recovery: A Corporate Insurance Policy":
http://www.amazon.com/Enterprise-Systems-Backup-Recovery-Corporate/dp/1420076396
http://www.enterprisesystemsbackup.com
NetWorker blog: http://nsrd.wordpress.com
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
|
|
|