Re: Only increasing incrementals

[Gene Heskett]

On Wednesday 12 December 2018 17:10:08 Jon LaBadie wrote:

> On Wed, Dec 12, 2018 at 02:18:57PM +0700, Olivier wrote:
> > Nathan Stratton Treadway  writes:
> > > On Thu, Nov 22, 2018 at 11:18:25 +0700, Olivier wrote:
> > >> Hello,
> > >>
> > >> UI am wondering if there is a way to define a DLE that would all
> > >> incrementals but only with increasing level:
> > >>
> > >> - full (0)
> > >> - incremental 1
> > >> - incremental 2
> > >> - incremental 3
> > >> - etc.
> > >>
> > >> But never: 0, 1, 1, 1, 2
> > >>
> > >> Each back-up level must be above the previous one or be a full
> > >> back-up.
>
> Have you tried:
>
>   bumpdays0
>   bumpmult0
>   bumppercent 0
>   bumpsize0
>
> I don't know if it will work, or maybe bork somehow.
>
> Jon

ISTR I did something like that, back up  the log a year or so, and 
amcheck had a hungry bawling calf.  Anytime you do something odd, let 
amcheck see if it has an opinion. It does try to make you miss your foot 
when shooting at it.

Copyright 2018 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: amgtar application: exclude lists

[Gene Heskett]

On Wednesday 12 December 2018 14:31:06 Stefan G. Weichinger wrote:

