Thanks for getting back to me The filesystem version we are using is ext3. Can I run a tar using Amanda, so it doesnt interfere with the filesystem versions? How would I go about doign that? Would a separate config and disklist need to be created? By the way, we dont have a firewall issue because these machines (servers & clients) are completely independant of any connection via the firewall.
Thanks - Ranveer -----Original Message----- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: 12 August 2004 18:04 To: Ranveer Attalia Cc: Christoph Scheeder; [EMAIL PROTECTED] Subject: Re: data timeout - no replies...anyone??? On Thursday 12 August 2004 12:08, Ranveer Attalia wrote: >Yes tsslin1 is a linux machine and no there was no finishing line on >sendbackup, but I have another linux machine that is working fine with >the same version of amanda client on it. What do you mean by > ext2/3 ? The question is what filesystem version you are using? We're assuming that its ext2, with the journalling laid on top which is then called ext3. Dump would care, tar would not. >- Ranveer > >DUMP SUMMARY: > DUMPER STATS TAPER > STATS > >HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS >KB/s >-------------------------- --------------------------------- >------------ >pedlinux1 / 1 64770 64770 -- 11:37 93.0 >0:106639.1 >pedlinux1 /boot 1 10 10 -- 0:02 4.1 0:00 >34.9 > >-----Original Message----- >From: Christoph Scheeder [mailto:[EMAIL PROTECTED] >Sent: 12 August 2004 16:57 >To: Ranveer Attalia >Cc: [EMAIL PROTECTED] >Subject: Re: data timeout - no replies...anyone??? > >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 Something Chhristoph wrote triggerd another fading memory. If there is a firewall involved, and the ports were opened ok, but the firewall see's no activity to 'keep-alive' within a certain time, it closed the ports. This happened to another user at least a year ago IIRC. I believe the cure was to extend the autoclosure timeing in the firewall rules. And I concur with Christoph regarding dump. Tar worked better for me, and it usually gives sensible error messages when it doesn't. But tar versions vary too, and historicly we have been recommending only version 1.13-19 or 1.13-25. There is an even newer version extant, but I can't recall if anyone here on this list has said it works correctly or not. -- 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. ________________________________________________________________________