Backup Central

Hi all,

I have ZWC-Community-3.1.3-32bit installed on a Win 2003 server. The server is amanda 2.5.2p1 coming with Ubuntu 8.04, re-compiled as to use my own tar wrapper (I need SELinux attributes). Unfortunately, ZWC seems to crash regularly.

Symptoms:

- on the Ubuntu server, the log says
<snip>
FAIL dumper winsrv D:/Freigaben/ALL 20101120 1 [data timeout]
sendbackup: start [winsrv:"D:/Freigaben/ALL" level 1]
sendbackup: info BACKUP=pkzip
sendbackup: info RECOVER_CMD=Extract with zmanda windows client or unzip program
sendbackup: info end
PARTIAL chunker winsrv D:/Freigaben/ALL 20101120 1 [sec 4814.995 kb 15981504 kps 3319.2]
FAIL chunker winsrv D:/Freigaben/ALL 20101120 1 [cannot read header: got 0 instead of 32768]
FAIL driver winsrv D:/Freigaben/ALL 20101120 1 [too many dumper retry: "[request failed: timeout waiting for REP]"]
</snip>

- running amcheck on the Ubuntu server complains that winsrv timed out

- logging on winsrv, the services panel says that ZWCService is running

- trying to re-start ZWCService, Windows tells me that it was unable to stop the service, and now its marked as not running

- start ZWCService manually, and now amcheck on the Ubuntu box can contact winsrv.

Any idea what goes wrong here, and how I could debug and resolve the issue?

Thanks in advance,
Albrecht.

Windows client 3.1.3 has not been tested with 2.5.2p1 release.

Do you use maxdumps parameter in the dumptype?

Can you check the log files on the Windows Client?
http://wiki.zmanda.com/index.php/Zmanda_Windows_Client#Log_Files

thanks
Paddy

On Mon, Nov 22, 2010 at 11:41 AM, Albrecht Dreß <albrecht.dress < at > arcor.de> wrote:
Hi all,

I have ZWC-Community-3.1.3-32bit installed on a Win 2003 server.  The server
is amanda 2.5.2p1 coming with Ubuntu 8.04, re-compiled as to use my own tar
wrapper (I need SELinux attributes).  Unfortunately, ZWC seems to crash
regularly.

Symptoms:

- on the Ubuntu server, the log says
<snip>
FAIL dumper winsrv D:/Freigaben/ALL 20101120 1 [data timeout]
 sendbackup: start [winsrv:"D:/Freigaben/ALL" level 1]
 sendbackup: info BACKUP=pkzip
 sendbackup: info RECOVER_CMD=Extract with zmanda windows client or unzip
program
 sendbackup: info end
PARTIAL chunker winsrv D:/Freigaben/ALL 20101120 1 [sec 4814.995 kb 15981504
kps 3319.2]
FAIL chunker winsrv D:/Freigaben/ALL 20101120 1 [cannot read header: got 0
instead of 32768]
FAIL driver winsrv D:/Freigaben/ALL 20101120 1 [too many dumper retry:
"[request failed: timeout waiting for REP]"]
</snip>

- running amcheck on the Ubuntu server complains that winsrv timed out

- logging on winsrv, the services panel says that ZWCService is running

- trying to re-start ZWCService, Windows tells me that it was unable to stop
the service, and now its marked as not running

- start ZWCService manually, and now amcheck on the Ubuntu box can contact
winsrv.

Any idea what goes wrong here, and how I could debug and resolve the issue?

Thanks in advance,
Albrecht.




--
Amanda http://amanda.zmanda.com
ZRM for MySQL http://www.zmanda.com/backup-mysql.html

Am 23.11.10 02:26 schrieb(en) Paddy Sreenivasan:
Windows client 3.1.3 has not been tested with 2.5.2p1 release.

I know... but I use a bunch of production Linux boxes (with Ubuntu 8.04, SuSE and RHEL) and I didn't want to upgrade them all. And even *if* the 2.5.2p1 server sends crap to zwc, it shouldn't crash, right?

Do you use maxdumps parameter in the dumptype?

Yes:

<snip>
define dumptype zwc-compress {
global
auth "bsdtcp"
maxdumps 1
compress client fast
program "DUMP"
}

define dumptype zwc-compress-o {
global
auth "bsdtcp"
maxdumps 1
compress client fast
program "DUMP"
exclude "DSI*.zip"
}
</snip>

Can you check the log files on the Windows Client?
http://wiki.zmanda.com/index.php/Zmanda_Windows_Client#Log_Files

Umm. Last night the backup has been successful, and thus the logs of the previous crashed one are gone. I'll check again if the service shows the issue again...

Thanks, Albrecht.

Good to hear that the backup worked this time.

Of course, Windows client should not crash. If it happens again,
please do the following:

1. Remove "maxdumps 1" from the dumptype. We used to have this
problem. I think it is fixed but I would
prefer to avoid it since the default for maxdumps is 1.

2. Windows client uses VSS. Apply Windows 2003 VSS hot fix.
http://support.microsoft.com/kb/833167

thanks
Paddy