Hi, i don't recall when it went in, but AFAIK it was 1 subrelease after the point where a missing exclude-file began to get treated as an error.... ;-) Perhaps its mentioned somewhere in a changelog. Christoph
Gene Heskett schrieb:
On Tuesday 17 August 2004 04:19, Christoph Scheeder wrote:
Hi, first sorry for the delay in answering. The exclude-list option gives the path to a text-file containig patterns which describe what files should be excluded from the backup. mine contains lines like
./core ./*.tmp ./*~
etc the "./" at the start is required, without it won't work.
you'll have to create one meeting your requirements or, as Gene already pointed out, you can remove this line from the dumptype definition, or you can modify it to read:
exclude list optional "/path/to/your/exclude-list"
which makes it an optional file, and amanda will work with or without it and stop complaining if it does not exist. Christoph
At what tarball version did that 'optional' get built in? He may, if a beginner, be trying to use an (spit) rpm. I don't know, either I wasn't paying enough attention, or he didn't say.
Ranveer Attalia schrieb:
Hi Christoph
I've found the GNUTAR dumptype and changed the partition which was failing to backup:
FAILURE AND STRANGE DUMP SUMMARY: tsslin1 /export/mansun1_telco lev 0 FAILED [data timeout]
Amanda.conf: define dumptype root-tar { global program "GNUTAR" comment "root partitions dumped with tar" compress none index exclude list "/usr/local/lib/amanda/exclude.gtar" priority low }
Disklist data: #TSSLIN1 tsslin1 / nocomp tsslin1 /boot nocomp tsslin1 /usr nocomp tsslin1 /var nocomp tsslin1 /opt nocomp tsslin1 /databases nocomp tsslin1 /export/home nocomp tsslin1 /export/mansun1_tss nocomp tsslin1 /export/mansun1_telco root-tar
When I run an amcheck Daily -C tsslin1, I get the following error. Problem is, the exclude.gtar file doesnt actually exist on the server.. Can this just be downloaded?
Amanda Backup Client Hosts Check -------------------------------- ERROR: tsslin1: [Can't open exclude file '/usr/local/lib/amanda/exclude.gtar': No such file or directory] Client check: 1 host checked in 0.095 seconds, 1 problem found
-----Original Message----- From: Christoph Scheeder [mailto:[EMAIL PROTECTED] Sent: 13 August 2004 11:24 To: Ranveer Attalia Cc: [EMAIL PROTECTED] Subject: Re: data timeout - no replies...anyone???
Hi, yes you can, go to your amanda.conf: have a look at the defined dumptypes at the bottom of it, an check if one meets your requirements. in the example-amanda.conf there are some dumptypes defined using tar. if none meets your requirements create a new one including the line
programm "GNUTAR"
which tells amanda to use tar as backup-program. then edit your disklist setting the disks in question to use this dumptype. now run amcheck to make shure the needed files and directorys for tar exist. If it complains about something fix it and you should be fine for the next run.
Christoph
Ranveer Attalia schrieb:
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. _________________________________________________________________ _____ __
__________________________________________________________________ _____
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. __________________________________________________________________ ______
