|
Re: [Networker] Save shutdown failed
2008-05-30 11:03:05
On May 30, 2008, at 10:53 AM, Vince Howard wrote:
Hi Fazil,
Is it possible that you are running into resource conflict, busy
server
during full backups, what happens if you run FULL schedule on a trial
bases with extra v switches cmd line, during weekday (assuming the
full
are over the weekend) ?
I tried running a full backup of the client during the week, when it's
quieter, and it worked fine, so you may be onto something. Thanks.
I had the same problem with a Windows client a couple of weeks ago. I
did a search on PowerLink's knowledgebase for "shutdown failed" and I
found exactly the same problem there with a solution that worked for
me. The solution was to delete the client entry, then go into /nsr/
indexes and delete the index directory for that client, then recreate
the client entry in the NetWorker Management Console, and if
necessary, recover the indexes for that client via nsrck -L7. This
worked fine for me and since this was a new client, I didn't bother
with nsrck -L7.
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
|
|
|
