Re: Amanda's DB

[Nathan Stratton Treadway]

On Wed, Nov 14, 2018 at 15:35:50 -0500, Chris Nighswonger wrote:
> Can anyone point me to "good" documentation that describes Amanda's DB?
> Things like schema, field descriptions and/or uses, etc.
> 
> It looks like maybe they are located in
> '/var/backups/jobname/index|curinfo' ? So flat files?

Yes, those are flat files.  I haven't run across specific documentation
for them (though I can't say I've looked hard for it).

The "index" files (up through Amanda 3.3, anyway) are just the plain
file/directory names pulled out of the dump-archives, and they are used
to present you with the list of directories/files that can be recovered
in "amrecover".

The curinfo files feel like a simple dump-to-text of in-memory data
structures (the datetime stamps are seconds-since-the-unix-epoch, for
example, and spaces are used to separate unlabeled fields on the lines).


Two other (interrelated) categories of data that Amanda maintains are
the tapelist file, and the log.DATETIMESTAMP files (in the same
directory as the amdump.DATETIMESTAP files).  There is a "tapelist" man
page to describe the former; the latter records the mapping of which
dumps were written to which volume.

> I notice that the later versions of ZWC use SQL.

I saw that the Amanda source repository master branch includes the
following commit:

commit ea4dd29d265b44a914e794d5150e53bce9d9435d
Author: Jean-Louis Martineau 
Date:   Thu Jan 4 12:52:28 2018 +

