Hi,
That is all what your sendbackup.debug file contains?
no line telling dump reached 100% ?
and no finishing line from sendbackup?
Then your dump-process is dying whitout message after 43.03% of the
Backup.
am i correct that this is a linux-box?
then i would recomend switching to tar for the backup's, as dump for
ext2/3 is known to be problematic with active (mounted) filesystems.
Christoph

Ranveer Attalia schrieb:
Sorry
I've made this abit confusing to read. By server's I meant the actual
machines but you are correct, I have added 2 more clients. For example,
the client tsslin1 /export/mansun1_telco has failed with the timeout
error and I've checked the sendbackup log file on tsslin1 itself. Below
is the whole content of the sendbackup log file and doesnt seem to give
me any errors and appears to be dumping fine...



FAILURE AND STRANGE DUMP SUMMARY: tsslin1 /opt lev 0 FAILED [data timeout] tsslin1 /export/mansun1_telco lev 0 FAILED [data timeout]


sendbackup.20040812055906.debug sendbackup: debug 1 pid 12551 ruid 33 euid 33: start at Thu Aug 12 05:59:06 2004 /opt/amanda/libexec/sendbackup: version 2.4.4p2 parsed request as: program `DUMP' disk `/export/mansun1_telco' device `/export/mansun1_telco' level 0 since 1970:1:1:0:0:0 options `|;auth=bsd;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.37029 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.37030 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.37031 sendbackup: time 0.000: waiting for connect on 37029, then 37030, then 37031 sendbackup: time 0.004: stream_accept: connection from 193.195.219.173.58139 sendbackup: time 0.006: stream_accept: connection from 193.195.219.173.58140 sendbackup: time 0.008: stream_accept: connection from 193.195.219.173.58141 sendbackup: time 0.008: got all connections sendbackup: time 0.031: dumping device '/dev/vg01/mansun1_telco' with 'ext3' sendbackup: time 0.031: spawning /sbin/dump in pipeline sendbackup: argument list: dump 0usf 1048576 - /dev/vg01/mansun1_telco sendbackup: time 0.032: started index creator: "/sbin/restore -tvf - 2>&1 | sed -e ' s/^leaf[ ]*[0-9]*[ ]*\.// t /^dir[ ]/ { s/^dir[ ]*[0-9]*[ ]*\.// s%$%/% t } d '" sendbackup: time 0.357: 93: normal(|): DUMP: Date of this level 0 dump: Thu Aug 12 05:59:06 2004 sendbackup: time 0.359: 93: normal(|): DUMP: Dumping /dev/vg01/mansun1_telco (/export/mansun1_telco) to standard output sendbackup: time 0.368: 93: normal(|): DUMP: Exclude ext3 journal inode 8 sendbackup: time 0.407: 93: normal(|): DUMP: Label: none sendbackup: time 0.409: 93: normal(|): DUMP: mapping (Pass I) [regular files] sendbackup: time 8.413: 93: normal(|): DUMP: mapping (Pass II) [directories] sendbackup: time 8.415: 93: normal(|): DUMP: estimated 10329957 tape blocks. sendbackup: time 8.417: 93: normal(|): DUMP: Volume 1 started with block 1 at: Thu Aug 12 05:59:15 2004 sendbackup: time 8.443: 93: normal(|): DUMP: dumping (Pass III) [directories] sendbackup: time 19.568: 93: normal(|): DUMP: dumping (Pass IV) [regular files] sendbackup: time 308.326: 93: normal(|): DUMP: 10.40% done at 3579 kB/s, finished in 0:43 sendbackup: time 608.283: 93: normal(|): DUMP: 20.91% done at 3600 kB/s, finished in 0:37 sendbackup: time 908.287: 93: normal(|): DUMP: 31.86% done at 3657 kB/s, finished in 0:32 sendbackup: time 1208.361: 93: normal(|): DUMP: 43.03% done at 3704 kB/s, finished in 0:26




















-----Original Message-----
From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: 12 August 2004 14:54
To: Ranveer Attalia
Cc: [EMAIL PROTECTED]
Subject: Re: data timeout - no replies...anyone???


On Thursday 12 August 2004 04:21, Ranveer Attalia wrote:

I'm still having this problem, can anyone help?

-----Original Message-----
From: Ranveer Attalia
Sent: 11 August 2004 11:21
To: [EMAIL PROTECTED]
Subject: data timeout


Hi

I recently added two new servers to the daily backup list but now keep


getting data timeout errors for them.
I have already increased my dtimeout parameter in the amanda.conf  file


to 7200 before I added the new servers. Can anyone tell me if there is


a more reasonable size I can increase this to without the backup falling over or running through late into the next morning?

Thanks for any help.

- Ranveer


This really isn't enough info to do more than make a wild guess.

And theres some confusion about servers vs clients.  An amanda server is
the machine the tape drives live in, everybody else is a client
(including the server if it also backs itself up), and I'm interpreting
the above to mean you've added 2 more clients, not 2 more servers.

I'd start by looking in the logs the client copy of amanda keeps to see
if the process is dying for some reason.  Amanda does keep pretty
detailed logs, and does her own log rotations. To me a dtimeout of 7200
is considerable overkill.

[...]

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.24% setiathome rank, not too shabby for a WV hillbilly Yahoo.com
attorneys please note, additions to this message by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

_______________________________________________________________________

This email has been scanned by the MessageLabs Email Security System.
MLabs systems monitored and maintained by Tertio Internal Support.
_______________________________________________________________________



________________________________________________________________________

Tertio Telecoms (www.telco-tertio.com)

Head Office: One Angel Square  Torrens Street  London  EC1V 1PL
Tel: +44 (0)20 7843 4000 - Fax: +44 (0)20 7843 4001

Bath Office: Riverside Buildings 108 Walcot Street Bath BA1 5BG
Tel: +44 (0)1225 478000 - Fax: +44 (0)1225 478001


Munich Office: Freisinger Strasse 10, 85737 Ismaning/Munich, Germany,
Tel: +49 (0)89 665506 41 - Fax: +49 (0)89 665506 99

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of Tertio Ltd.

This email has been scanned by the MessageLabs Email Security System.
________________________________________________________________________




Reply via email to