Re: Disklist - partial directory backup - advice please
Hello John,
2.4.3b3 is buggy with relative exclude list. Try the latest snapshot
from http://www.iro.umontreal.ca/~martinea/amanda .
Jean-Louis
On Mon, Aug 19, 2002 at 08:47:52PM -0400, John Ouellette wrote:
>
> Ok, now that's interesting... I'll agree that the fact that you're using
> 2.4.3b3 and aren't having problems indicates that you're right.
> However... The comments in the amanda.conf file say:
>
> "Note that the `full pathname' of a file within its
> filesystem starts with `./', because of the way amanda runs
> gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
> the final dot!) Thus, if you're backing up `/usr' with a
> diskfile entry like ``host /usr gnutar-root', but you don't
> want to backup /usr/tmp, your exclude list should contain
> the pattern `./tmp', as this is relative to the `/usr' above.
> Please refer to the man-page of gnutar for more information.
> If a relative pathname is specified as the exclude list,
> it is searched from within the directory that is
> going to be backed up."
>
> The man page says:
>
> " For exclude list, If the file name is relative, the
> disk name being backed up is prepended. So if this
> is entered:
>
>exclude list ".amanda.excludes"
>
> the actual file use would be /var/.amanda.excludes
> for a backup of /var, /usr/local/.amanda.excludes
> for a backup of /usr/local, and so on."
>
> These suggest that the exclude pattern, whether as a exclude pattern or a
> file containing a list of patterns, is supposed to have *relative*
> pathnames, not absolute pathnames. Yes, your list is relative, but your
> path for the exclude list file itself is absolute
> (/usr/local/etc/amanda/exclude.gtar) which is not quite what the docs
> recommend
>
> I'll try some absolute paths later: if they work, it suggests a
> documentation bug, rather than a coding one...
>
> J.
>
> On Mon, 19 Aug 2002, Gene Heskett wrote:
>
> > On Monday 19 August 2002 20:09, John Ouellette wrote:
> > >We're going a bit far afield from what Kevin had originally posted
> > > but oh well.
> > >
> > >Are you using version 2.4.2, Gene?
> >
> > No, 2.4.3b3-20020805 right now. And I'm not having any known
> > problems, none. And other than some broken scripting in the
> > amstatus command, I've had zilch troubles with amanda in the last 4
> > or more months, thru a goodly number of 2.4.3b* versions.
> >
> > > Kevin and I are using v2.4.3b3
> > > and have found the same problem with exclude lists. What I have
> > > found (again, with v2.4.3b3) was that the exclude keyword in a
> > > dumptype definition *causes the size estimates from tar to fail*.
> > > The debug info from Amanda shows that tar is never even called.
> > > From one of my tests (sendsize.*.debug):
> > >
> > >++
> > >sendsize: debug 1 pid 27066 ruid 499 euid 499 start time Mon Aug
> > > 19 14:31:57 2002
> > >/home/amanda/libexec/sendsize: version 2.4.3b3
> > >sendsize: calculating for amname '/', dirname '/'
> > >sendsize: getting size via gnutar for / level 0
> > >++
> >
> > Any one of my copious numbers of sendsize.*.debug files is exactly
> > like the rest, containing only a copy of the exclude file as
> > follows:
> > -
> > ./usr/dumps/*
> > ./var/pacct
> > -
> > So I again submit that the exclude logic isn't broken, but that the
> > file itself simply isn't being found due to a lack of a full
> > pathlist in the dumptype specification, as is shown that I am using
> > below.
> >
> > >(Note that there were three other partitions called with the same
> > >dumptype: the size estimates weren't even attempted by amanda --
> > > the above is the entire contents of the debug file.) This with a
> > > dumptype definition of:
> > >
> >
> > This is yours
> >
> > >define dumptype TEST {
> > >global
> > >comment "test dumptype"
> > >program "GNUTAR"
> > >compress none
> > >index
> > >exclude "./amanda" <---whats the current pwd when this
> > executes?
> > >record no
> > >}
> > >
> > >(The idea of the exclude was the same as Kevin's: to exclude the
> > > holding disk areas from those disks.) The result is the same if
> > > I use:
> > >
> > >exclude "./amanda*"
> > >exclude "*amanda*
> > >exclude list ".amanda.exclude"
> > >exclude list "./.amanda.exclude"
> > >
> > >etc., in the dumptype definition. The exclude keyword seemed to
> > > work in v2.4.2p2, but I decided to upgrade to 2.4.3b3 to get
> > > other features working (I'm not sure if it was worth it now...).
> >
> > Thats odd. I also note that you still aren't giving it a full path
> > to the exclude file. Its possible that the fact that it can't find
> > it might be enough of an error to cause the tar call to fail.
> >
> > >I've taken a brief look into the code for how exclude lists are
> > > handled, but there was such a big change from v2.4.2 to v2.4.3,
> > > I'm not sure if I'll be able to fi
Re: Disklist - partial directory backup - advice please
On Monday 19 August 2002 20:47, John Ouellette wrote: >Ok, now that's interesting... I'll agree that the fact that > you're using 2.4.3b3 and aren't having problems indicates that > you're right. However... The comments in the amanda.conf file > say: > >"Note that the `full pathname' of a file within its >filesystem starts with `./', because of the way amanda runs >gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note >the final dot!) Thus, if you're backing up `/usr' with a >diskfile entry like ``host /usr gnutar-root', but you don't >want to backup /usr/tmp, your exclude list should contain >the pattern `./tmp', as this is relative to the `/usr' above. >Please refer to the man-page of gnutar for more information. >If a relative pathname is specified as the exclude list, >it is searched from within the directory that is >going to be backed up." Which refers to the CONTENTS of the exclude file. >The man page says: > >" For exclude list, If the file name is relative, the >disk name being backed up is prepended. So if this >is entered: > > exclude list ".amanda.excludes" Ohmygawd, who wrote that?? Never mind, I don't wanna know that badly cause it would cause my faith in the real authors to slip a notch. The meaning somehow got lost in the translation to english at least as I understand it and I've been speaking it for 67 of my nearly 68 years! In the first place (IIRC) amdump itself actually cd's to each directory in a tree, backing up each and every subdir in that subdir using tar, with tar itself skipping the subdirs that match in the ./here format from the listing in the exclude file. So the CONTENTS of the exclude file are then stated in a format relative TO the current directory. No wonder its confusing the troops here, gaahhck! >the actual file use would be /var/.amanda.excludes >for a backup of /var, /usr/local/.amanda.excludes >for a backup of /usr/local, and so on." I think we are getting the fact that I'm argueing to the point of boreing this whole list for a full pathlist arguement leading to the exclude file, with the exclude files actual contents. Apples vs Oranges, or was it kiwi fruit... Whatever. >These suggest that the exclude pattern, whether as a exclude > pattern or a file containing a list of patterns, is supposed to > have *relative* pathnames, not absolute pathnames. Yes, your > list is relative, but your path for the exclude list file itself > is absolute >(/usr/local/etc/amanda/exclude.gtar) which is not quite what the > docs recommend Again, the pathlist TO the exclude file is absolute. BUT, The contents of the exclude file are relative to ./ The docs don't say in plain language that the exclude files location is relative, anyplace in them. They assume, and rightly so IMO, that the location is an absolute, just as the location of any other file in the system is barring the installation of links by the thousands all over the system pointing back to the real file. >I'll try some absolute paths later: if they work, it suggests a >documentation bug, rather than a coding one... See above, that particular paragraph would be better off if excised from the docs rather than to continue its confusion facter. I'm not normally one to beat on the doc writers as its generally a rather thankless job anyway, but I could make an exception this one time. [... way past time for a snippage party here folks] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.12% setiathome rank, not too shabby for a WV hillbilly
Re: Disklist - partial directory backup - advice please
Ok, now that's interesting... I'll agree that the fact that you're using
2.4.3b3 and aren't having problems indicates that you're right.
However... The comments in the amanda.conf file say:
"Note that the `full pathname' of a file within its
filesystem starts with `./', because of the way amanda runs
gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
the final dot!) Thus, if you're backing up `/usr' with a
diskfile entry like ``host /usr gnutar-root', but you don't
want to backup /usr/tmp, your exclude list should contain
the pattern `./tmp', as this is relative to the `/usr' above.
Please refer to the man-page of gnutar for more information.
If a relative pathname is specified as the exclude list,
it is searched from within the directory that is
going to be backed up."
The man page says:
" For exclude list, If the file name is relative, the
disk name being backed up is prepended. So if this
is entered:
exclude list ".amanda.excludes"
the actual file use would be /var/.amanda.excludes
for a backup of /var, /usr/local/.amanda.excludes
for a backup of /usr/local, and so on."
These suggest that the exclude pattern, whether as a exclude pattern or a
file containing a list of patterns, is supposed to have *relative*
pathnames, not absolute pathnames. Yes, your list is relative, but your
path for the exclude list file itself is absolute
(/usr/local/etc/amanda/exclude.gtar) which is not quite what the docs
recommend
I'll try some absolute paths later: if they work, it suggests a
documentation bug, rather than a coding one...
J.
On Mon, 19 Aug 2002, Gene Heskett wrote:
> On Monday 19 August 2002 20:09, John Ouellette wrote:
> >We're going a bit far afield from what Kevin had originally posted
> > but oh well.
> >
> >Are you using version 2.4.2, Gene?
>
> No, 2.4.3b3-20020805 right now. And I'm not having any known
> problems, none. And other than some broken scripting in the
> amstatus command, I've had zilch troubles with amanda in the last 4
> or more months, thru a goodly number of 2.4.3b* versions.
>
> > Kevin and I are using v2.4.3b3
> > and have found the same problem with exclude lists. What I have
> > found (again, with v2.4.3b3) was that the exclude keyword in a
> > dumptype definition *causes the size estimates from tar to fail*.
> > The debug info from Amanda shows that tar is never even called.
> > From one of my tests (sendsize.*.debug):
> >
> >++
> >sendsize: debug 1 pid 27066 ruid 499 euid 499 start time Mon Aug
> > 19 14:31:57 2002
> >/home/amanda/libexec/sendsize: version 2.4.3b3
> >sendsize: calculating for amname '/', dirname '/'
> >sendsize: getting size via gnutar for / level 0
> >++
>
> Any one of my copious numbers of sendsize.*.debug files is exactly
> like the rest, containing only a copy of the exclude file as
> follows:
> -
> ./usr/dumps/*
> ./var/pacct
> -
> So I again submit that the exclude logic isn't broken, but that the
> file itself simply isn't being found due to a lack of a full
> pathlist in the dumptype specification, as is shown that I am using
> below.
>
> >(Note that there were three other partitions called with the same
> >dumptype: the size estimates weren't even attempted by amanda --
> > the above is the entire contents of the debug file.) This with a
> > dumptype definition of:
> >
>
> This is yours
>
> >define dumptype TEST {
> >global
> >comment "test dumptype"
> >program "GNUTAR"
> >compress none
> >index
> >exclude "./amanda" <---whats the current pwd when this
> executes?
> >record no
> >}
> >
> >(The idea of the exclude was the same as Kevin's: to exclude the
> > holding disk areas from those disks.) The result is the same if
> > I use:
> >
> >exclude "./amanda*"
> >exclude "*amanda*
> >exclude list ".amanda.exclude"
> >exclude list "./.amanda.exclude"
> >
> >etc., in the dumptype definition. The exclude keyword seemed to
> > work in v2.4.2p2, but I decided to upgrade to 2.4.3b3 to get
> > other features working (I'm not sure if it was worth it now...).
>
> Thats odd. I also note that you still aren't giving it a full path
> to the exclude file. Its possible that the fact that it can't find
> it might be enough of an error to cause the tar call to fail.
>
> >I've taken a brief look into the code for how exclude lists are
> > handled, but there was such a big change from v2.4.2 to v2.4.3,
> > I'm not sure if I'll be able to figure out what broke the exclude
> > keyword...
> >
> >Note that in the amandad debug file, the exclude list seems to be
> > parsed OK, so it really must be in the call to sendsize that the
> > error is occurring...
> >
> >J.
> >
> >On Mon, 19 Aug 2002, Gene Heskett wrote:
> >> On Monday 19 August 2002 16:12, John Ouellette wrote:
> >> >I've played around with the exclude lists for a while (as
> >> > defined in the dumptypes) and have had no luck i
Re: Disklist - partial directory backup - advice please
On Monday 19 August 2002 20:09, John Ouellette wrote:
>We're going a bit far afield from what Kevin had originally posted
> but oh well.
>
>Are you using version 2.4.2, Gene?
No, 2.4.3b3-20020805 right now. And I'm not having any known
problems, none. And other than some broken scripting in the
amstatus command, I've had zilch troubles with amanda in the last 4
or more months, thru a goodly number of 2.4.3b* versions.
> Kevin and I are using v2.4.3b3
> and have found the same problem with exclude lists. What I have
> found (again, with v2.4.3b3) was that the exclude keyword in a
> dumptype definition *causes the size estimates from tar to fail*.
> The debug info from Amanda shows that tar is never even called.
> From one of my tests (sendsize.*.debug):
>
>++
>sendsize: debug 1 pid 27066 ruid 499 euid 499 start time Mon Aug
> 19 14:31:57 2002
>/home/amanda/libexec/sendsize: version 2.4.3b3
>sendsize: calculating for amname '/', dirname '/'
>sendsize: getting size via gnutar for / level 0
>++
Any one of my copious numbers of sendsize.*.debug files is exactly
like the rest, containing only a copy of the exclude file as
follows:
-
./usr/dumps/*
./var/pacct
-
So I again submit that the exclude logic isn't broken, but that the
file itself simply isn't being found due to a lack of a full
pathlist in the dumptype specification, as is shown that I am using
below.
>(Note that there were three other partitions called with the same
>dumptype: the size estimates weren't even attempted by amanda --
> the above is the entire contents of the debug file.) This with a
> dumptype definition of:
>
This is yours
>define dumptype TEST {
>global
>comment "test dumptype"
>program "GNUTAR"
>compress none
>index
>exclude "./amanda" <---whats the current pwd when this
executes?
>record no
>}
>
>(The idea of the exclude was the same as Kevin's: to exclude the
> holding disk areas from those disks.) The result is the same if
> I use:
>
>exclude "./amanda*"
>exclude "*amanda*
>exclude list ".amanda.exclude"
>exclude list "./.amanda.exclude"
>
>etc., in the dumptype definition. The exclude keyword seemed to
> work in v2.4.2p2, but I decided to upgrade to 2.4.3b3 to get
> other features working (I'm not sure if it was worth it now...).
Thats odd. I also note that you still aren't giving it a full path
to the exclude file. Its possible that the fact that it can't find
it might be enough of an error to cause the tar call to fail.
>I've taken a brief look into the code for how exclude lists are
> handled, but there was such a big change from v2.4.2 to v2.4.3,
> I'm not sure if I'll be able to figure out what broke the exclude
> keyword...
>
>Note that in the amandad debug file, the exclude list seems to be
> parsed OK, so it really must be in the call to sendsize that the
> error is occurring...
>
>J.
>
>On Mon, 19 Aug 2002, Gene Heskett wrote:
>> On Monday 19 August 2002 16:12, John Ouellette wrote:
>> >I've played around with the exclude lists for a while (as
>> > defined in the dumptypes) and have had no luck in getting any
>> > configs with exclude lists to work, whether I define the paths
>> > with the leading ./ or no
>> >
>> >Kevin was using an exclude list defined in the disklist, but I
>> > assume it is the same code that parses this and passes it on
>> > to 'tar', so the same bug might exist.
>> >
>> >And, according to the docs and examples, you do need the
>> > quotes... (or get a parse error if you exclude them).
>>
>> I'm not here, but I'm using an exclude file too, here it is:
>> -
>> ./usr/dumps/*
>> ./var/pacct
>> -
>>
>> Also, I recall the filename didn't give the full path in your
>> earler example, which should look like this in your amanda.conf:
>> --
>> define dumptype root-tar {
>> global
>> program "GNUTAR"
>> comment "root partitions dumped with tar"
>> compress none
>> index yes
>> exclude list "/usr/local/etc/amanda/exclude.gtar"
^
>> priority low
>> }
>>
>> define dumptype user-tar {
>> root-tar
>> comment "user partitions dumped with tar"
>> exclude list "/usr/local/etc/amanda/exclude.gtar"
Again
>> compress server best
>> priority medium
>> }
>> -etc, etc taking note that each "dumptype" can
>> have its own unique name-it-whatever-file.
>>
>> >I've started to trudge through the code to see if the bug is
>> > obvious, but haven't managed to get far.
>> >
>> >J.
>> >
>> >On Mon, 19 Aug 2002, Gene Heskett wrote:
>> >> On Monday 19 August 2002 12:00, Kevin Passey wrote:
>> >> >Thanks John
>> >> >
>> >> >That is what I am using.
>> >> >
>> >> >I only what to omit the /dumps folders.
>> >>
>> >> Did you specify them as "./dumps" (witho
Re: Disklist - partial directory backup - advice please
We're going a bit far afield from what Kevin had originally posted but oh
well.
Are you using version 2.4.2, Gene? Kevin and I are using v2.4.3b3 and
have found the same problem with exclude lists. What I have found (again,
with v2.4.3b3) was that the exclude keyword in a dumptype definition
*causes the size estimates from tar to fail*. The debug info from Amanda
shows that tar is never even called. From one of my tests
(sendsize.*.debug):
++
sendsize: debug 1 pid 27066 ruid 499 euid 499 start time Mon Aug 19
14:31:57 2002
/home/amanda/libexec/sendsize: version 2.4.3b3
sendsize: calculating for amname '/', dirname '/'
sendsize: getting size via gnutar for / level 0
++
(Note that there were three other partitions called with the same
dumptype: the size estimates weren't even attempted by amanda -- the
above is the entire contents of the debug file.) This with a dumptype
definition of:
define dumptype TEST {
global
comment "test dumptype"
program "GNUTAR"
compress none
index
exclude "./amanda"
record no
}
(The idea of the exclude was the same as Kevin's: to exclude the holding
disk areas from those disks.) The result is the same if I use:
exclude "./amanda*"
exclude "*amanda*
exclude list ".amanda.exclude"
exclude list "./.amanda.exclude"
etc., in the dumptype definition. The exclude keyword seemed to work in
v2.4.2p2, but I decided to upgrade to 2.4.3b3 to get other features
working (I'm not sure if it was worth it now...).
I've taken a brief look into the code for how exclude lists are handled,
but there was such a big change from v2.4.2 to v2.4.3, I'm not sure if
I'll be able to figure out what broke the exclude keyword...
Note that in the amandad debug file, the exclude list seems to be parsed
OK, so it really must be in the call to sendsize that the error is
occurring...
J.
On Mon, 19 Aug 2002, Gene Heskett wrote:
> On Monday 19 August 2002 16:12, John Ouellette wrote:
> >I've played around with the exclude lists for a while (as defined
> > in the dumptypes) and have had no luck in getting any configs
> > with exclude lists to work, whether I define the paths with the
> > leading ./ or no
> >
> >Kevin was using an exclude list defined in the disklist, but I
> > assume it is the same code that parses this and passes it on to
> > 'tar', so the same bug might exist.
> >
> >And, according to the docs and examples, you do need the quotes...
> > (or get a parse error if you exclude them).
> >
> I'm not here, but I'm using an exclude file too, here it is:
> -
> ./usr/dumps/*
> ./var/pacct
> -
>
> Also, I recall the filename didn't give the full path in your earler
> example, which should look like this in your amanda.conf:
> --
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> index yes
> exclude list "/usr/local/etc/amanda/exclude.gtar"
> priority low
> }
>
> define dumptype user-tar {
> root-tar
> comment "user partitions dumped with tar"
> exclude list "/usr/local/etc/amanda/exclude.gtar"
> compress server best
> priority medium
> }
> -etc, etc taking note that each "dumptype" can have
> its own unique name-it-whatever-file.
>
> >I've started to trudge through the code to see if the bug is
> > obvious, but haven't managed to get far.
> >
> >J.
> >
> >On Mon, 19 Aug 2002, Gene Heskett wrote:
> >> On Monday 19 August 2002 12:00, Kevin Passey wrote:
> >> >Thanks John
> >> >
> >> >That is what I am using.
> >> >
> >> >I only what to omit the /dumps folders.
> >>
> >> Did you specify them as "./dumps" (without the quotes of course)
> >> The missing leading dot in your line above says its your exclude
> >> file thats broken. Tar's exludes are relative to the currently
> >> being processed directory, hence the leading ./
> >>
> >> >I think I will have to create them in a separate partition.
> >> >
> >> >Thanks for that.
> >> >
> >> >Regards
> >> >
> >> >Kevin
> >> >
> >> >
> >> >
> >> >-Original Message-
> >>
> >> From: John Ouellette [mailto:[EMAIL PROTECTED]]
>
> [...]
>
>
--
++
John Ouellette | Ph: 212-313-7919
Department of Astrophysics | Fax: 212-769-5007
American Museum of Natural History | e-mail: [EMAIL PROTECTED]
Central Park West at 79th St. | http://research.amnh.org/astrophysics
New York, NY 10024-5192 |
++
Re: Disklist - partial directory backup - advice please
Hello Kevin,
Try the latest snapshot of 2.4.3b3 from
http://www.iro.umontreal.ca/~martinea/amanda
it fixe a few problem with the exclude.
Don't forget to upgrade the server and the client.
I'm not sure it works if you use the device name in the disklist,
you should try with the directory name.
dilmom /usr {
high-tar
exclude "./dumps"
} 1
Jean-Louis
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Disklist - partial directory backup - advice please
On Monday 19 August 2002 16:12, John Ouellette wrote:
>I've played around with the exclude lists for a while (as defined
> in the dumptypes) and have had no luck in getting any configs
> with exclude lists to work, whether I define the paths with the
> leading ./ or no
>
>Kevin was using an exclude list defined in the disklist, but I
> assume it is the same code that parses this and passes it on to
> 'tar', so the same bug might exist.
>
>And, according to the docs and examples, you do need the quotes...
> (or get a parse error if you exclude them).
>
I'm not here, but I'm using an exclude file too, here it is:
-
./usr/dumps/*
./var/pacct
-
Also, I recall the filename didn't give the full path in your earler
example, which should look like this in your amanda.conf:
--
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index yes
exclude list "/usr/local/etc/amanda/exclude.gtar"
priority low
}
define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
exclude list "/usr/local/etc/amanda/exclude.gtar"
compress server best
priority medium
}
-etc, etc taking note that each "dumptype" can have
its own unique name-it-whatever-file.
>I've started to trudge through the code to see if the bug is
> obvious, but haven't managed to get far.
>
>J.
>
>On Mon, 19 Aug 2002, Gene Heskett wrote:
>> On Monday 19 August 2002 12:00, Kevin Passey wrote:
>> >Thanks John
>> >
>> >That is what I am using.
>> >
>> >I only what to omit the /dumps folders.
>>
>> Did you specify them as "./dumps" (without the quotes of course)
>> The missing leading dot in your line above says its your exclude
>> file thats broken. Tar's exludes are relative to the currently
>> being processed directory, hence the leading ./
>>
>> >I think I will have to create them in a separate partition.
>> >
>> >Thanks for that.
>> >
>> >Regards
>> >
>> >Kevin
>> >
>> >
>> >
>> >-Original Message-
>>
>> From: John Ouellette [mailto:[EMAIL PROTECTED]]
[...]
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.12% setiathome rank, not too shabby for a WV hillbilly
Re: Disklist - partial directory backup - advice please
I've played around with the exclude lists for a while (as defined in the dumptypes) and have had no luck in getting any configs with exclude lists to work, whether I define the paths with the leading ./ or no Kevin was using an exclude list defined in the disklist, but I assume it is the same code that parses this and passes it on to 'tar', so the same bug might exist. And, according to the docs and examples, you do need the quotes... (or get a parse error if you exclude them). I've started to trudge through the code to see if the bug is obvious, but haven't managed to get far. J. On Mon, 19 Aug 2002, Gene Heskett wrote: > On Monday 19 August 2002 12:00, Kevin Passey wrote: > >Thanks John > > > >That is what I am using. > > > >I only what to omit the /dumps folders. > > Did you specify them as "./dumps" (without the quotes of course) > The missing leading dot in your line above says its your exclude > file thats broken. Tar's exludes are relative to the currently > being processed directory, hence the leading ./ > > >I think I will have to create them in a separate partition. > > > >Thanks for that. > > > >Regards > > > >Kevin > > > > > > > >-----Original Message- > From: John Ouellette [mailto:[EMAIL PROTECTED]] > >Sent: 19 August 2002 16:11 > >To: [EMAIL PROTECTED] > >Subject: Re: Disklist - partial directory backup - advice please > > > > > > > >Hi Kevin, > > > >Are you using Amanda 2.4.3b3? I think there is a bug in the > > 'exclude' lists in the definition of dumptypes (including the > > inline exclude lists like you're using) for that version. The > > bug causes the dumps to fail, at least it does in my case. > > > >How to work around your problem without using exclude lists, I'm > > not sure, although you might try 'include' lists -- I'm not sure > > if the same bug affects these. > > > >J. > > -- ++ John Ouellette | Ph: 212-313-7919 Department of Astrophysics | Fax: 212-769-5007 American Museum of Natural History | e-mail: [EMAIL PROTECTED] Central Park West at 79th St. | http://research.amnh.org/astrophysics New York, NY 10024-5192 | ++
Re: Disklist - partial directory backup - advice please
On Monday 19 August 2002 12:00, Kevin Passey wrote: >Thanks John > >That is what I am using. > >I only what to omit the /dumps folders. Did you specify them as "./dumps" (without the quotes of course) The missing leading dot in your line above says its your exclude file thats broken. Tar's exludes are relative to the currently being processed directory, hence the leading ./ >I think I will have to create them in a separate partition. > >Thanks for that. > >Regards > >Kevin > > > >-Original Message- From: John Ouellette [mailto:[EMAIL PROTECTED]] >Sent: 19 August 2002 16:11 >To: [EMAIL PROTECTED] >Subject: Re: Disklist - partial directory backup - advice please > > > >Hi Kevin, > >Are you using Amanda 2.4.3b3? I think there is a bug in the > 'exclude' lists in the definition of dumptypes (including the > inline exclude lists like you're using) for that version. The > bug causes the dumps to fail, at least it does in my case. > >How to work around your problem without using exclude lists, I'm > not sure, although you might try 'include' lists -- I'm not sure > if the same bug affects these. > >J. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.12% setiathome rank, not too shabby for a WV hillbilly
Re: Disklist - partial directory backup - advice please
At 2002-08-19T16:00:21Z, Kevin Passey <[EMAIL PROTECTED]> writes:
> I only what to omit the /dumps folders.
>
> I think I will have to create them in a separate partition.
Try this:
1) Create a new dumptype with an "exclude list" option. For example:
define dumptype compressed-tar-with-excludes {
compressed-tar
comment "Non-root partitions without compression, plus an exclude list"
exclude list ".amanda.excludes"
}
2) Edit the file specified above. For example:
root@kanga:/usr/share/media# cat .amanda.excludes
./music/all
That will cause Amanda to skip the files/directories listed in the
exclude file.
--
Kirk Strauser
The Strauser Group - http://www.strausergroup.com/
RE: Disklist - partial directory backup - advice please
Thanks John That is what I am using. I only what to omit the /dumps folders. I think I will have to create them in a separate partition. Thanks for that. Regards Kevin -Original Message- From: John Ouellette [mailto:[EMAIL PROTECTED]] Sent: 19 August 2002 16:11 To: [EMAIL PROTECTED] Subject: Re: Disklist - partial directory backup - advice please Hi Kevin, Are you using Amanda 2.4.3b3? I think there is a bug in the 'exclude' lists in the definition of dumptypes (including the inline exclude lists like you're using) for that version. The bug causes the dumps to fail, at least it does in my case. How to work around your problem without using exclude lists, I'm not sure, although you might try 'include' lists -- I'm not sure if the same bug affects these. J. -- ++ John Ouellette | Ph: 212-313-7919 Department of Astrophysics | Fax: 212-769-5007 American Museum of Natural History | e-mail: [EMAIL PROTECTED] Central Park West at 79th St. | http://research.amnh.org/astrophysics New York, NY 10024-5192 | ++
Re: Disklist - partial directory backup - advice please
Hi Kevin, Are you using Amanda 2.4.3b3? I think there is a bug in the 'exclude' lists in the definition of dumptypes (including the inline exclude lists like you're using) for that version. The bug causes the dumps to fail, at least it does in my case. How to work around your problem without using exclude lists, I'm not sure, although you might try 'include' lists -- I'm not sure if the same bug affects these. J. -- ++ John Ouellette | Ph: 212-313-7919 Department of Astrophysics | Fax: 212-769-5007 American Museum of Natural History | e-mail: [EMAIL PROTECTED] Central Park West at 79th St. | http://research.amnh.org/astrophysics New York, NY 10024-5192 | ++
Disklist - partial directory backup - advice please
Hi,
I have amanda configured and almost working (thanks to this list).
I have one remaining problem.
I have a disk "sda5" that has /usr/ on it.
Inside /usr/ are my /dump directories. I have been wrestling with the
example in disklist
"hostA /diskA/all /diskA" and the relevant exclude statements.
Can anybody help me out here - here is what I have.
dilmom /sda5/all /sda5 {
high-tar
exclude "./dumps"
} 1
What have I done wrong??
Here is my summary
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
dilmom /sda5/all 0 FAILED ---
dilmom sda11 10 64 --0:00 110.8 0:0013217.7
dilmom sda21 390 64 16.4 0:02 1.3 0:0013185.0
dilmom sda31 390 64 16.4 0:01 51.4 0:0012774.5
dilmom sda71 550608 --0:02 243.1 0:0011482.7
dilmom sda81 370 96 25.9 0:00 230.2 0:0012924.1
(brought to you by Amanda version 2.4.3b3)
Thanks again.
Kevin Passey