Use a database (SQLite, MySQL or ProstgreSQL) to replace the tapelist
and log.* file
Read the Amanda-Catalog file
* perl/*, server-src/*, common-src/conffile.c: Major changes
* installcheck/*: Fix tests
* Amanda-Catalog: New documentation document

Jan 2018 is after Amanda 3.5 was released so this is still
work-in-progress, and I don't know how "mature" this transition got
before Jean-Louis left 

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: Amanda's DB

[Gene Heskett]

On Wednesday 14 November 2018 15:35:50 Chris Nighswonger wrote:

> Can anyone point me to "good" documentation that describes Amanda's
> DB? Things like schema, field descriptions and/or uses, etc.
>
> It looks like maybe they are located in
> '/var/backups/jobname/index|curinfo' ? So flat files?
>
> I notice that the later versions of ZWC use SQL.
>
> Kind regards,
> Chris

What I have here Deb, is in /usr/local/var/amanda because its a 
prefix=/usr/local build, and are flat files. I can read them by 
highlighting them in mc, and hitting F3. No database encryption or 
security involved. The only protection is the sandbox of the amanda usr, 
who has no login. Only access is from root via su.

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: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Gene Heskett]

On Wednesday 14 November 2018 15:30:11 Debra S Baddorf wrote:

> > On Nov 14, 2018, at 2:18 PM, Gene Heskett 
> > wrote:
> >
> > On Wednesday 14 November 2018 15:11:33 Debra S Baddorf wrote:
> >>> On Nov 14, 2018, at 2:04 PM, Gene Heskett 
> >>> wrote:
> >>>
> >>> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
>  On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> > First a snip/paste of my 3 new del's as I try to split a big one
> > up: line entry
> > 28 coyote /home/gene/PublicA/ Publicag {
> > 29  comp-coyote-tar
> > 30  include "./[a-g]*"
> > 31  exclude "./[h-z]*"
> > 32  } 1 local
> > 33
> 
>  Chris already got the syntax error.
> 
>  I'll just note you do not need both the include
>  and the exclude lines.  The "include" says these
>  are the only things to backup.
> 
>  If "comp-coyote-tar" has any common excludes (like
>  temp files or ???) the exclude above would replace
>  them.  If you want to retain the excludes, you may
>  want to make them "exclude append" to add to any
>  default exclude.
> 
>  What if you create a "Gene" or a "123go" or a ".save"
>  file or directory under PublicA?  Your 3 DLEs would
>  not back them up.  I usually add a "catchall" DLE.
> 
>  In your case it might be:
> > 28 coyote PublicMisc /home/gene/PublicA/ {
> > 29  comp-coyote-tar
> > 31  exclude "./[a-z]*"
> > 32  } 1 local
> 
>  Jon
> >>>
> >>> Probably a good idea now that  you mention it Jon, there are some
> >>> files that start with numbers.
> >>>
> >>> Are the alpha's case sensitive?
> >>>
> >>> Meaning should I make one for include "./[0-9]*" "./[A-Z]*"
> >>> perhaps? Something like:
> >>>
> >>> coyote PublicA09AZ /home/gene/PublicA {
> >>>   comp-coyote-tar
> >>>   include "./[0-9]*" "./[A-Z]*"
> >>>   ] 1 local
> >>>
> >>> to cover everything else? Done.
> >>
> >> Yes, they are case sensitive.   If you have only a few numbers of
> >> capital letters,  they make perfect candidates for that Misc data
> >> set. You really DO need to have that,  in case you dump a file
> >> there later that doesn’t fit any of the “include”  rules you’ve
> >> remembered to use.
> >>
> >> Also,  a tar backup fails  (for me)  if it has NO contents.  So you
> >> need to save a few things, like the numbers or capitals letters, 
> >> that really do already exist — so that the Misc set isn’t empty.
> >>
> >> Deb Baddorf
> >
> > Thanks for the headsup Deb, but I am positive there will be hits for
> > the above entry. Tonight. or should I say tomorrow morning should
> > tell that tale. Amcheck is saying it should work.
>
> I wasn’t so much worried about contents existing for your nice  0-9
> and CAPS set ….. it’s the “LeftOvers” set that worried me.  It can’t
> be empty.
>
With the addition of the last one, I don't think there will be 
any "leftovers" as there aren't any  .files

> And I’m not certain that amcheck  cares, I don’t think it’ll tell you
> if the set is empty. Let’s see how tomorrow goes!
> Deb Baddorf

Yes. Its entirely possible it will make a liar out of me. I do see some 
stuff "./-* and "./._*" so I'll include those too and that really should 
include all.


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: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Chris Nighswonger]

On Wed, Nov 14, 2018 at 3:34 PM Debra S Baddorf  wrote:

>
> And I’m not certain that amcheck  cares, I don’t think it’ll tell you if
> the set is empty.
>
>
It doesn't and it won't.

Kind regards,
Chris

Amanda's DB

[Chris Nighswonger]

Can anyone point me to "good" documentation that describes Amanda's DB?
Things like schema, field descriptions and/or uses, etc.

It looks like maybe they are located in
'/var/backups/jobname/index|curinfo' ? So flat files?

I notice that the later versions of ZWC use SQL.

Kind regards,
Chris

Re: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Debra S Baddorf]

> On Nov 14, 2018, at 2:18 PM, Gene Heskett  wrote:
> 
> On Wednesday 14 November 2018 15:11:33 Debra S Baddorf wrote:
> 
>>> On Nov 14, 2018, at 2:04 PM, Gene Heskett 
>>> wrote:
>>> 
>>> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
 On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> First a snip/paste of my 3 new del's as I try to split a big one
> up: line entry
> 28 coyote /home/gene/PublicA/ Publicag {
> 29comp-coyote-tar
> 30include "./[a-g]*"
> 31exclude "./[h-z]*"
> 32} 1 local
> 33
 
 Chris already got the syntax error.
 
 I'll just note you do not need both the include
 and the exclude lines.  The "include" says these
 are the only things to backup.
 
 If "comp-coyote-tar" has any common excludes (like
 temp files or ???) the exclude above would replace
 them.  If you want to retain the excludes, you may
 want to make them "exclude append" to add to any
 default exclude.
 
 What if you create a "Gene" or a "123go" or a ".save"
 file or directory under PublicA?  Your 3 DLEs would
 not back them up.  I usually add a "catchall" DLE.
 
 In your case it might be:
> 28 coyote PublicMisc /home/gene/PublicA/ {
> 29comp-coyote-tar
> 31exclude "./[a-z]*"
> 32} 1 local
 
 Jon
>>> 
>>> Probably a good idea now that  you mention it Jon, there are some
>>> files that start with numbers.
>>> 
>>> Are the alpha's case sensitive?
>>> 
>>> Meaning should I make one for include "./[0-9]*" "./[A-Z]*" perhaps?
>>> Something like:
>>> 
>>> coyote PublicA09AZ /home/gene/PublicA {
>>> comp-coyote-tar
>>> include "./[0-9]*" "./[A-Z]*"
>>> ] 1 local
>>> 
>>> to cover everything else? Done.
>> 
>> Yes, they are case sensitive.   If you have only a few numbers of
>> capital letters,  they make perfect candidates for that Misc data set.
>> You really DO need to have that,  in case you dump a file there later
>> that doesn’t fit any of the “include”  rules you’ve remembered to use.
>> 
>> Also,  a tar backup fails  (for me)  if it has NO contents.  So you
>> need to save a few things, like the numbers or capitals letters,  that
>> really do already exist — so that the Misc set isn’t empty.
>> 
>> Deb Baddorf
> Thanks for the headsup Deb, but I am positive there will be hits for the 
> above entry. Tonight. or should I say tomorrow morning should tell that 
> tale. Amcheck is saying it should work.
> 

I wasn’t so much worried about contents existing for your nice  0-9 and CAPS
set ….. it’s the “LeftOvers” set that worried me.  It can’t be empty.

And I’m not certain that amcheck  cares, I don’t think it’ll tell you if the 
set is empty.
Let’s see how tomorrow goes!
Deb Baddorf

Re: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Gene Heskett]

On Wednesday 14 November 2018 15:11:33 Debra S Baddorf wrote:

> > On Nov 14, 2018, at 2:04 PM, Gene Heskett 
> > wrote:
> >
> > On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
> >> On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> >>> First a snip/paste of my 3 new del's as I try to split a big one
> >>> up: line entry
> >>> 28 coyote /home/gene/PublicA/ Publicag {
> >>> 29comp-coyote-tar
> >>> 30include "./[a-g]*"
> >>> 31exclude "./[h-z]*"
> >>> 32} 1 local
> >>> 33
> >>
> >> Chris already got the syntax error.
> >>
> >> I'll just note you do not need both the include
> >> and the exclude lines.  The "include" says these
> >> are the only things to backup.
> >>
> >> If "comp-coyote-tar" has any common excludes (like
> >> temp files or ???) the exclude above would replace
> >> them.  If you want to retain the excludes, you may
> >> want to make them "exclude append" to add to any
> >> default exclude.
> >>
> >> What if you create a "Gene" or a "123go" or a ".save"
> >> file or directory under PublicA?  Your 3 DLEs would
> >> not back them up.  I usually add a "catchall" DLE.
> >>
> >> In your case it might be:
> >>> 28 coyote PublicMisc /home/gene/PublicA/ {
> >>> 29comp-coyote-tar
> >>> 31exclude "./[a-z]*"
> >>> 32} 1 local
> >>
> >> Jon
> >
> > Probably a good idea now that  you mention it Jon, there are some
> > files that start with numbers.
> >
> > Are the alpha's case sensitive?
> >
> > Meaning should I make one for include "./[0-9]*" "./[A-Z]*" perhaps?
> > Something like:
> >
> > coyote PublicA09AZ /home/gene/PublicA {
> > comp-coyote-tar
> > include "./[0-9]*" "./[A-Z]*"
> > ] 1 local
> >
> > to cover everything else? Done.
>
> Yes, they are case sensitive.   If you have only a few numbers of
> capital letters,  they make perfect candidates for that Misc data set.
>  You really DO need to have that,  in case you dump a file there later
> that doesn’t fit any of the “include”  rules you’ve remembered to use.
>
> Also,  a tar backup fails  (for me)  if it has NO contents.  So you
> need to save a few things, like the numbers or capitals letters,  that
> really do already exist — so that the Misc set isn’t empty.
>
> Deb Baddorf
Thanks for the headsup Deb, but I am positive there will be hits for the 
above entry. Tonight. or should I say tomorrow morning should tell that 
tale. Amcheck is saying it should work.


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: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Gene Heskett]

On Wednesday 14 November 2018 15:04:25 Gene Heskett wrote:

> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
> > On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> > > First a snip/paste of my 3 new del's as I try to split a big one
> > > up: line entry
> > > 28 coyote /home/gene/PublicA/ Publicag {
> > > 29comp-coyote-tar
> > > 30include "./[a-g]*"
> > > 31exclude "./[h-z]*"
> > > 32} 1 local
> > > 33
> >
> > Chris already got the syntax error.
> >
> > I'll just note you do not need both the include
> > and the exclude lines.  The "include" says these
> > are the only things to backup.
> >
> > If "comp-coyote-tar" has any common excludes (like
> > temp files or ???) the exclude above would replace
> > them.  If you want to retain the excludes, you may
> > want to make them "exclude append" to add to any
> > default exclude.
> >
> > What if you create a "Gene" or a "123go" or a ".save"
> > file or directory under PublicA?  Your 3 DLEs would
> > not back them up.  I usually add a "catchall" DLE.
> >
> > In your case it might be:
> > > 28 coyote PublicMisc /home/gene/PublicA/ {
> > > 29comp-coyote-tar
> > > 31exclude "./[a-z]*"
> > > 32} 1 local
> >
> > Jon
>
> Probably a good idea now that  you mention it Jon, there are some
> files that start with numbers.
>
> Are the alpha's case sensitive?
>
> Meaning should I make one for include "./[0-9]*" "./[A-Z]*" perhaps?
> Something like:
>
> coyote PublicA09AZ /home/gene/PublicA {
>   comp-coyote-tar
>   include "./[0-9]*" "./[A-Z]*"
>   ] 1 local
And the closing bracket s/b a }, danged typu's
> to cover everything else? Done.
>
> Copyright 2018 by Maurice E. Heskett



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: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Debra S Baddorf]

> On Nov 14, 2018, at 2:04 PM, Gene Heskett  wrote:
> 
> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
> 
>> On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
>>> First a snip/paste of my 3 new del's as I try to split a big one up:
>>> line entry
>>> 28 coyote /home/gene/PublicA/ Publicag {
>>> 29  comp-coyote-tar
>>> 30  include "./[a-g]*"
>>> 31  exclude "./[h-z]*"
>>> 32  } 1 local
>>> 33
>> 
>> Chris already got the syntax error.
>> 
>> I'll just note you do not need both the include
>> and the exclude lines.  The "include" says these
>> are the only things to backup.
>> 
>> If "comp-coyote-tar" has any common excludes (like
>> temp files or ???) the exclude above would replace
>> them.  If you want to retain the excludes, you may
>> want to make them "exclude append" to add to any
>> default exclude.
>> 
>> What if you create a "Gene" or a "123go" or a ".save"
>> file or directory under PublicA?  Your 3 DLEs would
>> not back them up.  I usually add a "catchall" DLE.
>> 
>> In your case it might be:
>>> 28 coyote PublicMisc /home/gene/PublicA/ {
>>> 29  comp-coyote-tar
>>> 31  exclude "./[a-z]*"
>>> 32  } 1 local
>> 
>> Jon
> 
> Probably a good idea now that  you mention it Jon, there are some files 
> that start with numbers.
> 
> Are the alpha's case sensitive? 
> 
> Meaning should I make one for include "./[0-9]*" "./[A-Z]*" perhaps?
> Something like:
> 
> coyote PublicA09AZ /home/gene/PublicA {
>   comp-coyote-tar
>   include "./[0-9]*" "./[A-Z]*"
>   ] 1 local
> 
> to cover everything else? Done.
> 

Yes, they are case sensitive.   If you have only a few numbers of capital 
letters,  they
make perfect candidates for that Misc data set.  You really DO need to have 
that,  in case you
dump a file there later that doesn’t fit any of the “include”  rules you’ve 
remembered to use.

Also,  a tar backup fails  (for me)  if it has NO contents.  So you need to 
save a few things,
like the numbers or capitals letters,  that really do already exist — so that 
the Misc set
isn’t empty.

Deb Baddorf

Re: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Gene Heskett]

On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:

> On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> > First a snip/paste of my 3 new del's as I try to split a big one up:
> > line entry
> > 28 coyote /home/gene/PublicA/ Publicag {
> > 29  comp-coyote-tar
> > 30  include "./[a-g]*"
> > 31  exclude "./[h-z]*"
> > 32  } 1 local
> > 33
>
> Chris already got the syntax error.
>
> I'll just note you do not need both the include
> and the exclude lines.  The "include" says these
> are the only things to backup.
>
> If "comp-coyote-tar" has any common excludes (like
> temp files or ???) the exclude above would replace
> them.  If you want to retain the excludes, you may
> want to make them "exclude append" to add to any
> default exclude.
>
> What if you create a "Gene" or a "123go" or a ".save"
> file or directory under PublicA?  Your 3 DLEs would
> not back them up.  I usually add a "catchall" DLE.
>
> In your case it might be:
> > 28 coyote PublicMisc /home/gene/PublicA/ {
> > 29  comp-coyote-tar
> > 31  exclude "./[a-z]*"
> > 32  } 1 local
>
> Jon

Probably a good idea now that  you mention it Jon, there are some files 
that start with numbers.

Are the alpha's case sensitive? 

Meaning should I make one for include "./[0-9]*" "./[A-Z]*" perhaps?
Something like:

coyote PublicA09AZ /home/gene/PublicA {
comp-coyote-tar
include "./[0-9]*" "./[A-Z]*"
] 1 local

to cover everything else? Done.

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: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Gene Heskett]

On Wednesday 14 November 2018 13:13:30 Chris Nighswonger wrote:

> On Wed, Nov 14, 2018 at 1:10 PM Gene Heskett  
wrote:
> > First a snip/paste of my 3 new del's as I try to split a big one up:
> > line entry
> > 28 coyote /home/gene/PublicA/ Publicag {
> > 29  comp-coyote-tar
> > 30  include "./[a-g]*"
> > 31  exclude "./[h-z]*"
> > 32  } 1 local
> >
> > Try this variation:
>
> coyote Publicag /home/gene/PublicA/ {
>  comp-coyote-tar
>  include "./[a-g]*"
>  exclude "./[h-z]*"
>  } 1 local
>
> Syntax is:
>
> hostname diskname diskdevice {
> }
Makeing the 2nd argument the "/path/to" to the directory to be backed up 
on the "hostname".
> Kind regards,
> Chris

Worked like I knew what I was doing!
amcheck is tickled pink too:

NOTE: info dir '/usr/local/var/amanda/Daily/curinfo/coyote/PublicAnz' 
does not exist
  it will be created on the next run
NOTE: index dir '/usr/local/var/amanda/Daily/index/coyote/PublicAnz' does 
not exist
  it will be created on the next run
NOTE: info dir '/usr/local/var/amanda/Daily/curinfo/coyote/PublicAhm' 
does not exist
  it will be created on the next run
NOTE: index dir '/usr/local/var/amanda/Daily/index/coyote/PublicAhm' does 
not exist
  it will be created on the next run
NOTE: info dir '/usr/local/var/amanda/Daily/curinfo/coyote/PublicAag' 
does not exist
  it will be created on the next run
NOTE: index dir '/usr/local/var/amanda/Daily/index/coyote/PublicAag' does 
not exist
  it will be created on the next run
Who knows, might have to adjust the split, but its got to be an 
improvement.

Here all this time I thought the path was arg(1). The man page for 
disklist is a bit obtuse in its use of wordings.

Particularly so for someone who was taught phonics in his official 
schooling. A subject that is IMNSHO sorely lacking in any us funded 
school for around 75 ears now. That lack is evident in todays 
journalistic output. Their students can't read the front page of the 
weekly fishwrap, not to mention the Daily from the next city up the 
pike. They could learn a lot from a comic strip featuring a duck called 
Mallard Philmore, who loves to point out the sometimes very different 
meanings of very similar words.

Thanks Chris.

I've also noticed the BETSOL guy is quiet, so I'd mention fork again and 
take up a collection to pay JLM at least a part-time wage.  Think 
TANSTAAFL folks.  Change the license just enough to bring in copyright 
and donate a dollar per active entry in our disklists a year. Even on 
SS, I can find that much. As some of you may know, I've worked for an 
MBA, and as a sheriffs deputy was escorting him and a bankers box with 
his personal stuff out of the building for cookong the books, I told him 
to make sure the doorknob didn't hit him in the ass on his way out. He 
was basically a salesman, and didn't have a clue about running a tv 
station's AND its legal responsibilities, which as the Chief Operator I 
was designated as, were my responsibilities. Tried to fire me because I 
stopped a payola scam, not once but twice. We didn't exactly geehaw 
after the owner told him "not no, but hell no", to both.

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: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Jon LaBadie]

On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> 
> First a snip/paste of my 3 new del's as I try to split a big one up:
> line entry
> 28 coyote /home/gene/PublicA/ Publicag {
> 29comp-coyote-tar
> 30include "./[a-g]*"
> 31exclude "./[h-z]*"
> 32} 1 local
> 33

Chris already got the syntax error.

I'll just note you do not need both the include
and the exclude lines.  The "include" says these
are the only things to backup.

If "comp-coyote-tar" has any common excludes (like
temp files or ???) the exclude above would replace
them.  If you want to retain the excludes, you may
want to make them "exclude append" to add to any
default exclude.

What if you create a "Gene" or a "123go" or a ".save"
file or directory under PublicA?  Your 3 DLEs would
not back them up.  I usually add a "catchall" DLE.
In your case it might be:


> 28 coyote PublicMisc /home/gene/PublicA/ {
> 29comp-coyote-tar
> 31exclude "./[a-z]*"
> 32} 1 local

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

Re: Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Chris Nighswonger]

On Wed, Nov 14, 2018 at 1:10 PM Gene Heskett  wrote:

>
> First a snip/paste of my 3 new del's as I try to split a big one up:
> line entry
> 28 coyote /home/gene/PublicA/ Publicag {
> 29  comp-coyote-tar
> 30  include "./[a-g]*"
> 31  exclude "./[h-z]*"
> 32  } 1 local
>
> Try this variation:

coyote Publicag /home/gene/PublicA/ {
 comp-coyote-tar
 include "./[a-g]*"
 exclude "./[h-z]*"
 } 1 local

Syntax is:

hostname diskname diskdevice {
}

Kind regards,
Chris

Now I'm confuzzled about disklist entry's for "./[a-g]*" types

[Gene Heskett]

First a snip/paste of my 3 new del's as I try to split a big one up:
line entry
28 coyote /home/gene/PublicA/ Publicag {
29  comp-coyote-tar
30  include "./[a-g]*"
31  exclude "./[h-z]*"
32  } 1 local
33  
34 coyote /home/gene/PublicA/ Publichm {
35  comp-coyote-tar
36  exclude "./[a-g]*"
37  include "./[h-m]*"
38  exclude "./[n-z]*"
39  } 1 local
40
41 coyote /home/gene/PublicA/ Publicnz {
42  comp-coyote-tar
43  exclude "./[a-m]*"
44  include "./[n-z]*"
45  } 1 local
46

Then the amcheck output:
amanda@coyote:/usr/local/etc/amanda/Daily$ /usr/local/sbin/amcheck Daily
"/usr/local/etc/amanda/Daily/disklist", line 34: duplicate disk record, 
previous on line 28
"/usr/local/etc/amanda/Daily/disklist", line 34: read of custom dumptype 
failed
ERROR: errors processing config file

And the line that did do PublicA
#coyote /home/gene/PublicA  comp-coyote-tar 1   local

What am I doing wrong?

Thanks all.

-- 
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: Configuration confusion

[Cuttler, Brian R (HEALTH)]

Tape custody – means what, retention policy or storage of the tape when not in 
the drive/juke?

Amanda is not an archiver in the sense that the tapes are cycled on a regular 
basis. You are able to tape a tape out of rotation and replace it, or create a 
unique tape label and perform level 0 backups to it and then mark it as 
no-reuse in the tapelist, but the primary function is not long term archiving, 
though the tools exist to do that very well.

You can use the same tape pool for all three Amanda configs, but they will need 
to have a common tapelist file. But if you are doing that then you are 
selecting a single set of standards for your data-at-rest security, in which 
case there is little reason to maintain 3 different configs.

Each Amanda config will look to level nightly data, but you will have nights 
with relatively little and nights with relatively large data volume swings, er 
think wave interference from physics. You eliminate a lot of that by combining 
disklists into a single configuration.

Amanda will backup a new DLE at level 0 the first time it sees it. If you are 
worried about running long you will want to phase in the DLEs across several 
evenings. You may want to add the largest on Friday night, assuming that no one 
cares how late Amanda runs into Saturday. You will want to avoid adding 
multiple large DLEs on a single night, add a large and a small each night until 
they are all added.

You may want to think about your dumpcycle, 1 week, 2 weeks? Depends on your 
tapecycle (number of tapes in the pool) as well as your business requirements. 
You want multiple level 0 dumps of each DLE in the pool, you want the level 0 
dumps to be relatively frequent as it simplifies the restore process should you 
need to run it (you remember the text book procedure for restoring TAR/DUMP 
backups).

From: owner-amanda-us...@amanda.org  On Behalf 
Of Cuttler, Brian R (HEALTH)
Sent: Wednesday, November 14, 2018 11:44 AM
To: Chris Miller ; amanda-users 
Subject: RE: Configuration confusion


ATTENTION: This email came from an external source. Do not open attachments or 
click on links from unknown senders or unexpected emails.

You can run amanda multiple times per night, and each config can specify a 
different, MUST specify a different set of tape labels, different tape pools. 
But I don’t believe you can run multiple amanda servers concurrently.

Could you run your tapes with the highest security level so that DLEs can 
intermix on the output tape?

I believe that selection of encryption data-in-motion (vs on tape data-at-rest) 
can be configured per DLE, if not then certainly by host.

From: owner-amanda-us...@amanda.org 
mailto:owner-amanda-us...@amanda.org>> On Behalf 
Of Chris Miller
Sent: Wednesday, November 14, 2018 11:33 AM
To: amanda-users mailto:amanda-users@amanda.org>>
Subject: Configuration confusion


ATTENTION: This email came from an external source. Do not open attachments or 
click on links from unknown senders or unexpected emails.

Hi Folks,

I now have three working configs, meaning that my test configuration can backup 
three clients. I still can't tell what is happening, but that is a topic for a 
different thread. There is not much difference among the configs; in fact the 
only difference is the src (contents of "disklist") and the dst ("tapedev").

So, I have three clients, but the way I have configured AMANDA, I am running 
three copies of AMANDA, none of which knows what any other is doing. They will 
quite probably schedule level 0 backups on the same run, meaning I lose the 
smoothing benefit of the scheduler, which wants to try to make the nightly 
backup task approximately equal in terms of storage and network bandwidth 
consumption. However, I recognize that I'm asking a single copy of AMANDA to do 
multiple backups each night, and this might not be something AMANDA was 
designed to do. I don't know, being relatively inexperienced.

The config specifies the src and dst of the backup where src is a set of DLEs 
and dst is single tapedev. I think I want a single config that recognizes 
multiple (src to dst) mappings, and AMANDA can make backup level decisions 
knowing the full scope of the problem for that cycle. Given that I have fewer 
clients than backup-cycles, I can space my level 0 backups so that I never do 
more than one on any given night. I can fear that AMANDA will schedule everyone 
for level 0 and backups are still proceeding the next day! That would be 
disruptive and embarrassing.

I think what I'm asking is if I can backup a set of DLEs to a single tapedev, 
and have a single copy of AMANDA run multiple backups each night? I can't mix 
clients on the backup media, since each has different security and custody 
requirements, and I think I'd like AMANDA to be aware of the complete set of 
tasks for any given night without coming into conflict with AMANDA 
doppelgangers, unless I'm inventing problems that don't 

RE: Configuration confusion

[Cuttler, Brian R (HEALTH)]

You can run amanda multiple times per night, and each config can specify a 
different, MUST specify a different set of tape labels, different tape pools. 
But I don’t believe you can run multiple amanda servers concurrently.

Could you run your tapes with the highest security level so that DLEs can 
intermix on the output tape?

I believe that selection of encryption data-in-motion (vs on tape data-at-rest) 
can be configured per DLE, if not then certainly by host.

From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Miller
Sent: Wednesday, November 14, 2018 11:33 AM
To: amanda-users 
Subject: Configuration confusion


ATTENTION: This email came from an external source. Do not open attachments or 
click on links from unknown senders or unexpected emails.

Hi Folks,

I now have three working configs, meaning that my test configuration can backup 
three clients. I still can't tell what is happening, but that is a topic for a 
different thread. There is not much difference among the configs; in fact the 
only difference is the src (contents of "disklist") and the dst ("tapedev").

So, I have three clients, but the way I have configured AMANDA, I am running 
three copies of AMANDA, none of which knows what any other is doing. They will 
quite probably schedule level 0 backups on the same run, meaning I lose the 
smoothing benefit of the scheduler, which wants to try to make the nightly 
backup task approximately equal in terms of storage and network bandwidth 
consumption. However, I recognize that I'm asking a single copy of AMANDA to do 
multiple backups each night, and this might not be something AMANDA was 
designed to do. I don't know, being relatively inexperienced.

The config specifies the src and dst of the backup where src is a set of DLEs 
and dst is single tapedev. I think I want a single config that recognizes 
multiple (src to dst) mappings, and AMANDA can make backup level decisions 
knowing the full scope of the problem for that cycle. Given that I have fewer 
clients than backup-cycles, I can space my level 0 backups so that I never do 
more than one on any given night. I can fear that AMANDA will schedule everyone 
for level 0 and backups are still proceeding the next day! That would be 
disruptive and embarrassing.

I think what I'm asking is if I can backup a set of DLEs to a single tapedev, 
and have a single copy of AMANDA run multiple backups each night? I can't mix 
clients on the backup media, since each has different security and custody 
requirements, and I think I'd like AMANDA to be aware of the complete set of 
tasks for any given night without coming into conflict with AMANDA 
doppelgangers, unless I'm inventing problems that don't exist and there is no 
problem running multiple copies of AMANDA.

I may be looking to solve a non-problem, meaning that running multiple copies 
of AMANDA each night is not a problem and hearing, "That is not a problem." 
from those who know would be comforting.

Thanks for the help,
--
Chris.

V:916.974.0424
F:916.974.0428

Re: Monitor and Manage

[Gene Heskett]

On Wednesday 14 November 2018 10:44:09 Chris Miller wrote:

> Hi Folks,
>
> I now have three working configs, meaning that I can backup three
> clients. There is not much difference among the configs, but that is a
> topic for a different thread. My question is how I manage what AMANDA
> is doing?
>
> So, let's suppose I fire up all three amdumps at once:
>
Don't do that, instead wrap them in a bash script that will run all of 
them sequentially. And run the script with the backuo users crontab if 
you want it automatic, which IMO it should be.

>
> * How do I know if I'm getting level 0 or higher?
> * How do I know the backups are running and have not silently
> failed? * How do I know when they complete?
> * How do I know what has been accomplished?
> * :
>
> These are all the sort of questions that might be answered by some
> sort of dashboard, but I haven't heard of any such thing, nor do I
> expect to hear of any such thing, but I am also equally sure that all
> the answers exist. I just don't know where.
>
> In short, how do I monitor and mange AMANDA?
>
> Thanks for the help,



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: Monitor and Manage

[Jean-Francois Malouin]

* Chris Miller  [20181114 10:45]:
> Hi Folks, 
> 
> I now have three working configs, meaning that I can backup three clients. 
> There is not much difference among the configs, but that is a topic for a 
> different thread. My question is how I manage what AMANDA is doing? 

I do not understand this statement...but let's keep going anyway...

> So, let's suppose I fire up all three amdumps at once: 
> 
> 
> * How do I know if I'm getting level 0 or higher? 

Disregarding the 'all three amdumps at once' comment, the command 'amstatus 
'
will tell you what amanda is currently doing if it's running, or the last time 
it ran.
You can also specify the amdump log file to use with '--file '.
'man amstatus' will tell you all the details.

> * How do I know the backups are running and have not silently failed? 

Define the variable 'malto' in amanda.conf file to a valid email address.  If
you have an healthy mail setup, amanda will send you a report (man amreport)
after amdump or amflush finishes running, as by default 'send-amreport-on' is
'on' by default.

> * How do I know when they complete? 
> * How do I know what has been accomplished? 

man amstatus, man amreport  will help you.

cheers,
jf


> * : 
> 
> These are all the sort of questions that might be answered by some sort of 
> dashboard, but I haven't heard of any such thing, nor do I expect to hear of 
> any such thing, but I am also equally sure that all the answers exist. I just 
> don't know where. 
> 
> In short, how do I monitor and mange AMANDA? 
> 
> Thanks for the help, 
> -- 
> Chris. 
> 
> V:916.974.0424 
> F:916.974.0428 

Configuration confusion

[Chris Miller]

Hi Folks, 

I now have three working configs, meaning that my test configuration can backup 
three clients. I still can't tell what is happening, but that is a topic for a 
different thread. There is not much difference among the configs; in fact the 
only difference is the src (contents of "disklist") and the dst ("tapedev"). 

So, I have three clients, but the way I have configured AMANDA, I am running 
three copies of AMANDA, none of which knows what any other is doing. They will 
quite probably schedule level 0 backups on the same run, meaning I lose the 
smoothing benefit of the scheduler, which wants to try to make the nightly 
backup task approximately equal in terms of storage and network bandwidth 
consumption. However, I recognize that I'm asking a single copy of AMANDA to do 
multiple backups each night, and this might not be something AMANDA was 
designed to do. I don't know, being relatively inexperienced. 

The config specifies the src and dst of the backup where src is a set of DLEs 
and dst is single tapedev. I think I want a single config that recognizes 
multiple (src to dst) mappings, and AMANDA can make backup level decisions 
knowing the full scope of the problem for that cycle. Given that I have fewer 
clients than backup-cycles, I can space my level 0 backups so that I never do 
more than one on any given night. I can fear that AMANDA will schedule everyone 
for level 0 and backups are still proceeding the next day! That would be 
disruptive and embarrassing. 

I think what I'm asking is if I can backup a set of DLEs to a single tapedev, 
and have a single copy of AMANDA run multiple backups each night? I can't mix 
clients on the backup media, since each has different security and custody 
requirements, and I think I'd like AMANDA to be aware of the complete set of 
tasks for any given night without coming into conflict with AMANDA 
doppelgangers, unless I'm inventing problems that don't exist and there is no 
problem running multiple copies of AMANDA. 

I may be looking to solve a non-problem, meaning that running multiple copies 
of AMANDA each night is not a problem and hearing, "That is not a problem." 
from those who know would be comforting. 

Thanks for the help, 
-- 
Chris. 

V:916.974.0424 
F:916.974.0428 

Re: Monitor and Manage

[Austin S. Hemmelgarn]

On 2018-11-14 10:44, Chris Miller wrote:

Hi Folks,

I now have three working configs, meaning that I can backup three 
clients. There is not much difference among the configs, but that is a 
topic for a different thread. My question is how I manage what AMANDA is 
doing?


So, let's suppose I fire up all three amdumps at once:

  * How do I know if I'm getting level 0 or higher?
  * How do I know the backups are running and have not silently failed?
  * How do I know when they complete?
  * How do I know what has been accomplished?
  * :

These are all the sort of questions that might be answered by some sort 
of dashboard, but I haven't heard of any such thing, nor do I expect to 
hear of any such thing, but I am also equally sure that all the answers 
exist. I just don't know where.


In short, how do I monitor and mange AMANDA?
Well, for generic monitoring, make sure the system can deliver email and 
you have the aliases set up appropriately, and then configure Amanda to 
email you a report when the dump completes.


The reports themselves are actually rather thorough, going over both 
aggregate timing and performance information as well as the useful 
generic stuff like knowing what dump level everything ran at and what 
tapes got used.


You can get similar details for the last dump (or the current one if one 
is in-progress) using the `amstatus` command, which will also show 
progress info for individual DLE's if there is a dump running currently.


For more in-depth management, take a look at the `amadmin` and `amtape` 
commands, they both provide useful functionality for general management 
that doesn't involve actually running the backups, including:


* Forcing a level 0 or level 1 dump for any or all of the DLE's for the 
next run.  Don't get in the habit of doing this regularly, overriding 
the planner will usually not get you good results.
* Forcing Amanda to bump to a new dump level for a given DLE.  Again, 
don't do this regularly.
* Querying when the next level 0 dump is due for a given DLE.  This 
gives you an upper limit on when the DLE will get a level 0 dump 
assuming you stick to the schedule you told Amanda about.
* Querying details about all currently stored backups, including dates, 
location, and dump status.

* Querying the state of all the tapes/vtapes Amanda is managing.

RE: Monitor and Manage

[Cuttler, Brian R (HEALTH)]

Chris,

How many work areas? How many tape drives?

I have one config per amanda service platform, I have several amanda server 
platforms, each backing up a unique and non-overlapping set of clients.

Are you creating multiple amanda configs and running them from a single amanda 
server?

You can do that, if they have non-overlapping clients, or you have structured 
them in a way that will backup level 0 from one config and never level 0 from 
the other, but that defeats the entire purpose of the amanda scheduler.

Also I’d be very much surprised if you could successfully run multiple configs 
concurrently from a single server, you “might” be able to if you were able to 
assure unique sockets for each instance of the server, but I wouldn’t recommend 
such a setup.
Oh, in the case of concurrent runs you want to make strictly certain that 
clients are unique to config, an amanda client can only reply to a single 
master, you can’t have multiple concurrent clients on the server end.

Brian


Brian Cuttler
Network and System Administrator, ITG - Information Technology Group
Wadsworth Center, NYS Department of Health
Biggs Lab, Empire State Plaza, Albany, NY 12201
(518) 486-1697 | brian.cutt...@health.ny.gov



From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Miller
Sent: Wednesday, November 14, 2018 10:44 AM
To: amanda-users 
Subject: Monitor and Manage


ATTENTION: This email came from an external source. Do not open attachments or 
click on links from unknown senders or unexpected emails.

Hi Folks,

I now have three working configs, meaning that I can backup three clients. 
There is not much difference among the configs, but that is a topic for a 
different thread. My question is how I manage what AMANDA is doing?

So, let's suppose I fire up all three amdumps at once:

  *   How do I know if I'm getting level 0 or higher?
  *   How do I know the backups are running and have not silently failed?
  *   How do I know when they complete?
  *   How do I know what has been accomplished?
  *   :
These are all the sort of questions that might be answered by some sort of 
dashboard, but I haven't heard of any such thing, nor do I expect to hear of 
any such thing, but I am also equally sure that all the answers exist. I just 
don't know where.

In short, how do I monitor and mange AMANDA?

Thanks for the help,
--
Chris.

V:916.974.0424
F:916.974.0428

Monitor and Manage

[Chris Miller]

Hi Folks, 

I now have three working configs, meaning that I can backup three clients. 
There is not much difference among the configs, but that is a topic for a 
different thread. My question is how I manage what AMANDA is doing? 

So, let's suppose I fire up all three amdumps at once: 


* How do I know if I'm getting level 0 or higher? 
* How do I know the backups are running and have not silently failed? 
* How do I know when they complete? 
* How do I know what has been accomplished? 
* : 

These are all the sort of questions that might be answered by some sort of 
dashboard, but I haven't heard of any such thing, nor do I expect to hear of 
any such thing, but I am also equally sure that all the answers exist. I just 
don't know where. 

In short, how do I monitor and mange AMANDA? 

Thanks for the help, 
-- 
Chris. 

V:916.974.0424 
F:916.974.0428