Re: ***UNCHECKED*** exact-match
On Fri, Jun 28, 2019 at 13:00:25 +0100, Nuno Dias wrote: > Yes, this will work if I use different labels not related with the > name of the diskdevice, the only problem is more work when I run > amstatus and amrecover to match the label with the disk/diredctory (Deb, sorry... I seem to have missed your previous email when it came through, but yes you showed what I was trying to get at, only with more-helpful example names :) .) Nuno, I would be curious to hear from any other sites where this problem has come up, but given that the current matching behavior seems to be more than two decades old, I suspect that changing your "diskname" format is going to be the easiest path forward to being able to select DLEs properly from the amdump command line. Note that you can certainly pick disknames that are "related" to the diskdevice name, so it should be possible to find a convention that works around the matching-problem without being too bad in the context of amstatus/amrecover/the Amanda Mail Report. For example, though I did it for competely unrelated reasons, in one Amanda config I run (named "Nightly), I have set the diskname of each DLE to be "ntly-" followed by the DLE path/"diskdevice path" (i.e. "ntly-/", "ntly-/data", etc.). So in that case I can tell easily from the diskname exactly what directory that DLE backs up... but yet none of the strings used for disknames exactly matches any string used for a diskdevice... Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: ***UNCHECKED*** exact-match
Hi Debra,
Yes, this will work if I use different labels not related with the
name of the diskdevice, the only problem is more work when I run
amstatus and amrecover to match the label with the disk/diredctory
Cheers,
Nuno
On Thu, 2019-06-27 at 18:37 +, Debra S Baddorf wrote:
> > On Jun 27, 2019, at 7:38 AM, Nuno Dias wrote:
> >
> > > I guess another possible solution is to using disknames of a form
> > > that
> > > are designend to be unique, e.g. something like (not tested)
> > >
> > > > --
> > > > MACHINE dir-main /dir {
> > > > tar
> > > > exclude "./subdir/*"
> > > > }
> > > >
> > > > MACHINE dir-subdir /dir {
> > > > tar
> > > > include "./subdir/*"
> > > > }
> > > > --
> > >
> > > ... and use those disknames on the amdump command line... (But
> > > you
> > > have to choose disknames carefully so your Amanda Mail Report
> > > looks
> > > reasonable, etc.)
> > >
> > >
> > > Nathan
> > >
> Possibly not tested, but that was what I was describing. I use text-
> only disknames
> like that all the time. No slashes in them, so they cannot be
> confused with actual disk designations!
>
> Deb Baddorf
> Fermilab
>
>
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
> On Jun 27, 2019, at 7:38 AM, Nuno Dias wrote:
>
>>
>> I guess another possible solution is to using disknames of a form
>> that
>> are designend to be unique, e.g. something like (not tested)
>>
>>> --
>>> MACHINE dir-main /dir {
>>> tar
>>> exclude "./subdir/*"
>>> }
>>>
>>> MACHINE dir-subdir /dir {
>>> tar
>>> include "./subdir/*"
>>> }
>>> --
>>
>> ... and use those disknames on the amdump command line... (But you
>> have to choose disknames carefully so your Amanda Mail Report looks
>> reasonable, etc.)
>>
>>
>> Nathan
>>
Possibly not tested, but that was what I was describing. I use text-only
disknames
like that all the time. No slashes in them, so they cannot be confused with
actual disk designations!
Deb Baddorf
Fermilab
Re: ***UNCHECKED*** exact-match
Hi Nathan,
Thanks for the reply, in my configuration I need the includes, I make
backups of terabytes of data, so split and the use of includes are
essencial.
I opened a bug in github.
Cheers,
Nuno
On Wed, 2019-06-26 at 18:48 -0400, Nathan Stratton Treadway wrote:
> On Wed, Jun 26, 2019 at 16:57:33 +0100, Nuno Dias wrote:
> > But if I have something like this
> >
> > --
> > MACHINE /dir {
> > tar
> > exclude "./subdir/*"
> > }
> >
> > MACHINE /dir/subdir /dir {
> > tar
> > include "./subdir/*"
> > }
> > --
> >
> > the commands
> >
> > $ amdump CONF MACHINE ^/dir$
> > and
> > $ amdump CONF MACHINE =/dir
> >
> > Don't work as expected, both backups (/dir and /dir/subdir) are
> > made
> >
> > From "man disklist"
> >
> > diskname
> > The name of the disk (a label). In most case, you set your
> > diskname
> > to the diskdevice and you don't set the diskdevice. If you
> > want
> > multiple entries with the same diskdevice, you must set a
> > different
> > diskname for each entry. It's the diskname that you use on the
> > commandline for any Amanda command. Look at the
> > example/disklist
> > file for example.
> >
> > So from this, if it's the diskname that is used in the command, it
> > seems that the reality is amdump is using the diskdevice instead!!
>
> Thanks for the additional info, which certainly helps explain what is
> happening to you
>
> My understanding of the inner workings of this part of Amanda is
> quite
> fuzzy, but assuming I have followed the program flow behind "amdump"
> correctly, it looks like the code in question is found in
> server-src/diskfile.c:match_disklist() , which contains the following
> lines:
> if ([...] &&
> (match_disk(sargv[i], dp->name) ||
> (dp->device && match_disk(sargv[i], dp->device {
>
> ..so I believe that in fact arguments specified on the amdump command
> line
> are matched against BOTH the "diskname" and "diskdevice" fields, and
> if
> either one matches the argument then that DLE is selected (which
> I
> agree doesn't match the wording of the manpage).
>
> (As far as I can tell from git, this code has been like that since
> at least 2006.)
>
>
> In this particular example I think you could work around the problem
> by
> changing your disklist to
>
> --
> MACHINE /dir {
> tar
> exclude "./subdir/*"
> }
>
> MACHINE /dir/subdir {
> tar
> }
> --
>
> (in which case presumably using either ^/dir$ or =/dir would not
> match
> the second DLE) ... but obviously that doesn't help if you ever want
> to
> have a DLE which uses "include" to pull in multiple subdirectories of
> /dir.
>
> I guess another possible solution is to using disknames of a form
> that
> are designend to be unique, e.g. something like (not tested)
>
> > --
> > MACHINE dir-main /dir {
> > tar
> > exclude "./subdir/*"
> > }
> >
> > MACHINE dir-subdir /dir {
> > tar
> > include "./subdir/*"
> > }
> > --
>
> ... and use those disknames on the amdump command line... (But you
> have to choose disknames carefully so your Amanda Mail Report looks
> reasonable, etc.)
>
>
> Nathan
>
> ---
> -
> Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic
> region
> Ray Ontko & Co. - Software consulting services -
> http://www.ontko.com/
> GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID:
> 1023D/ECFB6239
> Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
On Wed, Jun 26, 2019 at 16:57:33 +0100, Nuno Dias wrote:
> But if I have something like this
>
> --
> MACHINE /dir {
> tar
> exclude "./subdir/*"
> }
>
> MACHINE /dir/subdir /dir {
> tar
> include "./subdir/*"
> }
> --
>
> the commands
>
> $ amdump CONF MACHINE ^/dir$
> and
> $ amdump CONF MACHINE =/dir
>
> Don't work as expected, both backups (/dir and /dir/subdir) are made
>
> From "man disklist"
>
> diskname
> The name of the disk (a label). In most case, you set your diskname
> to the diskdevice and you don't set the diskdevice. If you want
> multiple entries with the same diskdevice, you must set a different
> diskname for each entry. It's the diskname that you use on the
> commandline for any Amanda command. Look at the example/disklist
> file for example.
>
> So from this, if it's the diskname that is used in the command, it
> seems that the reality is amdump is using the diskdevice instead!!
Thanks for the additional info, which certainly helps explain what is
happening to you
My understanding of the inner workings of this part of Amanda is quite
fuzzy, but assuming I have followed the program flow behind "amdump"
correctly, it looks like the code in question is found in
server-src/diskfile.c:match_disklist() , which contains the following
lines:
if ([...] &&
(match_disk(sargv[i], dp->name) ||
(dp->device && match_disk(sargv[i], dp->device {
..so I believe that in fact arguments specified on the amdump command line
are matched against BOTH the "diskname" and "diskdevice" fields, and if
either one matches the argument then that DLE is selected (which I
agree doesn't match the wording of the manpage).
(As far as I can tell from git, this code has been like that since
at least 2006.)
In this particular example I think you could work around the problem by
changing your disklist to
--
MACHINE /dir {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir {
tar
}
--
(in which case presumably using either ^/dir$ or =/dir would not match
the second DLE) ... but obviously that doesn't help if you ever want to
have a DLE which uses "include" to pull in multiple subdirectories of
/dir.
I guess another possible solution is to using disknames of a form that
are designend to be unique, e.g. something like (not tested)
> --
> MACHINE dir-main /dir {
> tar
> exclude "./subdir/*"
> }
>
> MACHINE dir-subdir /dir {
> tar
> include "./subdir/*"
> }
> --
... and use those disknames on the amdump command line... (But you
have to choose disknames carefully so your Amanda Mail Report looks
reasonable, etc.)
Nathan
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: ***UNCHECKED*** exact-match
Hi all,
Sorry to only now reply to this, but I was testing ... so the problem
is this
If I have something like this in disklist
--
MACHINE /dir {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir tar
--
and run
$ amdump CONF MACHINE ^/dir$
or
$ amdump CONF MACHINE =/dir
It works as expected the only backup made is /dir
But if I have something like this
--
MACHINE /dir {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir /dir {
tar
include "./subdir/*"
}
--
the commands
$ amdump CONF MACHINE ^/dir$
and
$ amdump CONF MACHINE =/dir
Don't work as expected, both backups (/dir and /dir/subdir) are made
From "man disklist"
diskname
The name of the disk (a label). In most case, you set your diskname
to the diskdevice and you don't set the diskdevice. If you want
multiple entries with the same diskdevice, you must set a different
diskname for each entry. It's the diskname that you use on the
commandline for any Amanda command. Look at the example/disklist
file for example.
So from this, if it's the diskname that is used in the command, it
seems that the reality is amdump is using the diskdevice instead!!
Cheers,
Nuno
On Mon, 2019-06-17 at 21:47 +, Debra S Baddorf wrote:
> I’ve been on vacation, so I’m coming late to this discussion.
> I’ve had problems trying to one-off dump a DLE is its name matches
> another name. It’s true we haven’t answered why the $ doesn’t fix
> that.
> But --
>
> I give them “nicknames”.
>
> disklist file:
> MACHINE Main2019 /dir/subdir/name/2019 ….. {
> tar
> exclude "./subdir/*"
>
> }
>
> MACHINE SubOf2019 /dir/subdir/name/2019/subdir tar
>
> Then I do dumps or restores by using the “nickname” which is not
> multiple matched.
>
> amdump CONFIG MACHINE Main2019
> amdump CONFIG MACHINE SubOf2019
>
> Deb Baddorf
> Fermilab
>
> > On Jun 11, 2019, at 9:32 PM, Jon LaBadie wrote:
> >
> > On Tue, Jun 11, 2019 at 11:47:15AM +0100, Nuno Dias wrote:
> > > Thanks, but I'm already doing that (the exclude)
> > >
> > > This is what I have in disklist
> > >
> > > MACHINE /dir/subdir/name/2019 {
> > > tar
> > > exclude "./subdir/*"
> > >
> > > }
> > >
> > > MACHINE /dir/subdir/name/2019/subdir tar
> > >
> > > Because this are very big directories, I want to dump only one
> > > every
> > > time, anyone know how I can do this?
> > >
> >
> > Two ideas
> >
> > 1) instead of trying to exclude everything you don't want,
> > consider including the one you do want. That should auto-
> > exclude all else.
> >
> > 2) have a separate DLE for each directory you want. Have
> > them do only full backups. Run your amdump in such a way
> > that only one DLE is dumped each day.
> >
> > --
> > Jon H. LaBadie j...@jgcomp.com
> > 11226 South Shore Rd. (703) 787-0688 (H)
> > Reston, VA 20190 (703) 935-6720 (C)
>
>
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
I’ve been on vacation, so I’m coming late to this discussion.
I’ve had problems trying to one-off dump a DLE is its name matches
another name. It’s true we haven’t answered why the $ doesn’t fix that.
But --
I give them “nicknames”.
disklist file:
MACHINE Main2019 /dir/subdir/name/2019 ….. {
tar
exclude "./subdir/*"
}
MACHINE SubOf2019 /dir/subdir/name/2019/subdir tar
Then I do dumps or restores by using the “nickname” which is not multiple
matched.
amdump CONFIG MACHINE Main2019
amdump CONFIG MACHINE SubOf2019
Deb Baddorf
Fermilab
> On Jun 11, 2019, at 9:32 PM, Jon LaBadie wrote:
>
> On Tue, Jun 11, 2019 at 11:47:15AM +0100, Nuno Dias wrote:
>> Thanks, but I'm already doing that (the exclude)
>>
>> This is what I have in disklist
>>
>> MACHINE /dir/subdir/name/2019 {
>> tar
>> exclude "./subdir/*"
>>
>> }
>>
>> MACHINE /dir/subdir/name/2019/subdir tar
>>
>> Because this are very big directories, I want to dump only one every
>> time, anyone know how I can do this?
>>
>
> Two ideas
>
> 1) instead of trying to exclude everything you don't want,
> consider including the one you do want. That should auto-
> exclude all else.
>
> 2) have a separate DLE for each directory you want. Have
> them do only full backups. Run your amdump in such a way
> that only one DLE is dumped each day.
>
> --
> Jon H. LaBadie j...@jgcomp.com
> 11226 South Shore Rd. (703) 787-0688 (H)
> Reston, VA 20190 (703) 935-6720 (C)
Re: ***UNCHECKED*** exact-match
On Tuesday 11 June 2019 10:00:09 am Nuno Dias wrote:
> Hi Gene,
>
> The exclude here, is to exclude a subdir that are to big to go in one
> backup, that's the reason I have another line in the disklist so I can
> backup the exclude in next backup.
>
> The quotes are necessary because sometimes users put spaces in file
> and dir names!!
>
I don't think so. The exclude is a single string beginning with a ./
which anchors it to that directory, so anything in ./auntmary is out of
reach. If that dle has more than one auntmary subdir, they will all be
skipped.
Reread the comments in your amanda.conf at the start of the dumptype's
section.
> Cheers,
> Nuno
>
> On Tue, 2019-06-11 at 07:47 -0400, Gene Heskett wrote:
> > On Tuesday 11 June 2019 06:47:15 am Nuno Dias wrote:
> > > Thanks, but I'm already doing that (the exclude)
> > >
> > > This is what I have in disklist
> > >
> > > MACHINE /dir/subdir/name/2019 {
> > > tar
> > > exclude "./subdir/*"
> >
> > looks wrong, excludes are in the dumptype specified, in the
> > amanda,conf
> >
> > ./subdir in your exclude s/b sufficient to block any and all access
> > below that level. and the dbl-qoutes at not needed.
> >
> > All of this s/b in the dumptype section in your amanda.conf, and
> > your
> > disklist should contain only the dumptype which is then referenced
> > to
> > determine if there even is an exclude, or exclude list if more than
> > 1
> > exclude, in which case the name of the exclude list is any handy
> > name to
> > identify to you, which dumptype its to be used with.
> >
> > I don't believe the disklist is scanned for any exclude info, just
> > the
> > dumptype, that is what specifies all of that profile.
> >
> > > }
> > >
> > > MACHINE /dir/subdir/name/2019/subdir tar
> > >
> > > Because this are very big directories, I want to dump only one
> >
> > every
> >
> > > time, anyone know how I can do this?
> > >
> > > Thanks
> > > Nuno
> > >
> > > On Fri, 2019-06-07 at 16:37 -0400, Jon LaBadie wrote:
> > > > On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote:
> > > > > Hi,
> > > > >
> > > > > I'm trying to use amanda to backup only one dir from a list
> > > > > of dirs
> > > > > that are in disklist file
> > > > >
> > > > > I run amdump like this
> > > > >
> > > > > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > > > > ^/dir/subdir/name/2019$
> > > > >
> > > > > and with ps I can see the amdump running
> > > > >
> > > > > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper
> > > > > MACHINE ^/dir/subdir/name/2019$
> > > > >
> > > > > The problem is instead of only one dir I have two dirs in the
> > > > > backup
> > > > >
> > > > > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g
> > > > > dumping
> > > > > (18g done (3.74%)) (15:39:26)
> > > > >
> > > > > MACHINE:/dir/subdir/name/2019/another 20190606153859
> > > > > 1 244g
> > > > > wait for dumping
> > > > >
> > > > >
> > > > > From the amanda-match man page
> > > > >
> > > > > /usr$
> > > > > Will match the disks /usr but not /usr/local.
> > > > >
> > > > > So, this is a bug or I'm doing something wrong?
> > > >
> > > > Not wrong, just a misconception.
> > > > The directory you give is a "starting" directory. amdump will
> > > > backup everything under that directory unless it could cross
> > > > a mount point (file system) or if something is excluded.
> > > >
> > > > So, assuming you have a DLE for ".../2019" and that your
> >
> > "another"
> >
> > > > directory is the only problem, add a directive to the DLE to
> > > > exclude another. If you don't have a DLE for 2019, PERHAPS
> > > > the -o option to amdump can be used to add an exclude directive.
> > > > I don't know if it can or cannot.
> > > >
> > > > Jon
> > > >
> > > > > I'm using amanda-3.5.1-16.fc29.x86_64
> > > > >
> > > > > thanks,
> > > > > Nuno
> > > > > --
> > > > > Nuno Dias
> > > > > LIP
> > > > >
> > > > > > > End of included message <<<
> >
> > Copyright 2019 by Maurice E. Heskett
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page
Copyright 2019 by Maurice E. Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page
Re: ***UNCHECKED*** exact-match
On Tue, Jun 11, 2019 at 11:47:15AM +0100, Nuno Dias wrote:
> Thanks, but I'm already doing that (the exclude)
>
> This is what I have in disklist
>
> MACHINE /dir/subdir/name/2019 {
> tar
> exclude "./subdir/*"
>
> }
>
> MACHINE /dir/subdir/name/2019/subdir tar
>
> Because this are very big directories, I want to dump only one every
> time, anyone know how I can do this?
>
Two ideas
1) instead of trying to exclude everything you don't want,
consider including the one you do want. That should auto-
exclude all else.
2) have a separate DLE for each directory you want. Have
them do only full backups. Run your amdump in such a way
that only one DLE is dumped each day.
--
Jon H. LaBadie j...@jgcomp.com
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (703) 935-6720 (C)
Re: ***UNCHECKED*** exact-match
On Tue, Jun 11, 2019 at 07:47:20 -0400, Gene Heskett wrote:
> On Tuesday 11 June 2019 06:47:15 am Nuno Dias wrote:
> > This is what I have in disklist
> >
> > MACHINE /dir/subdir/name/2019 {
> > tar
> > exclude "./subdir/*"
>
> All of this s/b in the dumptype section in your amanda.conf, and your
> disklist should contain only the dumptype which is then referenced to
Gene, this option is indeed defined in the dumptype for the DLE in
question, but using an "in-line" dumptype definition rather than a
separate dumptype defined in amanda.conf. Search the disklist(5) man
page for "in-line" for more info.
(In this case you wouldn't want to have a separate dumptype defined in
your amanda.conf, because only this one partcular DLE uses that specific
exclude pattern. For this sort of one-off use, you can just do it
in-line within the disklist file and avoid having to edit amanda.conf
for each one [and you don't have to come up with new names for all the
one-off dumptypes...].)
Nathan
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: ***UNCHECKED*** exact-match
Hi Gene,
The exclude here, is to exclude a subdir that are to big to go in one
backup, that's the reason I have another line in the disklist so I can
backup the exclude in next backup.
The quotes are necessary because sometimes users put spaces in file
and dir names!!
Cheers,
Nuno
On Tue, 2019-06-11 at 07:47 -0400, Gene Heskett wrote:
> On Tuesday 11 June 2019 06:47:15 am Nuno Dias wrote:
>
> > Thanks, but I'm already doing that (the exclude)
> >
> > This is what I have in disklist
> >
> > MACHINE /dir/subdir/name/2019 {
> > tar
> > exclude "./subdir/*"
>
> looks wrong, excludes are in the dumptype specified, in the
> amanda,conf
>
> ./subdir in your exclude s/b sufficient to block any and all access
> below that level. and the dbl-qoutes at not needed.
>
> All of this s/b in the dumptype section in your amanda.conf, and
> your
> disklist should contain only the dumptype which is then referenced
> to
> determine if there even is an exclude, or exclude list if more than
> 1
> exclude, in which case the name of the exclude list is any handy name
> to
> identify to you, which dumptype its to be used with.
>
> I don't believe the disklist is scanned for any exclude info, just
> the
> dumptype, that is what specifies all of that profile.
> > }
> >
> > MACHINE /dir/subdir/name/2019/subdir tar
> >
> > Because this are very big directories, I want to dump only one
> every
> > time, anyone know how I can do this?
> >
> > Thanks
> > Nuno
> >
> > On Fri, 2019-06-07 at 16:37 -0400, Jon LaBadie wrote:
> > > On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote:
> > > > Hi,
> > > >
> > > > I'm trying to use amanda to backup only one dir from a list of
> > > > dirs
> > > > that are in disklist file
> > > >
> > > > I run amdump like this
> > > >
> > > > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > > > ^/dir/subdir/name/2019$
> > > >
> > > > and with ps I can see the amdump running
> > > >
> > > > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper
> > > > MACHINE ^/dir/subdir/name/2019$
> > > >
> > > > The problem is instead of only one dir I have two dirs in the
> > > > backup
> > > >
> > > > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g
> > > > dumping
> > > > (18g done (3.74%)) (15:39:26)
> > > >
> > > > MACHINE:/dir/subdir/name/2019/another 20190606153859
> > > > 1 244g
> > > > wait for dumping
> > > >
> > > >
> > > > From the amanda-match man page
> > > >
> > > > /usr$
> > > > Will match the disks /usr but not /usr/local.
> > > >
> > > > So, this is a bug or I'm doing something wrong?
> > >
> > > Not wrong, just a misconception.
> > > The directory you give is a "starting" directory. amdump will
> > > backup everything under that directory unless it could cross
> > > a mount point (file system) or if something is excluded.
> > >
> > > So, assuming you have a DLE for ".../2019" and that your
> "another"
> > > directory is the only problem, add a directive to the DLE to
> > > exclude another. If you don't have a DLE for 2019, PERHAPS
> > > the -o option to amdump can be used to add an exclude directive.
> > > I don't know if it can or cannot.
> > >
> > > Jon
> > >
> > > > I'm using amanda-3.5.1-16.fc29.x86_64
> > > >
> > > > thanks,
> > > > Nuno
> > > > --
> > > > Nuno Dias
> > > > LIP
> > > >
> > > > > > End of included message <<<
>
>
>
> Copyright 2019 by Maurice E. Heskett
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page
>
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
On Tuesday 11 June 2019 06:47:15 am Nuno Dias wrote:
> Thanks, but I'm already doing that (the exclude)
>
> This is what I have in disklist
>
> MACHINE /dir/subdir/name/2019 {
> tar
> exclude "./subdir/*"
looks wrong, excludes are in the dumptype specified, in the amanda,conf
./subdir in your exclude s/b sufficient to block any and all access
below that level. and the dbl-qoutes at not needed.
All of this s/b in the dumptype section in your amanda.conf, and your
disklist should contain only the dumptype which is then referenced to
determine if there even is an exclude, or exclude list if more than 1
exclude, in which case the name of the exclude list is any handy name to
identify to you, which dumptype its to be used with.
I don't believe the disklist is scanned for any exclude info, just the
dumptype, that is what specifies all of that profile.
> }
>
> MACHINE /dir/subdir/name/2019/subdir tar
>
> Because this are very big directories, I want to dump only one every
> time, anyone know how I can do this?
>
> Thanks
> Nuno
>
> On Fri, 2019-06-07 at 16:37 -0400, Jon LaBadie wrote:
> > On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote:
> > > Hi,
> > >
> > > I'm trying to use amanda to backup only one dir from a list of
> > > dirs
> > > that are in disklist file
> > >
> > > I run amdump like this
> > >
> > > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > > ^/dir/subdir/name/2019$
> > >
> > > and with ps I can see the amdump running
> > >
> > > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper
> > > MACHINE ^/dir/subdir/name/2019$
> > >
> > > The problem is instead of only one dir I have two dirs in the
> > > backup
> > >
> > > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g
> > > dumping
> > > (18g done (3.74%)) (15:39:26)
> > >
> > > MACHINE:/dir/subdir/name/2019/another 20190606153859
> > > 1 244g
> > > wait for dumping
> > >
> > >
> > > From the amanda-match man page
> > >
> > > /usr$
> > > Will match the disks /usr but not /usr/local.
> > >
> > > So, this is a bug or I'm doing something wrong?
> >
> > Not wrong, just a misconception.
> > The directory you give is a "starting" directory. amdump will
> > backup everything under that directory unless it could cross
> > a mount point (file system) or if something is excluded.
> >
> > So, assuming you have a DLE for ".../2019" and that your "another"
> > directory is the only problem, add a directive to the DLE to
> > exclude another. If you don't have a DLE for 2019, PERHAPS
> > the -o option to amdump can be used to add an exclude directive.
> > I don't know if it can or cannot.
> >
> > Jon
> >
> > > I'm using amanda-3.5.1-16.fc29.x86_64
> > >
> > > thanks,
> > > Nuno
> > > --
> > > Nuno Dias
> > > LIP
> > >
> > > > > End of included message <<<
Copyright 2019 by Maurice E. Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page
Re: ***UNCHECKED*** exact-match
Thanks, but I'm already doing that (the exclude)
This is what I have in disklist
MACHINE /dir/subdir/name/2019 {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir/name/2019/subdir tar
Because this are very big directories, I want to dump only one every
time, anyone know how I can do this?
Thanks
Nuno
On Fri, 2019-06-07 at 16:37 -0400, Jon LaBadie wrote:
> On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote:
> > Hi,
> >
> > I'm trying to use amanda to backup only one dir from a list of
> > dirs
> > that are in disklist file
> >
> > I run amdump like this
> >
> > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > ^/dir/subdir/name/2019$
> >
> > and with ps I can see the amdump running
> >
> > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > ^/dir/subdir/name/2019$
> >
> > The problem is instead of only one dir I have two dirs in the
> > backup
> >
> > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g
> > dumping
> > (18g done (3.74%)) (15:39:26)
> >
> > MACHINE:/dir/subdir/name/2019/another 20190606153859
> > 1 244g
> > wait for dumping
> >
> >
> > From the amanda-match man page
> >
> > /usr$
> > Will match the disks /usr but not /usr/local.
> >
> > So, this is a bug or I'm doing something wrong?
> >
> Not wrong, just a misconception.
> The directory you give is a "starting" directory. amdump will
> backup everything under that directory unless it could cross
> a mount point (file system) or if something is excluded.
>
> So, assuming you have a DLE for ".../2019" and that your "another"
> directory is the only problem, add a directive to the DLE to
> exclude another. If you don't have a DLE for 2019, PERHAPS
> the -o option to amdump can be used to add an exclude directive.
> I don't know if it can or cannot.
>
> Jon
> > I'm using amanda-3.5.1-16.fc29.x86_64
> >
> > thanks,
> > Nuno
> > --
> > Nuno Dias
> > LIP
> > > > End of included message <<<
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote: > Hi, > > I'm trying to use amanda to backup only one dir from a list of dirs > that are in disklist file > > I run amdump like this > > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE > ^/dir/subdir/name/2019$ > > and with ps I can see the amdump running > > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper MACHINE > ^/dir/subdir/name/2019$ > > The problem is instead of only one dir I have two dirs in the backup > > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g dumping > (18g done (3.74%)) (15:39:26) > > MACHINE:/dir/subdir/name/2019/another 20190606153859 1 244g > wait for dumping > > > From the amanda-match man page > > /usr$ > Will match the disks /usr but not /usr/local. > > So, this is a bug or I'm doing something wrong? > Not wrong, just a misconception. The directory you give is a "starting" directory. amdump will backup everything under that directory unless it could cross a mount point (file system) or if something is excluded. So, assuming you have a DLE for ".../2019" and that your "another" directory is the only problem, add a directive to the DLE to exclude another. If you don't have a DLE for 2019, PERHAPS the -o option to amdump can be used to add an exclude directive. I don't know if it can or cannot. Jon > I'm using amanda-3.5.1-16.fc29.x86_64 > > thanks, > Nuno > -- > Nuno Dias > LIP >>> End of included message <<< -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