> Am 12.12.18 um 19:38 schrieb Gene Heskett:
> > On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:
> >> Am 12.12.18 um 17:32 schrieb Gene Heskett:
> >>> On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
>  I only recently reconfigure some older servers to use the
>  application amgtar instead of "GNUTAR"
> 
>  Now my old exclude lists aren't read anymore and the manpages
>  aren't as informative as I would need them ;-)
> 
>  How to configure an exclude-list for amgtar, per DLE?
> 
>  I tried:
> 
> 
>  define dumptype global {
> 
>   program "APPLICATION"
>   application "app_amgtar"
>   # yes, I also defined that application above
> 
>  [..]
> 
>  }
> 
>  #disklist
> 
>  main root / {
>  property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
> 
>  [..]
> 
>  }
> 
>  Maybe that glob has to be on the client? manpage only says:
> 
>  "EXCLUDE-LIST-GLOB
>  A filename containing exclude glob expression for the restore
>  command."
> 
>  whoa, "for restore" ... what about dump time?
> >>>
> >>> It has been specified in the dumptype, I think since before I
> >>> started useing it it the late '90's. I tend to keep my named
> >>> exclude lists in my /GenesAmandaHelper-0.61 directory. Clutters it
> >>> some, but it seems handier to have a fixed location, but it is on
> >>> a per client basis, so the excludes are unique to the client,
> >>> achieved in the dumptype, which is unique to that client,
> >>> sometimes 4 or more per client as os stuff is on the install cd if
> >>> the disk should choke and die.
> >>
> >> example?
> >>
> >> still the "exclude list" parameter? IMO the manpage doesn't tell
> >> the exact syntax here.
> >
> > Perhaps the thing glossed over is that in the file the list points
> > to, insufficient emphasis is placed on the format of a line, it
> > needs an anchor point of ./ so that it only applies to that file, or
> > dir and below it if the name is a directory.
> >
> > As for an example:
> >
> > define dumptype shop-tar-comp {
> >  global
> >  compress client best
> >  exclude list "/GenesAmandaHelper-0.61/excludes"
> > }
> >
> > And that excludes list files content:
> >
> > ./*.iso
> > ./.gvfs
> > ./Ksocket-gene
> > ./orbit-gene
> > ./init
> > ./lock
> > ./run
> > ./rpc_pipefs
> >
> >
> > The filename itself is I think immaterial as long as its matched.
> > "excludes" above could both be one of the Kardashians. ;-)
>
> I had it exactly like that and it seemed to have stopped working with
> amgtar. Rechecked it, a single DLE test run looks good now. Thanks to
> you, Gene.

I'm going to have to quit this, everybody will think I am an expert. ;)


Copyright 2018 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: Only increasing incrementals

[Debra S Baddorf]

Oh, that’s right — Chris DID tell us what he was trying to do,  last week:
(in case it helps with any further answers)

> On Dec 7, 2018, at 12:04 PM, Chris Miller  wrote:
> 
> Hi Folks,
> 
> I'm about to start a project during which I want to be able to:
>   • Request a backup at any moment and have that backup be either an 
> incremental backup (Level N+1), meaning everything that has changed since the 
> last backup (Level N), or a differential backup, meaning everything that has 
> changed since the last full backup (Level 1). The second provision, 
> "differential backup" is pretty straight forward, but I have no idea how to 
> configure a constantly increasing dump level.
>   • The first backup of the day, meaning the first backup after midnight, 
> will be a full filesystem backup.
> 
> Discussion on point 1:
> The provision is for capturing changes that occur during a given period of 
> time, and no so much for "backup" per se, so AMANDA may not be the best tool, 
> but it is what I have, so I'm tying to make it fit. I know how to request a 
> backup, so that's not my problem, but I don't know how to force a given 
> level. In particular, I don't know how to force a Level N+1 backup. I could 
> replace the Level N+1 requirement with a forced Level 1, run my experiment, 
> and force a level 2, and this would meet my requirement of capturing all the 
> changes during a particular interval. But, again, that requires forcing 
> AMANDA to take direction about backup levels and I don't know how to do that.
> 
> Before anybody reminds me that this is why god invented git, I would like to 
> add, that the scope of git is typically only known parts of the project, and 
> I want to capture log files and other files that are sometimes created in 
> temporary locations with temporary names, which are not known a priori and 
> therefore can't be "managed" with git.
> 
> Discussion on point 2:
> The "first backup of the day", will run as a cron job, but it must be a level 
> 0, full filesystem backup so no work for the day is lost. It is more forcing 
> AMANDA to take direction, I don't know exactly how to do this.
> 
> I don't think I like the idea of forcing AMANDA (#MeToo) to do things, but 
> I'm not above payment in kind. (-:
> 
> Thanks for the help,
> --
> Chris.
> 
> V:916.974.0424
> F:916.974.0428

Re: Only increasing incrementals

[Jon LaBadie]

On Wed, Dec 12, 2018 at 02:18:57PM +0700, Olivier wrote:
> Nathan Stratton Treadway  writes:
> 
> > On Thu, Nov 22, 2018 at 11:18:25 +0700, Olivier wrote:
> >> Hello,
> >> 
> >> UI am wondering if there is a way to define a DLE that would all
> >> incrementals but only with increasing level:
> >> 
> >> - full (0)
> >> - incremental 1
> >> - incremental 2
> >> - incremental 3
> >> - etc.
> >> 
> >> But never: 0, 1, 1, 1, 2
> >> 
> >> Each back-up level must be above the previous one or be a full back-up.
> >

Have you tried:

  bumpdays0
  bumpmult0
  bumppercent 0
  bumpsize0

I don't know if it will work, or maybe bork somehow.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: amgtar application: exclude lists

[Stefan G. Weichinger]

Am 12.12.18 um 19:38 schrieb Gene Heskett:

On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:


Am 12.12.18 um 17:32 schrieb Gene Heskett:

On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:

I only recently reconfigure some older servers to use the
application amgtar instead of "GNUTAR"

Now my old exclude lists aren't read anymore and the manpages
aren't as informative as I would need them ;-)

How to configure an exclude-list for amgtar, per DLE?

I tried:


define dumptype global {

 program "APPLICATION"
 application "app_amgtar"
 # yes, I also defined that application above

[..]

}

#disklist

main root / {
property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"

[..]

}

Maybe that glob has to be on the client? manpage only says:

"EXCLUDE-LIST-GLOB
A filename containing exclude glob expression for the restore
command."

whoa, "for restore" ... what about dump time?


It has been specified in the dumptype, I think since before I
started useing it it the late '90's. I tend to keep my named exclude
lists in my /GenesAmandaHelper-0.61 directory. Clutters it some, but
it seems handier to have a fixed location, but it is on a per client
basis, so the excludes are unique to the client, achieved in the
dumptype, which is unique to that client, sometimes 4 or more per
client as os stuff is on the install cd if the disk should choke and
die.


example?

still the "exclude list" parameter? IMO the manpage doesn't tell the
exact syntax here.


Perhaps the thing glossed over is that in the file the list points to,
insufficient emphasis is placed on the format of a line, it needs an
anchor point of ./ so that it only applies to that file, or dir and
below it if the name is a directory.

As for an example:

define dumptype shop-tar-comp {
 global
 compress client best
 exclude list "/GenesAmandaHelper-0.61/excludes"
}

And that excludes list files content:

./*.iso
./.gvfs
./Ksocket-gene
./orbit-gene
./init
./lock
./run
./rpc_pipefs


The filename itself is I think immaterial as long as its matched.
"excludes" above could both be one of the Kardashians. ;-)


I had it exactly like that and it seemed to have stopped working with 
amgtar. Rechecked it, a single DLE test run looks good now. Thanks to 
you, Gene.

Re: Only increasing incrementals

[Debra S Baddorf]

> On Dec 12, 2018, at 6:09 AM, Austin S. Hemmelgarn  
> wrote:
> 
> On 2018-12-12 02:18, Olivier wrote:
>> Nathan Stratton Treadway  writes:
>>> On Thu, Nov 22, 2018 at 11:18:25 +0700, Olivier wrote:
 Hello,
 
 UI am wondering if there is a way to define a DLE that would all
 incrementals but only with increasing level:
 
 - full (0)
 - incremental 1
 - incremental 2
 - incremental 3
 - etc.
 
 But never: 0, 1, 1, 1, 2
 
 Each back-up level must be above the previous one or be a full back-up.
>>> 
>>> I am not sure what you are trying to accomplish,
>> I am trying to backup something that can only have incremental with
>> increasing levels: it cannot do two level 1 in a row, levels must be 1,
>> then 2, then 3, etc. (think some successive snapshots).
>> According to amanda.conf(5) man page:
>>bumpdays int
>>Default: 2 days. To insure redundancy in the dumps, Amanda keeps
>>filesystems at the same incremental level for at least bumpdays
>>days, even if the other bump threshold criteria are met.
>> I want to absolutely cancel that feature, each incremental must have a
>> level creater than the previous dump and an incremental level can not be
>> bumped (only level 0 can be bumped).
> OK, I"m actually curious what your exact reasoning for requiring this is, 
> because I'm seeing exactly zero circumstances where this makes sense at all, 
> and can think of multiple ways it's a bad thing (for example, losing your 
> level one incremental makes all of your backups for that cycle useless).


Ditto.  I’d like to know the problem that you are trying to solve.

 Also,  as far as I know, amanda does something to every DLE, every time you 
run amdump.  
It won’t skip the DLE just because no changes have occurred.
You might go up to really odd levels of incremental, if you have even a 
week-long cycle.   Level 0, 1, 2, 3, 4, 5, 6.
Some might even be empty,  if nothing has changed.  But it’ll have to create 
them anyway.
Unless you tell it your "dumpcycle”   is only 4  or 3 days long.  Or some such.
And then you are forced to have all of those tapes (vtapes)  available for any 
backup.

You could possibly do  “amadmin config  force-bump”   every night,  in your 
cronjob.

Just random thoughts, since we don’t understand the actual problem.

Deb Baddorf

Re: amgtar application: exclude lists

[Gene Heskett]

On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:

> Am 12.12.18 um 17:32 schrieb Gene Heskett:
> > On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> >> I only recently reconfigure some older servers to use the
> >> application amgtar instead of "GNUTAR"
> >>
> >> Now my old exclude lists aren't read anymore and the manpages
> >> aren't as informative as I would need them ;-)
> >>
> >> How to configure an exclude-list for amgtar, per DLE?
> >>
> >> I tried:
> >>
> >>
> >> define dumptype global {
> >>
> >> program "APPLICATION"
> >> application "app_amgtar"
> >> # yes, I also defined that application above
> >>
> >> [..]
> >>
> >> }
> >>
> >> #disklist
> >>
> >> main root / {
> >> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
> >>
> >> [..]
> >>
> >> }
> >>
> >> Maybe that glob has to be on the client? manpage only says:
> >>
> >> "EXCLUDE-LIST-GLOB
> >> A filename containing exclude glob expression for the restore
> >> command."
> >>
> >> whoa, "for restore" ... what about dump time?
> >
> > It has been specified in the dumptype, I think since before I
> > started useing it it the late '90's. I tend to keep my named exclude
> > lists in my /GenesAmandaHelper-0.61 directory. Clutters it some, but
> > it seems handier to have a fixed location, but it is on a per client
> > basis, so the excludes are unique to the client, achieved in the
> > dumptype, which is unique to that client, sometimes 4 or more per
> > client as os stuff is on the install cd if the disk should choke and
> > die.
>
> example?
>
> still the "exclude list" parameter? IMO the manpage doesn't tell the
> exact syntax here.

The man page has been squashed, needs help, so use your amanda.conf, its 
all explained in there.


Copyright 2018 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: amgtar application: exclude lists

[Gene Heskett]

On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:

> Am 12.12.18 um 17:32 schrieb Gene Heskett:
> > On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> >> I only recently reconfigure some older servers to use the
> >> application amgtar instead of "GNUTAR"
> >>
> >> Now my old exclude lists aren't read anymore and the manpages
> >> aren't as informative as I would need them ;-)
> >>
> >> How to configure an exclude-list for amgtar, per DLE?
> >>
> >> I tried:
> >>
> >>
> >> define dumptype global {
> >>
> >> program "APPLICATION"
> >> application "app_amgtar"
> >> # yes, I also defined that application above
> >>
> >> [..]
> >>
> >> }
> >>
> >> #disklist
> >>
> >> main root / {
> >> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
> >>
> >> [..]
> >>
> >> }
> >>
> >> Maybe that glob has to be on the client? manpage only says:
> >>
> >> "EXCLUDE-LIST-GLOB
> >> A filename containing exclude glob expression for the restore
> >> command."
> >>
> >> whoa, "for restore" ... what about dump time?
> >
> > It has been specified in the dumptype, I think since before I
> > started useing it it the late '90's. I tend to keep my named exclude
> > lists in my /GenesAmandaHelper-0.61 directory. Clutters it some, but
> > it seems handier to have a fixed location, but it is on a per client
> > basis, so the excludes are unique to the client, achieved in the
> > dumptype, which is unique to that client, sometimes 4 or more per
> > client as os stuff is on the install cd if the disk should choke and
> > die.
>
> example?
>
> still the "exclude list" parameter? IMO the manpage doesn't tell the
> exact syntax here.

Perhaps the thing glossed over is that in the file the list points to, 
insufficient emphasis is placed on the format of a line, it needs an 
anchor point of ./ so that it only applies to that file, or dir and 
below it if the name is a directory. 

As for an example:

define dumptype shop-tar-comp {
global
compress client best
exclude list "/GenesAmandaHelper-0.61/excludes"
}

And that excludes list files content:

./*.iso
./.gvfs
./Ksocket-gene
./orbit-gene
./init
./lock
./run
./rpc_pipefs


The filename itself is I think immaterial as long as its matched.
"excludes" above could both be one of the Kardashians. ;-)
 
Copyright 2018 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: amgtar application: exclude lists

[Stefan G. Weichinger]

Am 12.12.18 um 17:32 schrieb Gene Heskett:
> On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> 
>> I only recently reconfigure some older servers to use the application
>> amgtar instead of "GNUTAR"
>>
>> Now my old exclude lists aren't read anymore and the manpages aren't
>> as informative as I would need them ;-)
>>
>> How to configure an exclude-list for amgtar, per DLE?
>>
>> I tried:
>>
>>
>> define dumptype global {
>>
>> program "APPLICATION"
>> application "app_amgtar"
>> # yes, I also defined that application above
>>
>> [..]
>>
>> }
>>
>> #disklist
>>
>> main root / {
>> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
>>
>> [..]
>>
>> }
>>
>> Maybe that glob has to be on the client? manpage only says:
>>
>> "EXCLUDE-LIST-GLOB
>> A filename containing exclude glob expression for the restore
>> command."
>>
>> whoa, "for restore" ... what about dump time?
> 
> It has been specified in the dumptype, I think since before I started 
> useing it it the late '90's. I tend to keep my named exclude lists in 
> my /GenesAmandaHelper-0.61 directory. Clutters it some, but it seems 
> handier to have a fixed location, but it is on a per client basis, so 
> the excludes are unique to the client, achieved in the dumptype, which 
> is unique to that client, sometimes 4 or more per client as os stuff is 
> on the install cd if the disk should choke and die.

example?

still the "exclude list" parameter? IMO the manpage doesn't tell the
exact syntax here.

Re: amgtar application: exclude lists

[Gene Heskett]

On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:

> I only recently reconfigure some older servers to use the application
> amgtar instead of "GNUTAR"
>
> Now my old exclude lists aren't read anymore and the manpages aren't
> as informative as I would need them ;-)
>
> How to configure an exclude-list for amgtar, per DLE?
>
> I tried:
>
>
> define dumptype global {
>
> program "APPLICATION"
> application "app_amgtar"
> # yes, I also defined that application above
>
> [..]
>
> }
>
> #disklist
>
> main root / {
> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
>
> [..]
>
> }
>
> Maybe that glob has to be on the client? manpage only says:
>
> "EXCLUDE-LIST-GLOB
> A filename containing exclude glob expression for the restore
> command."
>
> whoa, "for restore" ... what about dump time?

It has been specified in the dumptype, I think since before I started 
useing it it the late '90's. I tend to keep my named exclude lists in 
my /GenesAmandaHelper-0.61 directory. Clutters it some, but it seems 
handier to have a fixed location, but it is on a per client basis, so 
the excludes are unique to the client, achieved in the dumptype, which 
is unique to that client, sometimes 4 or more per client as os stuff is 
on the install cd if the disk should choke and die.

Copyright 2018 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 

amgtar application: exclude lists

[Stefan G. Weichinger]

I only recently reconfigure some older servers to use the application
amgtar instead of "GNUTAR"

Now my old exclude lists aren't read anymore and the manpages aren't as
informative as I would need them ;-)

How to configure an exclude-list for amgtar, per DLE?

I tried:


define dumptype global {

program "APPLICATION"
application "app_amgtar"
# yes, I also defined that application above

[..]

}

#disklist

main root / {
property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"

[..]

}

Maybe that glob has to be on the client? manpage only says:

"EXCLUDE-LIST-GLOB
A filename containing exclude glob expression for the restore command."

whoa, "for restore" ... what about dump time?

Re: Only increasing incrementals

[Austin S. Hemmelgarn]

On 2018-12-12 02:18, Olivier wrote:

Nathan Stratton Treadway  writes:


On Thu, Nov 22, 2018 at 11:18:25 +0700, Olivier wrote:

Hello,

UI am wondering if there is a way to define a DLE that would all
incrementals but only with increasing level:

- full (0)
- incremental 1
- incremental 2
- incremental 3
- etc.

But never: 0, 1, 1, 1, 2

Each back-up level must be above the previous one or be a full back-up.


I am not sure what you are trying to accomplish,


I am trying to backup something that can only have incremental with
increasing levels: it cannot do two level 1 in a row, levels must be 1,
then 2, then 3, etc. (think some successive snapshots).

According to amanda.conf(5) man page:

bumpdays int
Default: 2 days. To insure redundancy in the dumps, Amanda keeps
filesystems at the same incremental level for at least bumpdays
days, even if the other bump threshold criteria are met.

I want to absolutely cancel that feature, each incremental must have a
level creater than the previous dump and an incremental level can not be
bumped (only level 0 can be bumped).
OK, I"m actually curious what your exact reasoning for requiring this 
is, because I'm seeing exactly zero circumstances where this makes sense 
at all, and can think of multiple ways it's a bad thing (for example, 
losing your level one incremental makes all of your backups for that 
cycle useless).