On Jul 24, 2010, at 2:35 AM, Preston de Guise wrote:

> On 24/07/2010, at 12:06 , wallace88 wrote:
> 
>> My personal peeve is hearing people say that deleting /nsr/tmp is the 
>> solution when backups or jukebox is hung...  that NetWorker will work ok if 
>> you just clear tmp regularly.  If you think about it, how do you know that 
>> deleting tmp solve the issue, and not restarting the NetWorker application? 
>> Isn't this similar to the windows solution of rebooting Windows will fix 
>> everything?
> 
> It's easy to come to this conclusion in situations where multiple restarts of 
> the NetWorker services do nothing, yet a stop, clear-out of /nsr/tmp and a 
> restart of NetWorker does achieve the intended goal.
> 
> While it's certainly true that in some instances a simple restart might be 
> sufficient to clear issues, it's also the case that there are various state 
> files in /nsr/tmp which you will sometimes find yourself needing to erase in 
> order to restore functionality after particularly unpleasant hardware issues. 

Is there any reason not to clear out /nsr/tmp as part of a normal NetWorker 
server restart process? I don't think so. I have noticed over time that 
/nsr/tmp gets very large. As a result, I just delete it each time I restart 
NetWorker, which for me is once every week or two.

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