Backup Central

Fo the past few days, one of the Windows 2000 servers on my nightly backup
schedule is failing. This server gets a full backup every night with about
130GB of data. The savegroup report says "5 retries" for this server. It
only backs up one directory on this Windows server. After the savegroup
stops, the backup for this particular server continues writing to tape.

The NetWorker server is version 7.1.3 under Solaris 9. The version of
NetWorker on the Windows server in question is also 7.1.3.

Does anyone have any suggestions on how to resolve this issue? Why would
the save still be running (as indicated in nwadmin), but I cannot find
anything about it in /nsr/tmp and the savegroup that controls this
server's backup reports that it finished the backup?

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Hi Stan

You might try a manual backup of this system, perhaps using the save
command, perhaps in debug mode. Maybe that would show more information
about whatever is causing the retries and mis-communication about whether
the save is truly done.

Hope this helps!
tl

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of Stan Horwitz
Sent: Tuesday, April 05, 2005 2:42 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Strange failure with a Windows backup

Fo the past few days, one of the Windows 2000 servers on my nightly backup
schedule is failing. This server gets a full backup every night with about
130GB of data. The savegroup report says "5 retries" for this server. It
only backs up one directory on this Windows server. After the savegroup
stops, the backup for this particular server continues writing to tape.

The NetWorker server is version 7.1.3 under Solaris 9. The version of
NetWorker on the Windows server in question is also 7.1.3.

Does anyone have any suggestions on how to resolve this issue? Why would
the save still be running (as indicated in nwadmin), but I cannot find
anything about it in /nsr/tmp and the savegroup that controls this
server's backup reports that it finished the backup?

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

On Tue, 5 Apr 2005, Terry Lemons wrote:

Hi Stan

You might try a manual backup of this system, perhaps using the save
command, perhaps in debug mode. Maybe that would show more information
about whatever is causing the retries and mis-communication about whether
the save is truly done.

Hope this helps!

Thanks. That's a good idea Terry. Before I do that, I am going to see
what happens by activating the verbose option in the group resource.
There are only two servers in this group so it should be informative.

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu