Hi all.

I'm planning a NetWorker update from 7.5.1 to either 7.5.2 or the new 7.5.3.

The part of the update that takes the most time is running nsrck -L6. It 
takes 9 hours on our 90GB index folder. That's a very long down time for 
our environment, if we're required to let the NetWorker system be 
completely idle during the nsrck -L6.

Is there a workaround so the update does not need such a long downtime? is 
it ok to run the nsrck -L6 after the update? or is it ok the have some 
backup / restores done durint the nsrck -L6 ?

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