Re: Can AMANDA be configured "per client"?

[Stefan G. Weichinger]

Am 09.11.18 um 06:19 schrieb Nathan Stratton Treadway:

> So, you were following the the instructions found in the "Using the new
> chg-disk:' section of the How_To:Set_Up_Virtual_Tapes wiki page that
> Stefan mentioned earlier in this thread, right?
>
> https://wiki.zmanda.com/index.php/How_To:Set_Up_Virtual_Tapes#Using_the_new_chg-disk:
> 
> As he mentioned that page has been around for a long time, but I've just
> edited the "new chg-disk" section

great. I wasn't aware that anyone still has write access there ;-)

tried to reset my password, failed with smtp error (the wiki can't send
email anymore, office365 login fails ...)

@Ashwin and/or BETSOL: please provide and point us at a working project
wiki/platform.

Re: sharing scripts

[Stefan G. Weichinger]

Am 08.11.18 um 21:01 schrieb Gene Heskett:
> On Thursday 08 November 2018 12:50:46 J Chapman Flack wrote:
> 
>> On 11/8/18 12:27 PM, Gene Heskett wrote:
>>> I certainly don't have any objections, and I wasn't aware there were
>>> anywhere near that many choices.  Can you PM me a list?
>>
>> In this instance, PM stands for "public message" ... they're all
>> listed under Insights / Forks on the zmanda/amanda GitHub page:
>>
>> https://github.com/zmanda/amanda/network/members
>>
>> -Chap
> 
> Never been there before, and thats quite a list.
> Bookmarked and thanks.

These are forks only in terms of git/github-lingua. Any user there can
fork the zmanda/amanda-repo ... it doesn't mean at all that every member
of that list does meaningful work on amanda ...

Re: Can AMANDA be configured "per client"?

[Olivier]

> In your case, though (i.e. with a fixed set of always-available slot
> directories), it certainly makes sense to set up an obvious 1-1 mapping
> between labels and slots, so that you don't have to think about or go
> hunting to figure out which vtape holds a particular label.  Amanda
> won't care about that (it will always look on the vtape and check the
> label found there before doing anything else), but it'll make your life
> slightly easier on those situations where you need to go look at the raw
> dump files or whatever.

Although it seems a good policy to map a one to one slot and label, in
the long run, it may not be so.

For example, I have retired some old disks and replaced them by new
ones. The new disks would endup with the same slot numbers as the disks
they replace. But I have created new labels and marked the previous
labels as "noreuse".

That way, I still have the data on the old disks, and Amanda still keeps
a track of what is in those old labels and I could remount the disk and
access the files if needed.

(BTW, I am using an homemade changer, that splits the virtual tape across
multiple physical disks; I came to that solution many years ago when
vtape could only use one disk/directory.) 

Best regards,

Olivier

Re: Can AMANDA be configured "per client"?

[Nathan Stratton Treadway]

On Thu, Nov 08, 2018 at 11:23:44 -0800, Chris Miller wrote:

> So, now I have a couple of "clean-up" questions to conclude this
> thread: vtape labels: Are these just an artifact of the tape heritage,
> meaning, How is the label any more restrictive/protective than the
> path to and filename of the vtape? It's not like you can inadvertently
> mount the wrong directory, is it?Well, actually, in the case of my NAS
> configuration, I guess that is possible, but unlikely except in the
> case of some sort of NAS failure and recovery. Is there a discussion
> somewhere describing how these are used and what sort of failures they
> can prevent in the vtape world?

As Jon mentioned, there are actually many different ways to set up
vtapes, expecially once you start including external USB drives or other
removable media in your mix of backup destinations.  The existence of
table labels allows Amanda to keep track of all the parts, and make sure
it's writing to the place it thinks it should be (and, therefore, to be
certain that it is *over*-writing the dumps it intended to overwrite).

In any case, table labels are such an important part of Amanda's whole
structure that there's no way to run it without them -- tape labels are
used both in all sorts of interaction with the user but also for
Amanda's internal record keeping, etc.  After a short while I think you
will see how interacting based on the tape label name is actually a lot
clearer than using a directory-path name or something along those
lines...

In your case, though (i.e. with a fixed set of always-available slot
directories), it certainly makes sense to set up an obvious 1-1 mapping
between labels and slots, so that you don't have to think about or go
hunting to figure out which vtape holds a particular label.  Amanda
won't care about that (it will always look on the vtape and check the
label found there before doing anything else), but it'll make your life
slightly easier on those situations where you need to go look at the raw
dump files or whatever.

(For that reason, I don't use a "number 0" in my tape label sequences,
but start my tape numbering with 1 to match the "slotN" directory
numbering.  But you can just as easily use tapes 0-through-(N-1) to go
with slots 1-through-N, or whatever. )


> And back to my original question about "per-clent configuration", I
> recognize that I will effectively be running N copies of AMANDA, and
> none of them will be aware of the others. I think this means that I
> have defeated the scheduler. I don't want to do that. It occurs to me
> that AMANDA does not know what any other copies are doing, which means
> that they could ALL schedule level 0 on the same night! I think I'd
> like to change my design from per-client configs in separate
> directories, to per-client qualified definitions in one amanda.conf. I
> see artifacts in various examples that lead me to believe that this
> can be done, and is probably preferable to my current scheme, because
> I then would have only one copy of AMANDA running and there can be a
> more sensible schedule. I'm most interested -- in fact, I am probably
> only interested -- that each client be able to direct backup storage
> to a location specific to that client.

Well, if in fact you are trying to dump each client to a compmletely
separate destination, then I don't think it matters whether you use
separate Amanda runs for each client, as far as the scheduling goes.

(Usually one of the points of the scheduling is to mix-and-match dump
levels from all the different clients so that when they are all combined
they fit together on that night's tape.  If you are sending each client
to a separate destination, that doesn't apply -- I think it would be
just as likely to end up scheduling all level 0s in the combined run as
separate, since the size of the dumps would be calculated separately for
each client.)

But certainly there are advantages to having just one instance running,
so it makese sense for you to at least try both setups and see which one
works better for you.  (This is exspecially true since you are running
v3.5, which has much better support for this sort of thing than has
historically been true..)

I haven't tried to do this sort of client-based separation of
backup destinations, so I can't give you examples... but a few things to
look at to help point you in the correct direction:

  1) you will need to set up multiple chg-disk: changers, each pointing
 to a client-specific path on your NAS.

  2) for each DLE in the disklist you would set a 'tag' to indicate
 which client that DLE applies to.  (Probably the easiest way to do
 that would be to create a separate dumptype for each client and
 use those dumptypes directly in the disklist.)

  3) Finally, you will need to set up a separate storage for each
 client, each referencing the tpchanger configured in 1) to write to
 the backup location for that client.  Set the 'tapepool "$r"'
 option on 

Re: Can AMANDA be configured "per client"?

[Nathan Stratton Treadway]

On Thu, Nov 08, 2018 at 10:28:06 -0800, Chris Miller wrote:
> Hi Nathan, 
> 
> > A little later I will look for a reference to documentation on this, but
> > in short: I believe the issue is that you are mixing the *name of the
> > subdirectory* and the *amanda label of on the vtape*.
>
> It may look that way, but that is probably not what is happening.
> "Mail.TCLC.org" is a component of the vtape path. "mail.tclc.org" is a
> component of the config path. "Mail.TCLC.org.%%", a reflection of the
> vtape path, is what I think I am trying to use as a label. I have no
> idea of the significance of the label, but it occurs to me that
> matching the tape label to its path is a good idea.

I actually wasn't trying to say anything one way or another about your
config names or vtape labels, but rather was noticing that your amlabel
slot option was not a number, and that you were trying to give
"label-like" names to the vtape subdirectories.

 
> > On the other hand, the subdirectories the chg-disk: changer uses to hold
> > its vtapes are not really designed for direct human interaction... and
> > they have a built-in naming pattern you can't change.

> O.K., now we're getting somewhere, and explains why I couldn't find
> how to change the names of the "slots". It can't be done! I didn't
> expect that, but hearing it confirms my experience and probably
> completely solves my problem. Thanks very much for this tid-bit. I
> interpreted lack of explanation of how to change the names of the
> slots to mean that it is either trivially simple or simply has been
> ignored in the docs. Since it can't be done, the HowTo should probably
> alerts fools like me to that fact. "Not documenting" is not the same
> as "documenting don't". (-:

So, you were following the the instructions found in the "Using the new
chg-disk:' section of the How_To:Set_Up_Virtual_Tapes wiki page that
Stefan mentioned earlier in this thread, right?
   
https://wiki.zmanda.com/index.php/How_To:Set_Up_Virtual_Tapes#Using_the_new_chg-disk:

As he mentioned that page has been around for a long time, but I've just
edited the "new chg-disk" section to spell out the rules for the
slot-directory names and also hopefully clarify the discussion a little
bit and mention some related features available in newer version of
Amanda.

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: Breaking DLEs up

[Nathan Stratton Treadway]

On Thu, Nov 08, 2018 at 21:24:04 -0500, Chris Nighswonger wrote:
> Dump program is GNUTAR. I can switch to amgtar.
> 

Amgtar is more flexible to use (and easier to maintain, should
development on Amanda ever resume), so while you're rolling this out
it's probably worth switching.  (And it should let you work around this
permission problem, too.)

> root@fileserver:~# stat -c "%a %n" /netdrives
> 755 /netdrives
> root@fileserver:~# stat -c "%a %n" /netdrives/CAMPUS
> 2771 /netdrives/CAMPUS
> 
> Which explains the problem if I understand correctly. 771 would
> prohibit the amanda user from reading everything below CAMPUS.

Right (assuming that the Amanda user is not in the group which owns the
CAMPUS directory).

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: Breaking DLEs up

[Chris Nighswonger]

On Thu, Nov 8, 2018 at 5:35 PM Nathan Stratton Treadway
 wrote:
>
>
> I haven't quite followed this whole thread, either, but have you taken a
> look at
>   http://wiki.zmanda.com/index.php/How_To:Split_DLEs_With_Exclude_Lists
> ? It may help explain some of the nuances in how things work.
>

That information is very similar to the information in the example
disklist file included with Amanda.

> As Stefan mentioned, it would be helpeful to know what amanda version
> you are using, and which dump program.  If your client supports it,
> using APPLICATION amgtar (rather than GNUTAR) is definitely a good idea.

This client is running 3.3.1.

The server is running 3.3.6.

Dump program is GNUTAR. I can switch to amgtar.

>
> But, especially if you are using GNUTAR, an important thing to keep in
> mind is that the exclude list is processed by passing the whole list
> using an --exclude option to GNU tar, which then processes that list as
> it does the dump -- while in contrast the "include" options are
> processed ahead of time by Amanda to build a list of directories to pass
> on the command line (thus making up tar's list of "what should I be
> backing up"?).  The tricky thing is that the tar process runs with root
> priviledge, so it can see any directory out there... but the "include"
> work is done by an unprivileged process and so the directory *above* the
> include pattern must be readable by the amanda user...
>

That explains a lot.

> So, what are the permissions on the /netdrives/CAMPUS/ directory itself?

root@fileserver:~# stat -c "%a %n" /netdrives
755 /netdrives
root@fileserver:~# stat -c "%a %n" /netdrives/CAMPUS
2771 /netdrives/CAMPUS

Which explains the problem if I understand correctly. 771 would
prohibit the amanda user from reading everything below CAMPUS.

Chris

Re: Breaking DLEs up

[Nathan Stratton Treadway]

On Thu, Nov 08, 2018 at 15:21:00 -0500, Chris Nighswonger wrote:
> On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) <
> brian.cutt...@health.ny.gov> wrote:
> 
> >
> >
> > Your syntax
> >
> >
> >
> > fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
> >   comp-tar
> >   include "./[a-f]*"
> >   estimate server
> > }
> >
[...]
> 
> Well, this fixes my problem, though why I do not know.
> 
> fileserver CAMPUS_a-f /netdrives/CAMPUS {
>   comp-tar
>   exclude file "./[g-z]*"
>   estimate server
> } 1
> 
> It seems a bit of work compared to the include directive. I tried "include
> file" to no avail.

I haven't quite followed this whole thread, either, but have you taken a
look at 
  http://wiki.zmanda.com/index.php/How_To:Split_DLEs_With_Exclude_Lists
? It may help explain some of the nuances in how things work.

As Stefan mentioned, it would be helpeful to know what amanda version
you are using, and which dump program.  If your client supports it,
using APPLICATION amgtar (rather than GNUTAR) is definitely a good idea.  

But, especially if you are using GNUTAR, an important thing to keep in
mind is that the exclude list is processed by passing the whole list
using an --exclude option to GNU tar, which then processes that list as
it does the dump -- while in contrast the "include" options are
processed ahead of time by Amanda to build a list of directories to pass
on the command line (thus making up tar's list of "what should I be
backing up"?).  The tricky thing is that the tar process runs with root
priviledge, so it can see any directory out there... but the "include"
work is done by an unprivileged process and so the directory *above* the
include pattern must be readable by the amanda user...

So, what are the permissions on the /netdrives/CAMPUS/ directory itself?

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: Breaking DLEs up

[Stefan G. Weichinger]

Am 08.11.18 um 22:55 schrieb Stefan G. Weichinger:

Am 08.11.18 um 22:52 schrieb Stefan G. Weichinger:


manpage says:

exclude [ list | file ][[optional][append][ string ]+]
Default: file. Exclude is the opposite of include and specifies files 
that will be excluded from the backup. The format of the exclude 
expressions depends on the application, and some applications do not 
support excluding files at all.


...
although I always skip that default "file" option (and recommend to 
test that)


another thought (maybe you mentioned it, it's late here and I haven't 
scanned the whole thread): do you use GNUTAR as dump program (parameter 
"program" in global dumptype or so)?


If you didn't specify the default is DUMP and not GNUTAR (and the 
include parameter might do completely other things)



Some more examples for you ;-)
these work for years afaik:


garten projekte_1 /home/Samba/Daten/Projekte {
comp-cl-highprio
include "./[a-gA-G]*"
}

garten projekte_2 /home/Samba/Daten/Projekte {
comp-cl-highprio
include "./[h-nH-N]*"
}

garten projekte_3 /home/Samba/Daten/Projekte {
comp-cl-highprio
include "./[o-pO-P]*"
}

Re: Breaking DLEs up

[Stefan G. Weichinger]

Am 08.11.18 um 22:52 schrieb Stefan G. Weichinger:


manpage says:

exclude [ list | file ][[optional][append][ string ]+]
Default: file. Exclude is the opposite of include and specifies files 
that will be excluded from the backup. The format of the exclude 
expressions depends on the application, and some applications do not 
support excluding files at all.


...
although I always skip that default "file" option (and recommend to test 
that)


another thought (maybe you mentioned it, it's late here and I haven't 
scanned the whole thread): do you use GNUTAR as dump program (parameter 
"program" in global dumptype or so)?


If you didn't specify the default is DUMP and not GNUTAR (and the 
include parameter might do completely other things)

Re: Breaking DLEs up

[Stefan G. Weichinger]

Am 08.11.18 um 22:49 schrieb Stefan G. Weichinger:

Am 08.11.18 um 22:06 schrieb Debra S Baddorf:

Ah, good!   What does “file”  do in your include line?


exactly

include file ...
means "read include regex(es) from that file

you want

include "./[a-g]*"

and not "include file"

see manpage



I might have been to quick to reply, sorry.

manpage says:

exclude [ list | file ][[optional][append][ string ]+]
Default: file. Exclude is the opposite of include and specifies files 
that will be excluded from the backup. The format of the exclude 
expressions depends on the application, and some applications do not 
support excluding files at all.


...
although I always skip that default "file" option (and recommend to test 
that)

Re: Breaking DLEs up

[Stefan G. Weichinger]

Am 08.11.18 um 22:06 schrieb Debra S Baddorf:

Ah, good!   What does “file”  do in your include line?


exactly

include file ...
means "read include regex(es) from that file

you want

include "./[a-g]*"

and not "include file"

see manpage

Re: Breaking DLEs up

[Debra S Baddorf]

Ah, good!   What does “file”  do in your include line?
Deb



> On Nov 8, 2018, at 2:54 PM, Jon LaBadie  wrote:
> 
> On Thu, Nov 08, 2018 at 08:43:49PM +, Debra S Baddorf wrote:
>> Yeah, I do use includes,  but I only do a single letter at a time
>>   include "./a*”
>> 
>> Perhaps the problem is with the syntax of doing more than one letter.
>> I only do   [a-f]   on my excludes.   Weird!
>> 
>> Deb Baddorf
> 
> I have a working entry that matches the OP.
> 
>include file "./201[7-9]*"
> 
> Jon
>> 
>>> On Nov 8, 2018, at 2:33 PM, Cuttler, Brian R (HEALTH) 
>>>  wrote:
>>> 
>>> 
>>> Interesting, not sure.
>>> 
>>> For part 2, I will say that it is far easier to exclude files from backup 
>>> than include them. You had done an excellent job of exclusion, you’ll 
>>> pardon the poor attempt at humor, it is getting late in the day.
>>> 
>>> 
>>> From: Chris Nighswonger  
>>> Sent: Thursday, November 8, 2018 3:21 PM
>>> To: Cuttler, Brian R (HEALTH) 
>>> Cc: amanda-users@amanda.org
>>> Subject: Re: Breaking DLEs up
>>> 
>>> ATTENTION: This email came from an external source. Do not open attachments 
>>> or click on links from unknown senders or unexpected emails.
>>> 
>>> On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) 
>>>  wrote:
>>> 
>>> Your syntax
>>> 
>>> fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
>>>  comp-tar
>>>  include "./[a-f]*"
>>>  estimate server
>>> }
>>> 
>>> my syntax
>>> 
>>> finsen  /export/home-A /export/home   {
>>>user-tar2
>>>include "./[a]*"
>>>}
>>> 
>>> finsen  /export/home-AZ /export/home   {
>>>user-tar2
>>>include "./[A-Z]*"
>>>}
>>> 
>>> 
>>> Well, this fixes my problem, though why I do not know.
>>> 
>>> fileserver CAMPUS_a-f /netdrives/CAMPUS {
>>>  comp-tar
>>>  exclude file "./[g-z]*"
>>>  estimate server
>>> } 1
>>> 
>>> It seems a bit of work compared to the include directive. I tried "include 
>>> file" to no avail.
>>> 
>>> I'll see how the backup runs tonight, but amcheck likes it.
>>> 
>>> Kind regards,
>>> Chris
 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)

Re: Breaking DLEs up

[Jon LaBadie]

On Thu, Nov 08, 2018 at 08:43:49PM +, Debra S Baddorf wrote:
> Yeah, I do use includes,  but I only do a single letter at a time
>include "./a*”
> 
> Perhaps the problem is with the syntax of doing more than one letter.
> I only do   [a-f]   on my excludes.   Weird!
> 
> Deb Baddorf

I have a working entry that matches the OP.

include file "./201[7-9]*"

Jon
> 
> > On Nov 8, 2018, at 2:33 PM, Cuttler, Brian R (HEALTH) 
> >  wrote:
> > 
> >  
> > Interesting, not sure.
> >  
> > For part 2, I will say that it is far easier to exclude files from backup 
> > than include them. You had done an excellent job of exclusion, you’ll 
> > pardon the poor attempt at humor, it is getting late in the day.
> >  
> >  
> > From: Chris Nighswonger  
> > Sent: Thursday, November 8, 2018 3:21 PM
> > To: Cuttler, Brian R (HEALTH) 
> > Cc: amanda-users@amanda.org
> > Subject: Re: Breaking DLEs up
> >  
> > ATTENTION: This email came from an external source. Do not open attachments 
> > or click on links from unknown senders or unexpected emails.
> > 
> > On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) 
> >  wrote:
> >  
> > Your syntax
> >  
> > fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
> >   comp-tar
> >   include "./[a-f]*"
> >   estimate server
> > }
> >  
> > my syntax
> >  
> > finsen  /export/home-A /export/home   {
> > user-tar2
> > include "./[a]*"
> > }
> >  
> > finsen  /export/home-AZ /export/home   {
> > user-tar2
> > include "./[A-Z]*"
> > }
> >  
> >  
> > Well, this fixes my problem, though why I do not know.
> >  
> > fileserver CAMPUS_a-f /netdrives/CAMPUS {
> >   comp-tar
> >   exclude file "./[g-z]*"
> >   estimate server
> > } 1
> >  
> > It seems a bit of work compared to the include directive. I tried "include 
> > file" to no avail.
> >  
> > I'll see how the backup runs tonight, but amcheck likes it.
> >  
> > Kind regards,
> > Chris
>>> 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)

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

My login directories are all lower case, but I did have one include "./[A-Z]*", 
it never found anything, which didn't bother me because there wasn't supposed 
to be anything to be found, now you make me wonder if it would have failed if I 
had in fact needed it.

Good the situation never come up.

-Original Message-
From: Debra S Baddorf  
Sent: Thursday, November 8, 2018 3:44 PM
To: Cuttler, Brian R (HEALTH) 
Cc: Debra S Baddorf ; Chris Nighswonger 
; amanda-users@amanda.org
Subject: Re: Breaking DLEs up

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


Yeah, I do use includes,  but I only do a single letter at a time
   include "./a*”

Perhaps the problem is with the syntax of doing more than one letter.
I only do   [a-f]   on my excludes.   Weird!

Deb Baddorf

> On Nov 8, 2018, at 2:33 PM, Cuttler, Brian R (HEALTH) 
>  wrote:
>
>
> Interesting, not sure.
>
> For part 2, I will say that it is far easier to exclude files from backup 
> than include them. You had done an excellent job of exclusion, you’ll pardon 
> the poor attempt at humor, it is getting late in the day.
>
>
> From: Chris Nighswonger 
> Sent: Thursday, November 8, 2018 3:21 PM
> To: Cuttler, Brian R (HEALTH) 
> Cc: amanda-users@amanda.org
> Subject: Re: Breaking DLEs up
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
> On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) 
>  wrote:
>
> Your syntax
>
> fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[a-f]*"
>   estimate server
> }
>
> my syntax
>
> finsen  /export/home-A /export/home   {
> user-tar2
> include "./[a]*"
> }
>
> finsen  /export/home-AZ /export/home   {
> user-tar2
> include "./[A-Z]*"
> }
>
>
> Well, this fixes my problem, though why I do not know.
>
> fileserver CAMPUS_a-f /netdrives/CAMPUS {
>   comp-tar
>   exclude file "./[g-z]*"
>   estimate server
> } 1
>
> It seems a bit of work compared to the include directive. I tried "include 
> file" to no avail.
>
> I'll see how the backup runs tonight, but amcheck likes it.
>
> Kind regards,
> Chris

Re: Breaking DLEs up

[Debra S Baddorf]

Yeah, I do use includes,  but I only do a single letter at a time
   include "./a*”

Perhaps the problem is with the syntax of doing more than one letter.
I only do   [a-f]   on my excludes.   Weird!

Deb Baddorf

> On Nov 8, 2018, at 2:33 PM, Cuttler, Brian R (HEALTH) 
>  wrote:
> 
>  
> Interesting, not sure.
>  
> For part 2, I will say that it is far easier to exclude files from backup 
> than include them. You had done an excellent job of exclusion, you’ll pardon 
> the poor attempt at humor, it is getting late in the day.
>  
>  
> From: Chris Nighswonger  
> Sent: Thursday, November 8, 2018 3:21 PM
> To: Cuttler, Brian R (HEALTH) 
> Cc: amanda-users@amanda.org
> Subject: Re: Breaking DLEs up
>  
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
> 
> On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) 
>  wrote:
>  
> Your syntax
>  
> fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[a-f]*"
>   estimate server
> }
>  
> my syntax
>  
> finsen  /export/home-A /export/home   {
> user-tar2
> include "./[a]*"
> }
>  
> finsen  /export/home-AZ /export/home   {
> user-tar2
> include "./[A-Z]*"
> }
>  
>  
> Well, this fixes my problem, though why I do not know.
>  
> fileserver CAMPUS_a-f /netdrives/CAMPUS {
>   comp-tar
>   exclude file "./[g-z]*"
>   estimate server
> } 1
>  
> It seems a bit of work compared to the include directive. I tried "include 
> file" to no avail.
>  
> I'll see how the backup runs tonight, but amcheck likes it.
>  
> Kind regards,
> Chris

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

Interesting, not sure.

For part 2, I will say that it is far easier to exclude files from backup than 
include them. You had done an excellent job of exclusion, you’ll pardon the 
poor attempt at humor, it is getting late in the day.


From: Chris Nighswonger 
Sent: Thursday, November 8, 2018 3:21 PM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: Breaking DLEs up


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

On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>> wrote:

Your syntax

fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
  comp-tar
  include "./[a-f]*"
  estimate server
}

my syntax

finsen  /export/home-A /export/home   {
user-tar2
include "./[a]*"
}

finsen  /export/home-AZ /export/home   {
user-tar2
include "./[A-Z]*"
}


Well, this fixes my problem, though why I do not know.

fileserver CAMPUS_a-f /netdrives/CAMPUS {
  comp-tar
  exclude file "./[g-z]*"
  estimate server
} 1

It seems a bit of work compared to the include directive. I tried "include 
file" to no avail.

I'll see how the backup runs tonight, but amcheck likes it.

Kind regards,
Chris

Re: Breaking DLEs up

[Chris Nighswonger]

On Thu, Nov 8, 2018 at 1:56 PM Cuttler, Brian R (HEALTH) <
brian.cutt...@health.ny.gov> wrote:

>
>
> Your syntax
>
>
>
> fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[a-f]*"
>   estimate server
> }
>
>
>
> my syntax
>
>
>
> finsen  /export/home-A /export/home   {
>
> user-tar2
>
> include "./[a]*"
>
> }
>
>
>
> finsen  /export/home-AZ /export/home   {
>
> user-tar2
>
> include "./[A-Z]*"
>
> }
>
>
>

Well, this fixes my problem, though why I do not know.

fileserver CAMPUS_a-f /netdrives/CAMPUS {
  comp-tar
  exclude file "./[g-z]*"
  estimate server
} 1

It seems a bit of work compared to the include directive. I tried "include
file" to no avail.

I'll see how the backup runs tonight, but amcheck likes it.

Kind regards,
Chris

Re: Can AMANDA be configured "per client"?

[Gene Heskett]

On Thursday 08 November 2018 14:23:44 Chris Miller wrote:

> Hi Folks,
>
> My thanks to the guys that helped me. You know who you are -- Austin,
> Gene, Stefan, Nathan.
>
> My problem with vtapes was that the name of the slots, "slot..." was
> not arbitrary, or at least not arbitrary on my part. I fixed that, and
> backups are happening as we speak. Beers all 'round. I now have a bit
> of breathing room, and I can review ALL the "HowTo"s, which is a
> pretty good place to start.
>
> So, now I have a couple of "clean-up" questions to conclude this
> thread: vtape labels: Are these just an artifact of the tape heritage,
> meaning, How is the label any more restrictive/protective than the
> path to and filename of the vtape? It's not like you can inadvertently
> mount the wrong directory, is it?Well, actually, in the case of my NAS
> configuration, I guess that is possible, but unlikely except in the
> case of some sort of NAS failure and recovery. Is there a discussion
> somewhere describing how these are used and what sort of failures they
> can prevent in the vtape world?
>
> And back to my original question about "per-clent configuration", I
> recognize that I will effectively be running N copies of AMANDA, and
> none of them will be aware of the others. I think this means that I
> have defeated the scheduler. I don't want to do that. It occurs to me
> that AMANDA does not know what any other copies are doing, which means
> that they could ALL schedule level 0 on the same night! I think I'd
> like to change my design from per-client configs in separate
> directories, to per-client qualified definitions in one amanda.conf. I
> see artifacts in various examples that lead me to believe that this
> can be done, and is probably preferable to my current scheme, because
> I then would have only one copy of AMANDA running and there can be a
> more sensible schedule. I'm most interested -- in fact, I am probably
> only interested -- that each client be able to direct backup storage
> to a location specific to that client.
>
> Can anybody show me an example of several per-client configs in a
> single amanda.conf?
>
> Thanks for the help,

IIRC the multiple spindle problem is addressed in "man disklist". What 
you don't want is 2 or more dumpers attacking the same spindle(drive in 
english). Doing a whole disk backup by different entries in the disklist 
is faster if the drive isn't taking seek beating between two or more 
dumpers If the target machine only has one drive, then the spindle value 
in the disklist is always one.


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: sharing scripts

[Gene Heskett]

On Thursday 08 November 2018 12:50:46 J Chapman Flack wrote:

> On 11/8/18 12:27 PM, Gene Heskett wrote:
> > I certainly don't have any objections, and I wasn't aware there were
> > anywhere near that many choices.  Can you PM me a list?
>
> In this instance, PM stands for "public message" ... they're all
> listed under Insights / Forks on the zmanda/amanda GitHub page:
>
> https://github.com/zmanda/amanda/network/members
>
> -Chap

Never been there before, and thats quite a list.
Bookmarked and thanks.

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: Breaking DLEs up

[Chris Nighswonger]

On Thu, Nov 8, 2018 at 2:57 PM Alan Hodgson 
wrote:

>
> I looked at your original post and it looked like it should work, and
> the logs show it mostly did work, it just didn't see anything to back
> up. I'd suspect permission problems or a bug in your version of tar
> maybe. The only thing the logs don't show are the contents of
> /tmp/amanda/sendbackup._netdrives_CAMPUS_sz.20181108052711.include,
> which presumable has the regex in it. You should be able to recreate
> that and test the tar command manually.
>
>
I finally looked in the right place and located the sendbackup...include
files: sendbackup._netdrives_CAMPUS_af.20181108052816.include, etc.

They are empty.

sendbackup...exclude files related to a completely different DLE on the
same server DO contain the correct exclude lists for that DLE.

That doesn't sound right.

Re: Can AMANDA be configured "per client"?

[Gene Heskett]

On Thursday 08 November 2018 12:40:37 Chris Miller wrote:

> Hi Gene,
>
> > From: "Gene Heskett" 
> > To: "amanda-users" 
> > Sent: Wednesday, November 7, 2018 12:16:36 PM
> > Subject: Re: Can AMANDA be configured "per client"?
> >
> > A few questions here:
> > How did you build amamda? [here, as the user amanda, always
> > configure driven by the same script shown here:]
> > ===
>
> I installed from RPM: amanda-backup_server-3.5.1-1.rhel7.x86_64.rpm
>
> A brief description:
>
> I have NAS storage available to AMANDA as /net/nas1/d0/Mail.TCLC.org.
> In an effort to generalize, this is symlinked as "dst" from the config
> directory, /etc/amanda/mail.tclc.org, vis:
>
> bash-4.2$ ls -al /etc/amanda/mail.tclc.org/
>
> lrwxrwxrwx. 1 root root 26 Nov 6 07:02 dst ->
> /net/nas1/d0/Mail.TCLC.org
>
>
> bash-4.2$ ls -l /net/nas1/d0/Mail.TCLC.org/
>
> -rwxr-xr-x. 1 amandabackup disk 1110 Nov 8 09:12 state
> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.00
>
> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.62
>
> When I run amlabel: amlabel mail.tclc.org Mail.TCLC.org.00 slot
> vtape.00
>
If there is nothing precious on that NAS now, take a look at the mkvtapes 
script in the GenesAmandaHelper I just made available on my web page. In 
my case the slots directories are the vtapes, and amanda manipulates the 
linkage of "data" to the slot to be used, as in "data" is a soft link to 
the slot-number it is going to use as a vtape for this run.

Grab the file from my site in the sig, out of the Genes-os9-stf link from 
the front page, look at the header will less which will show you how to 
unpack it. Position your shell/terminal at the root of your file system 
and run the line from the header, filling in the blanks between the < > 
with the filename. Then either unpack it which will create the directory 
if you've perms to do it, becomeing root is probably sufficient. Then do 
a chown amanda:disk on the directories contents, then step into the 
created directory and look at mkvtapes to see how I do it. Change the 
path to the NAS, and with a bit of luck it might work, but more than 
likely will need to chown the NAS to amanda:disk to give you permissions 
when su'd to amanda.

I actually have a user amanda, and I build amanda in that home directory 
using the script I posted here a couple or 3 days back. called gh.cf 
here. If you don't have a user amanda, check and see if backup will 
work, but since I build the amanda from source in the /home/amanda 
directory I have a real user amanda but no passwd set.

When working on this I do a sudo -i to get root, then su amanda to do any 
editing, otherwise you may accidentally give something to root, which is 
a no-no.

Adjust the number of vtapes in that script and figure on as many vtapes 
as can be fitted in the NAS at the size stated in your 
$config/amanda.conf. You should wind up with a Dailys/slot-(number) 
array, with "data" being a softlink to slot-00. At that point amanda can 
handle the rest of it.


> Reading label...
> Slot vtape.00 not found
> Slot vtape.00 not found
>
> I apparently do not understand the whole "vtape" thing at all... At a
> minimum, I don't see where the config declares my "slots" as having
> names "vtape.{00..62}"

vtape is essentially nothing but slanguage to indicate your "tape" is a 
directory on a hard drive.  It is not actually used by amanda. Amanda 
expects in my case to always write to $path/to/your/storage/Dailys/data. 
This gets manipulated by this entry in your $config/amanda.conf
TPCHANGER "chg-disk:/amandatapes/Dailys"
the pathname name to the right of the : is arbitrary, as long as the rest 
of the configurtion matches.

There's probably more, in which case yelp at me here.

> Thanks for the help,

NP, so far & thank you!

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: Can AMANDA be configured "per client"?

[Jon LaBadie]

On Thu, Nov 08, 2018 at 11:23:44AM -0800, Chris Miller wrote:
> Hi Folks, 
> 
> My thanks to the guys that helped me. You know who you are -- Austin, Gene, 
> Stefan, Nathan. 
> 
> My problem with vtapes was that the name of the slots, "slot..." was not 
> arbitrary, or at least not arbitrary on my part. I fixed that, and backups 
> are happening as we speak. Beers all 'round. I now have a bit of breathing 
> room, and I can review ALL the "HowTo"s, which is a pretty good place to 
> start. 
> 
> So, now I have a couple of "clean-up" questions to conclude this thread: 
> vtape labels: Are these just an artifact of the tape heritage, meaning, How 
> is the label any more restrictive/protective than the path to and filename of 
> the vtape? It's not like you can inadvertently mount the wrong directory, is 
> it?Well, actually, in the case of my NAS configuration, I guess that is 
> possible, but unlikely except in the case of some sort of NAS failure and 
> recovery. Is there a discussion somewhere describing how these are used and 
> what sort of failures they can prevent in the vtape world? 
> 

It is more restrictive/specific than a path to the vtape.
Some sites use portable drives and rotate them off-site.
So the same "slots" are used for many different vtapes.

My own setup has /amanda on the root filesystem.
Under /amanda are directories "Holding", "Storage", and
Slots.  A dedicated disk is mounted on "Holding".
Under Storage are six directories "D1" to "D6".  My six
dedicated vtape storage disks are mounted there.

Slots contains mostly symbolic links to the vtapes under
Storage.  230+ vtapes whose naming is DS1-### and matches
the numeric part of the Slot name.  I.e. slot28 is a
symbolic link to /Storage/D1/DS1-028.

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

Re: Breaking DLEs up

[Alan Hodgson]

On Thu, 2018-11-08 at 13:24 -0500, Chris Nighswonger wrote:
> No question is stupid. I learned that beating my head against the
> wall for long hours. :-)
> 
> /netdrives/CAMPUS/ is a path which contains users' network drives.
> The level below CAMPUS contains folders which follow the naming
> convention of the username of each account. ie. Chris Nighswonger
> would be cnighswonger and thus /netdrives/CAMPUS/cnighswonger/ would
> be my related network drive.
> 
> There are somewhat less than 100 user directories. Prior to this I
> have been backing them all up with a DLE which looks like this:
> 
> host "/netdrives/CAMPUS" {
>   comp-tar
>   estimate server
> }
> 
> This works fine with the caveat that it results in a huge level 0
> backup.
> 
> In the supplied disklist file example in Amanda's documentation
> (/usr/share/doc/amanda-server/examples/disklist), I discovered the
> DLE form I am currently attempting. According to the example this
> should limit each DLE to backing up subdirectories of
> /netdrives/CAMPUS/ based on the regexp supplied in the "include"
> directive.
> 
> It appears to me that something may have changed with the way Amanda
> handles this since that document was written.
> 
> As Stefan points out, Amanda seems to thing that there is "nothing"
> to be backed up. Furthermore, it appears that the log excerpts I
> posted also show that the regexp is not being applied but that Amanda
> is actually looking for specific subdirectories like
> /netdrives/CAMPUS/af and the like.
> 
> Maybe the DLE syntax is incorrect?

I looked at your original post and it looked like it should work, and
the logs show it mostly did work, it just didn't see anything to back
up. I'd suspect permission problems or a bug in your version of tar
maybe. The only thing the logs don't show are the contents of
/tmp/amanda/sendbackup._netdrives_CAMPUS_sz.20181108052711.include,
which presumable has the regex in it. You should be able to recreate
that and test the tar command manually.

For comparison, I use the following for one host and it works fine:

hyperion.example.com /home-A /home {
gentoo-ssh-encrypt-user-comp
include "./[aA0-9]*"
include append "./.amandastub"
} 1
hyperion.example.com /home-B /home {
gentoo-ssh-encrypt-user-comp
include "./[bB]*"
include append "./.amandastub"
} 1
hyperion.example.com /home-C /home {
gentoo-ssh-encrypt-user-comp
include "./[cC]*"
include append "./.amandastub"
} 1
... etc.

The 1's shouldn't matter, although you might want them to control
parallel backups. And my appends are just so the DLE always finds
something to backup even if I don't happen to have any directories
matching those names.

I'm using Amanda 3.5.1-r1, but those DLEs have been used for many
previous versions too.

Re: Breaking DLEs up

[Chris Nighswonger]

On Thu, Nov 8, 2018 at 2:34 PM Jon LaBadie  wrote:

> On Thu, Nov 08, 2018 at 01:24:46PM -0500, Chris Nighswonger wrote:
> > > Here is the relevant portion of my DLEs:
> > >
> > > fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
> > >   comp-tar
> > >   include "./[a-f]*"
> > >   estimate server
> > > }
>
> One difference I noticed.  Deb, Brian, and myself all use
> "disknames" that are not pathnames.  I've not heard of pathnanmes
> causing a problem, but you might consider changine /netdrives/CAMPUS/af
> to something like CAMPUSa-f.
>
>
You may be on to something there. I can easily conceive of Amanda not
discerning the difference given that the default behavior is to use the
diskname as the diskdevice. [1]

Kind regards,
Chris


[1] https://wiki.zmanda.com/man/disklist.5.html

Re: Breaking DLEs up

[Jon LaBadie]

On Thu, Nov 08, 2018 at 01:24:46PM -0500, Chris Nighswonger wrote:
> No question is stupid. I learned that beating my head against the wall for
> long hours. :-)
> 
[snip]
> >
> >
> > Here is the relevant portion of my DLEs:
> >
> > fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
> >   comp-tar
> >   include "./[a-f]*"
> >   estimate server
> > }

One difference I noticed.  Deb, Brian, and myself all use
"disknames" that are not pathnames.  I've not heard of pathnanmes
causing a problem, but you might consider changine /netdrives/CAMPUS/af
to something like CAMPUSa-f.

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

Re: Can AMANDA be configured "per client"?

[Chris Miller]

Hi Folks, 

My thanks to the guys that helped me. You know who you are -- Austin, Gene, 
Stefan, Nathan. 

My problem with vtapes was that the name of the slots, "slot..." was not 
arbitrary, or at least not arbitrary on my part. I fixed that, and backups are 
happening as we speak. Beers all 'round. I now have a bit of breathing room, 
and I can review ALL the "HowTo"s, which is a pretty good place to start. 

So, now I have a couple of "clean-up" questions to conclude this thread: vtape 
labels: Are these just an artifact of the tape heritage, meaning, How is the 
label any more restrictive/protective than the path to and filename of the 
vtape? It's not like you can inadvertently mount the wrong directory, is 
it?Well, actually, in the case of my NAS configuration, I guess that is 
possible, but unlikely except in the case of some sort of NAS failure and 
recovery. Is there a discussion somewhere describing how these are used and 
what sort of failures they can prevent in the vtape world? 

And back to my original question about "per-clent configuration", I recognize 
that I will effectively be running N copies of AMANDA, and none of them will be 
aware of the others. I think this means that I have defeated the scheduler. I 
don't want to do that. It occurs to me that AMANDA does not know what any other 
copies are doing, which means that they could ALL schedule level 0 on the same 
night! I think I'd like to change my design from per-client configs in separate 
directories, to per-client qualified definitions in one amanda.conf. I see 
artifacts in various examples that lead me to believe that this can be done, 
and is probably preferable to my current scheme, because I then would have only 
one copy of AMANDA running and there can be a more sensible schedule. I'm most 
interested -- in fact, I am probably only interested -- that each client be 
able to direct backup storage to a location specific to that client. 

Can anybody show me an example of several per-client configs in a single 
amanda.conf? 

Thanks for the help, 
-- 
Chris. 

V:916.974.0424 
F:916.974.0428 

Re: Breaking DLEs up

[Debra S Baddorf]

re:  what works
I use the following, and it works well.   I’m still on 3.3.9  and on RedHat 
variants,  fwiw.
define dumptype  alphaTara   {
dailyTarKRB5
include "./a*”
}

and IN my disk list,  these variants
to use the above defined dumptype:
heimdall.fnal.gov homea  /home  {
   alphaTara
   estimate server
   }

here’s one that is defined IN the disklist
mtamaster1.fnal.gov  17-Mod-rawTOP /data/mta/Run2017/ModularCavity/rawdata {
MTA-TarKRB5
exclude "./Agi80304B"
exclude append "./Lec625Zi"
exclude append "./Tek7104"
   # still includes  Agi7104A  and Tek7254   # since it must have SOME 
content
}


and one with RANGES,  so it more close matches your case:
heimdall.fnal.gov homeOther  /home  {
dailyTarKRB5
exclude "./[a-pr-tv-z]*"
exclude append "./ROOT-5.34*"
estimate server
}

Just some examples of working set lists.
Deb Baddorf
Fermilab



> On Nov 8, 2018, at 12:24 PM, Chris Nighswonger  
> wrote:
> 
> No question is stupid. I learned that beating my head against the wall for 
> long hours. :-)
> 
> /netdrives/CAMPUS/ is a path which contains users' network drives. The level 
> below CAMPUS contains folders which follow the naming convention of the 
> username of each account. ie. Chris Nighswonger would be cnighswonger and 
> thus /netdrives/CAMPUS/cnighswonger/ would be my related network drive.
> 
> There are somewhat less than 100 user directories. Prior to this I have been 
> backing them all up with a DLE which looks like this:
> 
> host "/netdrives/CAMPUS" {
>   comp-tar
>   estimate server
> }
> 
> This works fine with the caveat that it results in a huge level 0 backup.
> 
> In the supplied disklist file example in Amanda's documentation 
> (/usr/share/doc/amanda-server/examples/disklist), I discovered the DLE form I 
> am currently attempting. According to the example this should limit each DLE 
> to backing up subdirectories of /netdrives/CAMPUS/ based on the regexp 
> supplied in the "include" directive.
> 
> It appears to me that something may have changed with the way Amanda handles 
> this since that document was written.
> 
> As Stefan points out, Amanda seems to thing that there is "nothing" to be 
> backed up. Furthermore, it appears that the log excerpts I posted also show 
> that the regexp is not being applied but that Amanda is actually looking for 
> specific subdirectories like /netdrives/CAMPUS/af and the like.
> 
> Maybe the DLE syntax is incorrect?
> 
> On Thu, Nov 8, 2018 at 12:31 PM Cuttler, Brian R (HEALTH) 
>  wrote:
>  
> 
>  
> 
> Stupid question, host fileserver, directories  /netdrives/CAMPUS/s* to 
> /netdrives/CAMPUS/z* exist and have some files in them?
> 
>  
> 
> From: Chris Nighswonger  
> Sent: Thursday, November 8, 2018 12:11 PM
> To: Cuttler, Brian R (HEALTH) 
> Cc: amanda-users@amanda.org
> Subject: Re: Breaking DLEs up
> 
>  
> 
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
> 
> From the client:
> 
>  
> 
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195 
> euid 10195 version 3.3.1: start at Thu Nov  8 05:27:11 2018
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Version 3.3.1
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195 
> euid 10195 version 3.3.1: rename at Thu Nov  8 05:27:11 2018
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:   Parsed request as: 
> program `GNUTAR'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> disk `/netdrives/CAMPUS/sz'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> device `/netdrives/CAMPUS'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> level 0
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> since NODATE
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> options `'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> datapath `AMANDA'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: start: 
> host:/netdrives/CAMPUS/sz lev 0
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning "/bin/gzip 
> /bin/gzip --fast" in pipeline
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: pid 23694: 
> /bin/gzipThu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23694: 
> /bin/gzip --fast
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: doing level 0 dump as 
> listed-incremental to 
> '/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to include 
> for disk /netdrives/CAMPUS/sz
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning 
> "/usr/libexec/amanda/runtar runtar campus /bin/tar --create --file - 
> --directory /netdrives/CAMPUS --one-file-system --listed-incremental 
> 

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

Chris,

We seem to be doing the same thing. We are doing it for the same reason. I went 
a little more finely grained as I had about 1200 user accounts and some stored 
quite a bit of data in their home directories, vs the group samba share or data 
directories for projects (usually on the compute engine or cluster, rather than 
the home directory server). [Latest storage server came in the door with 250 
Tbytes of space]

Note that I have ‘a’ to ‘z’ and then the catch-all that never catches anything, 
but that is expected and fits in with Debra’s comments.

I always worry about the leading dot to anchor the path, but we did it the 
same. That is why I copied the two near each other, for easy comparison.

You can see the tar commands in the log files, what do you catch if you run the 
tar command manually?
Could it be a permissions problem for Amanda to read the user files?

Your syntax

fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
  comp-tar
  include "./[a-f]*"
  estimate server
}

my syntax

finsen  /export/home-A /export/home   {
user-tar2
include "./[a]*"
}

finsen  /export/home-AZ /export/home   {
user-tar2
include "./[A-Z]*"
}

I’ve removed all but the last email you wrote from this email, it was getting 
long for little or no gain.

From: Chris Nighswonger 
Sent: Thursday, November 8, 2018 1:25 PM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: Breaking DLEs up


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

No question is stupid. I learned that beating my head against the wall for long 
hours. :-)

/netdrives/CAMPUS/ is a path which contains users' network drives. The level 
below CAMPUS contains folders which follow the naming convention of the 
username of each account. ie. Chris Nighswonger would be cnighswonger and thus 
/netdrives/CAMPUS/cnighswonger/ would be my related network drive.

There are somewhat less than 100 user directories. Prior to this I have been 
backing them all up with a DLE which looks like this:

host "/netdrives/CAMPUS" {
  comp-tar
  estimate server
}

This works fine with the caveat that it results in a huge level 0 backup.

In the supplied disklist file example in Amanda's documentation 
(/usr/share/doc/amanda-server/examples/disklist), I discovered the DLE form I 
am currently attempting. According to the example this should limit each DLE to 
backing up subdirectories of /netdrives/CAMPUS/ based on the regexp supplied in 
the "include" directive.

It appears to me that something may have changed with the way Amanda handles 
this since that document was written.

As Stefan points out, Amanda seems to thing that there is "nothing" to be 
backed up. Furthermore, it appears that the log excerpts I posted also show 
that the regexp is not being applied but that Amanda is actually looking for 
specific subdirectories like /netdrives/CAMPUS/af and the like.

Maybe the DLE syntax is incorrect?

Re: Can AMANDA be configured "per client"?

[Debra S Baddorf]

I’m sure the “cannot change the name of slots”  stems from the original  (and 
still in use here, at least)
design for REAL tape drives.   Tape libraries have slots,  and you don’t get to 
change their names!

But I’ve starred and saved that email for when I eventually want vtapes too.  
Now I know not to try to rename them.  :D

Deb Baddorf
Fermilab

> On Nov 8, 2018, at 12:28 PM, Chris Miller  wrote:
> 
> Hi Nathan,
>  A little later I will look for a reference to documentation on this, but
>  in short: I believe the issue is that you are mixing the *name of the
>  subdirectory* and the *amanda label of on the vtape*.
> It may look that way, but that is probably not what is happening. 
> "Mail.TCLC.org" is a component of the vtape path. "mail.tclc.org" is a 
> component of the config path. "Mail.TCLC.org.%%", a reflection of the vtape 
> path, is what I think I am trying to use as a label. I have no idea of the 
> significance of the label, but it occurs to me that matching the tape label 
> to its path is a good idea.
> 
> 
> 
>  The Amanda label is what shows up in your interactition with Amanda, and
>  is actually a name stored in a little header file on your physical tape
>  or under the vtape subdirectory, to help Amanda keep track of which
>  tape/vtape is which.
>  
>  On the other hand, the subdirectories the chg-disk: changer uses to hold
>  its vtapes are not really designed for direct human interaction... and
>  they have a built-in naming pattern you can't change.
> O.K., now we're getting somewhere, and explains why I couldn't find how to 
> change the names of the "slots". It can't be done! I didn't expect that, but 
> hearing it confirms my experience and probably completely solves my problem. 
> Thanks very much for this tid-bit. I interpreted lack of explanation of how 
> to change the names of the slots to mean that it is either trivially simple 
> or simply has been ignored in the docs. Since it can't be done, the HowTo 
> should probably alerts fools like me to that fact. "Not documenting" is not 
> the same as "documenting don't". (-:
> 
> 
> 
>  So, your first step is going to be to rename your subdirectories to
>  "slot1", "slot2" ... "slot9", "slot10"...  (Note that you can _not_
>  zero-pad the first 9 slot numbers -- "ls -v" may come in handy.)
>  
>  After that, the amlabel command should work (or at least give a new
>  error message) ... but note that the "slot" argument takes a slot
>  number, rather than some sort of name.
>  
>  
> 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
> 
> 
> Thanks for the help,
> --
> Chris.
> 
> V:916.974.0424
> F:916.974.0428

Re: Can AMANDA be configured "per client"?

[Chris Miller]

Hi Nathan, 

> A little later I will look for a reference to documentation on this, but
> in short: I believe the issue is that you are mixing the *name of the
> subdirectory* and the *amanda label of on the vtape*.
It may look that way, but that is probably not what is happening. 
"Mail.TCLC.org" is a component of the vtape path. "mail.tclc.org" is a 
component of the config path. "Mail.TCLC.org.%%", a reflection of the vtape 
path, is what I think I am trying to use as a label. I have no idea of the 
significance of the label, but it occurs to me that matching the tape label to 
its path is a good idea. 

> The Amanda label is what shows up in your interactition with Amanda, and
> is actually a name stored in a little header file on your physical tape
> or under the vtape subdirectory, to help Amanda keep track of which
> tape/vtape is which.

> On the other hand, the subdirectories the chg-disk: changer uses to hold
> its vtapes are not really designed for direct human interaction... and
> they have a built-in naming pattern you can't change.
O.K., now we're getting somewhere, and explains why I couldn't find how to 
change the names of the "slots". It can't be done! I didn't expect that, but 
hearing it confirms my experience and probably completely solves my problem. 
Thanks very much for this tid-bit. I interpreted lack of explanation of how to 
change the names of the slots to mean that it is either trivially simple or 
simply has been ignored in the docs. Since it can't be done, the HowTo should 
probably alerts fools like me to that fact. "Not documenting" is not the same 
as "documenting don't". (-: 

> So, your first step is going to be to rename your subdirectories to
> "slot1", "slot2" ... "slot9", "slot10"... (Note that you can _not_
> zero-pad the first 9 slot numbers -- "ls -v" may come in handy.)

> After that, the amlabel command should work (or at least give a new
> error message) ... but note that the "slot" argument takes a slot
> number, rather than some sort of name.

> 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

Thanks for the help, 
-- 
Chris. 

V:916.974.0424 
F:916.974.0428 

Re: Breaking DLEs up

[Chris Nighswonger]

No question is stupid. I learned that beating my head against the wall for
long hours. :-)

/netdrives/CAMPUS/ is a path which contains users' network drives. The
level below CAMPUS contains folders which follow the naming convention of
the username of each account. ie. Chris Nighswonger would be cnighswonger
and thus /netdrives/CAMPUS/cnighswonger/ would be my related network drive.

There are somewhat less than 100 user directories. Prior to this I have
been backing them all up with a DLE which looks like this:

host "/netdrives/CAMPUS" {
  comp-tar
  estimate server
}

This works fine with the caveat that it results in a huge level 0 backup.

In the supplied disklist file example in Amanda's documentation
(/usr/share/doc/amanda-server/examples/disklist), I discovered the DLE form
I am currently attempting. According to the example this should limit each
DLE to backing up subdirectories of /netdrives/CAMPUS/ based on the regexp
supplied in the "include" directive.

It appears to me that something may have changed with the way Amanda
handles this since that document was written.

As Stefan points out, Amanda seems to thing that there is "nothing" to be
backed up. Furthermore, it appears that the log excerpts I posted also show
that the regexp is not being applied but that Amanda is actually looking
for specific subdirectories like /netdrives/CAMPUS/af and the like.

Maybe the DLE syntax is incorrect?

On Thu, Nov 8, 2018 at 12:31 PM Cuttler, Brian R (HEALTH) <
brian.cutt...@health.ny.gov> wrote:

>
>
>
>
> Stupid question, host fileserver, directories  /netdrives/CAMPUS/s* to
> /netdrives/CAMPUS/z* exist and have some files in them?
>
>
>
> *From:* Chris Nighswonger 
> *Sent:* Thursday, November 8, 2018 12:11 PM
> *To:* Cuttler, Brian R (HEALTH) 
> *Cc:* amanda-users@amanda.org
> *Subject:* Re: Breaking DLEs up
>
>
>
> *ATTENTION: This email came from an external source. Do not open
> attachments or click on links from unknown senders or unexpected emails.*
>
> From the client:
>
>
>
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195
> euid 10195 version 3.3.1: start at Thu Nov  8 05:27:11 2018
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Version 3.3.1
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195
> euid 10195 version 3.3.1: rename at Thu Nov  8 05:27:11 2018
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:   Parsed request as:
> program `GNUTAR'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
> disk `/netdrives/CAMPUS/sz'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
> device `/netdrives/CAMPUS'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
> level 0
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
> since NODATE
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
> options `'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
> datapath `AMANDA'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: start:
> host:/netdrives/CAMPUS/sz lev 0
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning "/bin/gzip
> /bin/gzip --fast" in pipeline
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: pid 23694:
> /bin/gzipThu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23694:
> /bin/gzip --fast
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: doing level 0 dump as
> listed-incremental to
> '/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to
> include for disk /netdrives/CAMPUS/sz
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning
> "/usr/libexec/amanda/runtar runtar campus /bin/tar --create --file -
> --directory /netdrives/CAMPUS --one-file-system --listed-incremental
> /var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new --sparse
> --ignore-failed-read --totals --files-from
> /tmp/amanda/sendbackup._netdrives_CAMPUS_sz.20181108052711.include" in
> pipeline
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar:
> /usr/libexec/amanda/runtar: pid 23696
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started backup
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started index
> creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'"
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  46:size(|):
> Total bytes written: 10240 (10KiB, 78MiB/s)
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Index created
> successfully
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Parsed backup messages
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 finish time
> Thu Nov  8 05:27:11 2018
>
>
>
> From the server:
>
>
>
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165691:Thu
> Nov  8 05:27:11 2018: thd-0x5579048e2400: dumper: getcmd: PORT-DUMP
> 03-00023 50013 1 host 9efefbff1f /netdrives/CAMPUS/sz
> /netdrives/CAMPUS 0 1970:1:1:0:0:0 GNUTAR "" "" "" "" bsdtcp AMANDA
> 127.0.0.1:50014 20 |"  bsdtcp\n

Re: sharing scripts

[J Chapman Flack]

On 11/8/18 12:27 PM, Gene Heskett wrote:

> I certainly don't have any objections, and I wasn't aware there were 
> anywhere near that many choices.  Can you PM me a list?

In this instance, PM stands for "public message" ... they're all
listed under Insights / Forks on the zmanda/amanda GitHub page:

https://github.com/zmanda/amanda/network/members

-Chap

Re: Can AMANDA be configured "per client"?

[Stefan G. Weichinger]

Am 08.11.18 um 18:52 schrieb Chris Miller:
> Hi Stefan,
> 
> 
> 
> *From: *"Stefan G. Weichinger" 
  >  /etc should contain only config

> In my case, I will have a set of config -- probably one for each client,
> so in a first pass at generalization, I symlinked the vtapes as "./dst"
> This may not turn out to be helpful, but I won't know until I have a few
> more hours under my belt.

I would avoid symlinks here ... at least until things work. Just my opinion.

> I distinguish locally attached devices (mounted under "/mnt") from
> network attached devices. I don't know it this is important, but if
> keeps me aware of what I am doing, since putting huge amount of traffic
> on the LAN has performance consequences to the users that copying huge
> amount of data around among locally attached devices does not. This is
> probably just a matter of style.

maybe. As you like, but I recommend following the recommendations until
things work and optionally THEN do your own style ;-)

>  chown these dirs (= mounted fs) to your amandauser to allow amanda
>  rw-access.
>  
>  and then define your chg-disk changer as in:
>  
>  tpchanger "chg-disk:/mnt/externaldisk1"
>  
>  proceed from there ...
> 
> I think I've done that. I suspect my problem is going to be more subtle.
> Like, for example, I named my "slots" "vtape.00 -- vtape.62", but I find
> nowhere to tell AMANDA that. This is, in fact, probably my whole
> problem, which should be trivial to eliminate, once I learn how to tell
> AMANDA of my choice.

See other end of thread and Nathan's posting.

Re: Can AMANDA be configured "per client"?

[Stefan G. Weichinger]

Am 08.11.18 um 19:11 schrieb Nathan Stratton Treadway:
> On Thu, Nov 08, 2018 at 09:40:37 -0800, Chris Miller wrote:
>> bash-4.2$ ls -l /net/nas1/d0/Mail.TCLC.org/ 
>> : 
>> -rwxr-xr-x. 1 amandabackup disk 1110 Nov 8 09:12 state 
>> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.00 
>> : 
>> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.62 
>>
>> When I run amlabel: amlabel mail.tclc.org Mail.TCLC.org.00 slot vtape.00 
>>
>> Reading label... 
>> Slot vtape.00 not found 
>> Slot vtape.00 not found 
>>
>> I apparently do not understand the whole "vtape" thing at all... At a
>> minimum, I don't see where the config declares my "slots" as having
>> names "vtape.{00..62}"
> 
> A little later I will look for a reference to documentation on this, but
> in short: I believe the issue is that you are mixing the *name of the
> subdirectory* and the *amanda label of on the vtape*.
> 
> The Amanda label is what shows up in your interactition with Amanda, and
> is actually a name stored in a little header file on your physical tape
> or under the vtape subdirectory, to help Amanda keep track of which
> tape/vtape is which.
> 
> On the other hand, the subdirectories the chg-disk: changer uses to hold
> its vtapes are not really designed for direct human interaction... and
> they have a built-in naming pattern you can't change.
> 
> So, your first step is going to be to rename your subdirectories to
> "slot1", "slot2" ... "slot9", "slot10"...  (Note that you can _not_
> zero-pad the first 9 slot numbers -- "ls -v" may come in handy.)
> 
> After that, the amlabel command should work (or at least give a new
> error message) ... but note that the "slot" argument takes a slot
> number, rather than some sort of name.

I agree.
Plus:

amtape  inventory

is your friend here, it should display your virtual tapes as soon as you
get things set up ...

example:

$ amtape vtape inventory

slot 0:1: label vtape-001-001 (vtape-005) [retention-no]
slot 0:2: label vtape-001-002 (vtape-005) [retention-no]
slot 0:3: label vtape-001-003 (vtape-005) [retention-no]
slot 0:4: label vtape-001-004 (vtape-005) [retention-no]
slot 0:5: label vtape-001-005 (vtape-005) [retention-tapes]

(forget my 0:1 slot, you should see 1, 2, 3 ...)

Re: Breaking DLEs up

[Debra S Baddorf]

Yeah,  I have found that with TAR,  there needs to be SOME content in the 
backup.

I would also suggest adding another set:   (add the words around this;  this is 
only the idea)
 CAMPUS-Other
   exclude “./a-z]*”
   #  and by default,  INCLUDE  everything besides a-z

This will catch anything that starts with a capital letter,  or a number.  Even 
if somebody adds
them later,  and you weren’t planning on them. But again, make sure there
is initially something *in* the set.  Perhaps a text file at the top level  
“00info”
which describes the way you are splitting the backup   “a-f”,  ….
Mostly just to have something there,  but it might also be useful to know.

Deb Baddorf
Fermilab

> On Nov 8, 2018, at 11:31 AM, Cuttler, Brian R (HEALTH) 
>  wrote:
> 
>  
>  
> Stupid question, host fileserver, directories  /netdrives/CAMPUS/s* to 
> /netdrives/CAMPUS/z* exist and have some files in them?
>  
> From: Chris Nighswonger  
> Sent: Thursday, November 8, 2018 12:11 PM
> To: Cuttler, Brian R (HEALTH) 
> Cc: amanda-users@amanda.org
> Subject: Re: Breaking DLEs up
>  
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
> 
> From the client:
>  
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195 
> euid 10195 version 3.3.1: start at Thu Nov  8 05:27:11 2018
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Version 3.3.1
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195 
> euid 10195 version 3.3.1: rename at Thu Nov  8 05:27:11 2018
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:   Parsed request as: 
> program `GNUTAR'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> disk `/netdrives/CAMPUS/sz'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> device `/netdrives/CAMPUS'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> level 0
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> since NODATE
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> options `'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
> datapath `AMANDA'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: start: 
> host:/netdrives/CAMPUS/sz lev 0
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning "/bin/gzip 
> /bin/gzip --fast" in pipeline
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: pid 23694: 
> /bin/gzipThu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23694: 
> /bin/gzip --fast
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: doing level 0 dump as 
> listed-incremental to 
> '/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new'
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to include 
> for disk /netdrives/CAMPUS/sz
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning 
> "/usr/libexec/amanda/runtar runtar campus /bin/tar --create --file - 
> --directory /netdrives/CAMPUS --one-file-system --listed-incremental 
> /var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new --sparse 
> --ignore-failed-read --totals --files-from 
> /tmp/amanda/sendbackup._netdrives_CAMPUS_sz.20181108052711.include" in 
> pipeline
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: 
> /usr/libexec/amanda/runtar: pid 23696
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started backup
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started index creator: 
> "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'"
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  46:size(|): Total 
> bytes written: 10240 (10KiB, 78MiB/s)
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Index created 
> successfully
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Parsed backup messages
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 finish time 
> Thu Nov  8 05:27:11 2018
>  
> From the server:
>  
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165691:Thu Nov  
> 8 05:27:11 2018: thd-0x5579048e2400: dumper: getcmd: PORT-DUMP 03-00023 50013 
> 1 host 9efefbff1f /netdrives/CAMPUS/sz /netdrives/CAMPUS 0 
> 1970:1:1:0:0:0 GNUTAR "" "" "" "" bsdtcp AMANDA 127.0.0.1:50014 20 |"  
> bsdtcp\n  FAST\n  YES\n  
> YES\n  AMANDA\n  \n
> ./[s-z]*\n  \n"
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165705:  
> /netdrives/CAMPUS/sz
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165706:  
> /netdrives/CAMPUS
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165740:  
> /netdrives/CAMPUS/sz
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165741:  
> /netdrives/CAMPUS
> /var/log/amanda/server/campus/dumper.20181108020002007.debug:165857:Thu Nov  
> 8 05:27:11 2018: thd-0x5579048e2400: dumper: Building type FILE header of 
> 

Re: Can AMANDA be configured "per client"?

[Nathan Stratton Treadway]

On Thu, Nov 08, 2018 at 09:40:37 -0800, Chris Miller wrote:
> bash-4.2$ ls -l /net/nas1/d0/Mail.TCLC.org/ 
> : 
> -rwxr-xr-x. 1 amandabackup disk 1110 Nov 8 09:12 state 
> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.00 
> : 
> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.62 
> 
> When I run amlabel: amlabel mail.tclc.org Mail.TCLC.org.00 slot vtape.00 
> 
> Reading label... 
> Slot vtape.00 not found 
> Slot vtape.00 not found 
> 
> I apparently do not understand the whole "vtape" thing at all... At a
> minimum, I don't see where the config declares my "slots" as having
> names "vtape.{00..62}"

A little later I will look for a reference to documentation on this, but
in short: I believe the issue is that you are mixing the *name of the
subdirectory* and the *amanda label of on the vtape*.

The Amanda label is what shows up in your interactition with Amanda, and
is actually a name stored in a little header file on your physical tape
or under the vtape subdirectory, to help Amanda keep track of which
tape/vtape is which.

On the other hand, the subdirectories the chg-disk: changer uses to hold
its vtapes are not really designed for direct human interaction... and
they have a built-in naming pattern you can't change.

So, your first step is going to be to rename your subdirectories to
"slot1", "slot2" ... "slot9", "slot10"...  (Note that you can _not_
zero-pad the first 9 slot numbers -- "ls -v" may come in handy.)

After that, the amlabel command should work (or at least give a new
error message) ... but note that the "slot" argument takes a slot
number, rather than some sort of name.


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: Can AMANDA be configured "per client"?

[Chris Miller]

Hi Stefan, 

> From: "Stefan G. Weichinger" 
> To: "Chris Miller" , "amanda-users" 
> Sent: Thursday, November 8, 2018 2:01:04 AM
> Subject: Re: Can AMANDA be configured "per client"?

> 
> You are free to do as you like but I recommend the following (my own way
> of doing it, more standard ...)

> /etc should contain only config

> Not vtapes, not data, not logs.
In my case, I will have a set of config -- probably one for each client, so in 
a first pass at generalization, I symlinked the vtapes as "./dst" This may not 
turn out to be helpful, but I won't know until I have a few more hours under my 
belt. 

> I prefer mounted filesystems under /mnt, and logs under /var/log (or in
> systemd journal ... another topic)

> I mount my NAS or external disks under /mnt, like in

> # /etc/fstab

> UUID=5a5a9927-995f-4f0f-98ff-d222561f84ff /mnt/externaldisk1 ext4
> relatime,noauto,user 0 1

I distinguish locally attached devices (mounted under "/mnt") from network 
attached devices. I don't know it this is important, but if keeps me aware of 
what I am doing, since putting huge amount of traffic on the LAN has 
performance consequences to the users that copying huge amount of data around 
among locally attached devices does not. This is probably just a matter of 
style. 

> chown these dirs (= mounted fs) to your amandauser to allow amanda
> rw-access.

> and then define your chg-disk changer as in:

> tpchanger "chg-disk:/mnt/externaldisk1"

> proceed from there ...
I think I've done that. I suspect my problem is going to be more subtle. Like, 
for example, I named my "slots" "vtape.00 -- vtape.62", but I find nowhere to 
tell AMANDA that. This is, in fact, probably my whole problem, which should be 
trivial to eliminate, once I learn how to tell AMANDA of my choice. 

> Did you read:

> https://wiki.zmanda.com/index.php/How_To:Set_Up_Virtual_Tapes#Configuration
Yes -- parts of it many times. To the extent that I understand it, I am 
following it. To the extent that things are not working, I have apparently 
violated its instructions. (-: 

Thanks for the help, 
-- 
Chris. 

V:916.974.0424 
F:916.974.0428 

Re: Can AMANDA be configured "per client"?

[Chris Miller]

Hi Gene, 

> From: "Gene Heskett" 
> To: "amanda-users" 
> Sent: Wednesday, November 7, 2018 12:16:36 PM
> Subject: Re: Can AMANDA be configured "per client"?

> A few questions here: 
> How did you build amamda? [here, as the user amanda, always configure 
> driven by the same script shown here:] 
> === 

I installed from RPM: amanda-backup_server-3.5.1-1.rhel7.x86_64.rpm 

A brief description: 

I have NAS storage available to AMANDA as /net/nas1/d0/Mail.TCLC.org. In an 
effort to generalize, this is symlinked as "dst" from the config directory, 
/etc/amanda/mail.tclc.org, vis: 

bash-4.2$ ls -al /etc/amanda/mail.tclc.org/ 
: 
lrwxrwxrwx. 1 root root 26 Nov 6 07:02 dst -> /net/nas1/d0/Mail.TCLC.org 
: 

bash-4.2$ ls -l /net/nas1/d0/Mail.TCLC.org/ 
: 
-rwxr-xr-x. 1 amandabackup disk 1110 Nov 8 09:12 state 
drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.00 
: 
drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.62 

When I run amlabel: amlabel mail.tclc.org Mail.TCLC.org.00 slot vtape.00 

Reading label... 
Slot vtape.00 not found 
Slot vtape.00 not found 

I apparently do not understand the whole "vtape" thing at all... At a minimum, 
I don't see where the config declares my "slots" as having names 
"vtape.{00..62}" 

Thanks for the help, 
-- 
Chris. 

V:916.974.0424 
F:916.974.0428 

Breaking DLEs up

[Stefan G. Weichinger]

Am 08.11.18 um 18:11 schrieb Chris Nighswonger:
> Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to
> include for disk /netdrives/CAMPUS/sz

"nothing found"

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

Stupid question, host fileserver, directories  /netdrives/CAMPUS/s* to 
/netdrives/CAMPUS/z* exist and have some files in them?

From: Chris Nighswonger 
Sent: Thursday, November 8, 2018 12:11 PM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: Breaking DLEs up


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

From the client:

Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195 euid 
10195 version 3.3.1: start at Thu Nov  8 05:27:11 2018
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Version 3.3.1
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195 euid 
10195 version 3.3.1: rename at Thu Nov  8 05:27:11 2018
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:   Parsed request as: 
program `GNUTAR'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  disk 
`/netdrives/CAMPUS/sz'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
device `/netdrives/CAMPUS'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  level 0
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  since 
NODATE
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
options `'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  
datapath `AMANDA'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: start: 
host:/netdrives/CAMPUS/sz lev 0
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning "/bin/gzip 
/bin/gzip --fast" in pipeline
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: pid 23694: 
/bin/gzipThu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23694: 
/bin/gzip --fast
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: doing level 0 dump as 
listed-incremental to 
'/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to include 
for disk /netdrives/CAMPUS/sz
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning 
"/usr/libexec/amanda/runtar runtar campus /bin/tar --create --file - 
--directory /netdrives/CAMPUS --one-file-system --listed-incremental 
/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new --sparse 
--ignore-failed-read --totals --files-from 
/tmp/amanda/sendbackup._netdrives_CAMPUS_sz.20181108052711.include" in pipeline
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: 
/usr/libexec/amanda/runtar: pid 23696
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started backup
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started index creator: 
"/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'"
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  46:size(|): Total 
bytes written: 10240 (10KiB, 78MiB/s)
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Index created successfully
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Parsed backup messages
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 finish time Thu 
Nov  8 05:27:11 2018

From the server:

/var/log/amanda/server/campus/dumper.20181108020002007.debug:165691:Thu Nov  8 
05:27:11 2018: thd-0x5579048e2400: dumper: getcmd: PORT-DUMP 03-00023 50013 1 
host 9efefbff1f /netdrives/CAMPUS/sz /netdrives/CAMPUS 0 
1970:1:1:0:0:0 GNUTAR "" "" "" "" bsdtcp AMANDA 
127.0.0.1:50014 20 |"  bsdtcp\n  
FAST\n  YES\n  YES\n  
AMANDA\n  \n./[s-z]*\n  
\n"
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165705:  
/netdrives/CAMPUS/sz
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165706:  
/netdrives/CAMPUS
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165740:  
/netdrives/CAMPUS/sz
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165741:  
/netdrives/CAMPUS
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165857:Thu Nov  8 
05:27:11 2018: thd-0x5579048e2400: dumper: Building type FILE header of 
32768-32768 bytes with name='host' disk='/netdrives/CAMPUS/sz' dumplevel=0 and 
blocksize=32768
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165944:Thu Nov  8 
05:27:11 2018: thd-0x5579048e2400: dumper: Building type FILE header of 
32768-32768 bytes with name='host' disk='/netdrives/CAMPUS/sz' dumplevel=0 and 
blocksize=32768

On Thu, Nov 8, 2018 at 12:00 PM Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>> wrote:
Client and server side?
/var/log/amanda/ ?


From: Chris Nighswonger 
mailto:cnighswon...@foundations.edu>>
Sent: Thursday, November 8, 2018 11:43 AM
To: Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>>
Cc: amanda-users@amanda.org
Subject: Re: Breaking DLEs up


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

Oddly enough, /tmp/amanda is empty.

On Thu, 

Re: sharing scripts (was: Can AMANDA be configured "per client"?)

[Gene Heskett]

On Thursday 08 November 2018 07:40:29 Stefan G. Weichinger wrote:

> Am 08.11.18 um 12:46 schrieb Gene Heskett:
> > On Thursday 08 November 2018 05:02:30 Stefan G. Weichinger wrote:
> >
> > For those who might be interested, the link on my web page that
> > leads to "Genes-os9-stf", now has a new readme for
> > GenesAmandaHelper, and a fresh backup of that whole thing as
> > 00029etcetc. Adjust to suit your system.  Its been in use here since
> > 2002. Currently working with amanda-3.5.1.
>
> A small suggestion here:
>
> instead of posting the script to the list over and over again (thanks
> for doing so! no offense intended!) we could think of collecting
> knowledge and tools like this and maybe provide stuff via a
> github-repo or so (as done by other oss-projects ...).
>
> Currently 57 forks of the zmanda/amanda repo exist, let's choose one
> and commit our tricks etc there.
>
> We can't wait for betsol afai see ...
>
> Feedback welcome here.
>
> (to be clear: I don't say "fork amanda" here, I just say "let's
> collect the spread hints and tips shared via the mailing list and
> build up some knowledge base there")
>
> -
>
> Additionally I think of adding and maintaining updated versions of the
> vtapes-howto there etc
>
> Stefan

I certainly don't have any objections, and I wasn't aware there were 
anywhere near that many choices.  Can you PM me a list?

FWIW, thats the first real update published since back in 2002, so I had 
to re-adjust my disklist and dumptypes to achieve an amanda version of a 
tarball to get that. I didn't figure the rest of the crowd needed to put 
up with a 500 meg backup of my configs and indices. Keeping ahead of tar 
was a bit of an exercise over the years, so this brings it up to at 
least the tar in the wheezy repo. And the tar in the pi's jessie repo 
seems to work. But a rock64 running stretch is crashed by it. Since the 
rock64 isn't doing anything for me yet, I haven't tried to snoop that 
out yet. A rock64 is a nice board, several times faster than the pi's, 
but support for anything like an rt kernel just isn't there, plus 
rebuilding the pi3b's spi driver to run on the rock64 is quite beyond 
my "pay grade". Without that its useless to me as I can't run cnc 
machinery with it.

Pick a repo, and move it to it, and of course let me know.  Oh, and what 
are the names of these other projects?

Copyright 2018 by Maurice E. Heskett

With BETSOL's attitude so far, I think my copyright notice will remain 
until such time as they actually want to be a "community" member. As 
long as they have thrown JLM under the buss, I for one am very unhappy. 
If they were going to put anyone on the payroll it should have been 
Jean-Louis.

-- 
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: Breaking DLEs up

[Chris Nighswonger]

>From the client:

Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195
euid 10195 version 3.3.1: start at Thu Nov  8 05:27:11 2018
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Version 3.3.1
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 ruid 10195
euid 10195 version 3.3.1: rename at Thu Nov  8 05:27:11 2018
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:   Parsed request as:
program `GNUTAR'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
disk `/netdrives/CAMPUS/sz'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
device `/netdrives/CAMPUS'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
level 0
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
since NODATE
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
options `'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:
datapath `AMANDA'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: start:
host:/netdrives/CAMPUS/sz lev 0
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning "/bin/gzip
/bin/gzip --fast" in pipeline
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar: pid 23694:
/bin/gzipThu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23694:
/bin/gzip --fast
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: doing level 0 dump as
listed-incremental to
'/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new'
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to
include for disk /netdrives/CAMPUS/sz
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Spawning
"/usr/libexec/amanda/runtar runtar campus /bin/tar --create --file -
--directory /netdrives/CAMPUS --one-file-system --listed-incremental
/var/lib/amanda/gnutar-lists/host_netdrives_CAMPUS_sz_0.new --sparse
--ignore-failed-read --totals --files-from
/tmp/amanda/sendbackup._netdrives_CAMPUS_sz.20181108052711.include" in
pipeline
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: gnutar:
/usr/libexec/amanda/runtar: pid 23696
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started backup
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Started index creator:
"/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'"
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup:  46:size(|): Total
bytes written: 10240 (10KiB, 78MiB/s)
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Index created
successfully
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: Parsed backup messages
Thu Nov  8 05:27:11 2018: thd-0x1c8f200: sendbackup: pid 23692 finish time
Thu Nov  8 05:27:11 2018

>From the server:

/var/log/amanda/server/campus/dumper.20181108020002007.debug:165691:Thu
Nov  8 05:27:11 2018: thd-0x5579048e2400: dumper: getcmd: PORT-DUMP
03-00023 50013 1 host 9efefbff1f /netdrives/CAMPUS/sz
/netdrives/CAMPUS 0 1970:1:1:0:0:0 GNUTAR "" "" "" "" bsdtcp AMANDA
127.0.0.1:50014 20 |"  bsdtcp\n  FAST\n
YES\n  YES\n
AMANDA\n  \n./[s-z]*\n
\n"
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165705:
/netdrives/CAMPUS/sz
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165706:
/netdrives/CAMPUS
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165740:
/netdrives/CAMPUS/sz
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165741:
/netdrives/CAMPUS
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165857:Thu
Nov  8 05:27:11 2018: thd-0x5579048e2400: dumper: Building type FILE header
of 32768-32768 bytes with name='host' disk='/netdrives/CAMPUS/sz'
dumplevel=0 and blocksize=32768
/var/log/amanda/server/campus/dumper.20181108020002007.debug:165944:Thu
Nov  8 05:27:11 2018: thd-0x5579048e2400: dumper: Building type FILE header
of 32768-32768 bytes with name='host' disk='/netdrives/CAMPUS/sz'
dumplevel=0 and blocksize=32768


On Thu, Nov 8, 2018 at 12:00 PM Cuttler, Brian R (HEALTH) <
brian.cutt...@health.ny.gov> wrote:

> Client and server side?
>
> /var/log/amanda/ ?
>
>
>
>
>
> *From:* Chris Nighswonger 
> *Sent:* Thursday, November 8, 2018 11:43 AM
> *To:* Cuttler, Brian R (HEALTH) 
> *Cc:* amanda-users@amanda.org
> *Subject:* Re: Breaking DLEs up
>
>
>
> *ATTENTION: This email came from an external source. Do not open
> attachments or click on links from unknown senders or unexpected emails.*
>
> Oddly enough, /tmp/amanda is empty.
>
>
>
> On Thu, Nov 8, 2018 at 11:33 AM Cuttler, Brian R (HEALTH) <
> brian.cutt...@health.ny.gov> wrote:
>
> I have been using a very similar setup for years, though I did not have
> any quotes in the first line of each DLE. I do NOT believe the quotes are
> an issue.
>
>
>
> What do the /tmp/amanda files show for these attempted dumps?
>
>
>
> *From:* owner-amanda-us...@amanda.org  *On
> Behalf Of *Chris Nighswonger
> *Sent:* Thursday, November 8, 2018 11:12 AM
> *To:* amanda-users@amanda.org
> *Subject:* Breaking DLEs up
>
>
>
> *ATTENTION: This email came from an external source. Do not open
> attachments or click on links from unknown senders or unexpected emails.*
>
> I attempted this 

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

What does amcheck say, no logs may mean authentication failure between client 
and server.

Try running the client on the client side, as the amanda user, from the command 
line. You should get a log, on occasion I’ve seen failures that proved to be a 
path issue to the binary in the inetd.conf (or equiv).

From: Cuttler, Brian R (HEALTH)
Sent: Thursday, November 8, 2018 12:00 PM
To: 'Chris Nighswonger' 
Cc: amanda-users@amanda.org
Subject: RE: Breaking DLEs up

Client and server side?
/var/log/amanda/ ?


From: Chris Nighswonger 
mailto:cnighswon...@foundations.edu>>
Sent: Thursday, November 8, 2018 11:43 AM
To: Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>>
Cc: amanda-users@amanda.org
Subject: Re: Breaking DLEs up


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

Oddly enough, /tmp/amanda is empty.

On Thu, Nov 8, 2018 at 11:33 AM Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>> wrote:
I have been using a very similar setup for years, though I did not have any 
quotes in the first line of each DLE. I do NOT believe the quotes are an issue.

What do the /tmp/amanda files show for these attempted dumps?

From: owner-amanda-us...@amanda.org 
mailto:owner-amanda-us...@amanda.org>> On Behalf 
Of Chris Nighswonger
Sent: Thursday, November 8, 2018 11:12 AM
To: amanda-users@amanda.org
Subject: Breaking DLEs up


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

I attempted this and it appears to not have worked. I'm not sure why.

Here is the relevant portion of my DLEs:

fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
  comp-tar
  include "./[a-f]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/gl" "/netdrives/CAMPUS" {
  comp-tar
  include "./[g-l]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/mr" "/netdrives/CAMPUS" {
  comp-tar
  include "./[m-r]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/sz" "/netdrives/CAMPUS" {
  comp-tar
  include "./[s-z]*"
  estimate server
}

Here are the corresponding lines from amreport for the last backup run:

fileserver:/netdrives/CAMPUS/af 
0 1k dump done (5:28:16), waiting for writing to tape
fileserver:/netdrives/CAMPUS/gl 
0 1k dump done (5:28:11), waiting for writing to tape
fileserver:/netdrives/CAMPUS/mr 
0 1k dump done (5:28:06), waiting for writing to tape
fileserver:/netdrives/CAMPUS/sz 
0 1k dump done (5:27:11), waiting for writing to tape

Kind regards,
Chris

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

Client and server side?
/var/log/amanda/ ?


From: Chris Nighswonger 
Sent: Thursday, November 8, 2018 11:43 AM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: Breaking DLEs up


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

Oddly enough, /tmp/amanda is empty.

On Thu, Nov 8, 2018 at 11:33 AM Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>> wrote:
I have been using a very similar setup for years, though I did not have any 
quotes in the first line of each DLE. I do NOT believe the quotes are an issue.

What do the /tmp/amanda files show for these attempted dumps?

From: owner-amanda-us...@amanda.org 
mailto:owner-amanda-us...@amanda.org>> On Behalf 
Of Chris Nighswonger
Sent: Thursday, November 8, 2018 11:12 AM
To: amanda-users@amanda.org
Subject: Breaking DLEs up


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

I attempted this and it appears to not have worked. I'm not sure why.

Here is the relevant portion of my DLEs:

fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
  comp-tar
  include "./[a-f]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/gl" "/netdrives/CAMPUS" {
  comp-tar
  include "./[g-l]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/mr" "/netdrives/CAMPUS" {
  comp-tar
  include "./[m-r]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/sz" "/netdrives/CAMPUS" {
  comp-tar
  include "./[s-z]*"
  estimate server
}

Here are the corresponding lines from amreport for the last backup run:

fileserver:/netdrives/CAMPUS/af 
0 1k dump done (5:28:16), waiting for writing to tape
fileserver:/netdrives/CAMPUS/gl 
0 1k dump done (5:28:11), waiting for writing to tape
fileserver:/netdrives/CAMPUS/mr 
0 1k dump done (5:28:06), waiting for writing to tape
fileserver:/netdrives/CAMPUS/sz 
0 1k dump done (5:27:11), waiting for writing to tape

Kind regards,
Chris

Re: Breaking DLEs up

[Chris Nighswonger]

Oddly enough, /tmp/amanda is empty.

On Thu, Nov 8, 2018 at 11:33 AM Cuttler, Brian R (HEALTH) <
brian.cutt...@health.ny.gov> wrote:

> I have been using a very similar setup for years, though I did not have
> any quotes in the first line of each DLE. I do NOT believe the quotes are
> an issue.
>
>
>
> What do the /tmp/amanda files show for these attempted dumps?
>
>
>
> *From:* owner-amanda-us...@amanda.org  *On
> Behalf Of *Chris Nighswonger
> *Sent:* Thursday, November 8, 2018 11:12 AM
> *To:* amanda-users@amanda.org
> *Subject:* Breaking DLEs up
>
>
>
> *ATTENTION: This email came from an external source. Do not open
> attachments or click on links from unknown senders or unexpected emails.*
>
> I attempted this and it appears to not have worked. I'm not sure why.
>
>
>
> Here is the relevant portion of my DLEs:
>
>
>
> fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[a-f]*"
>   estimate server
> }
> fileserver "/netdrives/CAMPUS/gl" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[g-l]*"
>   estimate server
> }
> fileserver "/netdrives/CAMPUS/mr" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[m-r]*"
>   estimate server
> }
> fileserver "/netdrives/CAMPUS/sz" "/netdrives/CAMPUS" {
>   comp-tar
>   include "./[s-z]*"
>   estimate server
> }
>
>
>
> Here are the corresponding lines from amreport for the last backup run:
>
>
>
> fileserver:/netdrives/CAMPUS/af
> 0 1k dump done (5:28:16), waiting for writing to tape
> fileserver:/netdrives/CAMPUS/gl
> 0 1k dump done (5:28:11), waiting for writing to tape
> fileserver:/netdrives/CAMPUS/mr
> 0 1k dump done (5:28:06), waiting for writing to tape
> fileserver:/netdrives/CAMPUS/sz
> 0 1k dump done (5:27:11), waiting for writing to tape
>
>
>
> Kind regards,
>
> Chris
>

RE: Breaking DLEs up

[Cuttler, Brian R (HEALTH)]

I have been using a very similar setup for years, though I did not have any 
quotes in the first line of each DLE. I do NOT believe the quotes are an issue.

What do the /tmp/amanda files show for these attempted dumps?

From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Nighswonger
Sent: Thursday, November 8, 2018 11:12 AM
To: amanda-users@amanda.org
Subject: Breaking DLEs up


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

I attempted this and it appears to not have worked. I'm not sure why.

Here is the relevant portion of my DLEs:

fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
  comp-tar
  include "./[a-f]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/gl" "/netdrives/CAMPUS" {
  comp-tar
  include "./[g-l]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/mr" "/netdrives/CAMPUS" {
  comp-tar
  include "./[m-r]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/sz" "/netdrives/CAMPUS" {
  comp-tar
  include "./[s-z]*"
  estimate server
}

Here are the corresponding lines from amreport for the last backup run:

fileserver:/netdrives/CAMPUS/af 
0 1k dump done (5:28:16), waiting for writing to tape
fileserver:/netdrives/CAMPUS/gl 
0 1k dump done (5:28:11), waiting for writing to tape
fileserver:/netdrives/CAMPUS/mr 
0 1k dump done (5:28:06), waiting for writing to tape
fileserver:/netdrives/CAMPUS/sz 
0 1k dump done (5:27:11), waiting for writing to tape

Kind regards,
Chris

Breaking DLEs up

[Chris Nighswonger]

I attempted this and it appears to not have worked. I'm not sure why.

Here is the relevant portion of my DLEs:

fileserver "/netdrives/CAMPUS/af" "/netdrives/CAMPUS" {
  comp-tar
  include "./[a-f]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/gl" "/netdrives/CAMPUS" {
  comp-tar
  include "./[g-l]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/mr" "/netdrives/CAMPUS" {
  comp-tar
  include "./[m-r]*"
  estimate server
}
fileserver "/netdrives/CAMPUS/sz" "/netdrives/CAMPUS" {
  comp-tar
  include "./[s-z]*"
  estimate server
}

Here are the corresponding lines from amreport for the last backup run:

fileserver:/netdrives/CAMPUS/af
0 1k dump done (5:28:16), waiting for writing to tape
fileserver:/netdrives/CAMPUS/gl
0 1k dump done (5:28:11), waiting for writing to tape
fileserver:/netdrives/CAMPUS/mr
0 1k dump done (5:28:06), waiting for writing to tape
fileserver:/netdrives/CAMPUS/sz
0 1k dump done (5:27:11), waiting for writing to tape

Kind regards,
Chris

Re: sharing scripts (was: Can AMANDA be configured "per client"?)

[Stefan G. Weichinger]

Am 08.11.18 um 13:56 schrieb Chris Nighswonger:
> Why not form a document git repo to house just Amanda docs?

Sure, why not ... I just want to avoid creating something noone
contributes to. Let's collect some opinions, decide and then collect
knowhow ;-)

Re: sharing scripts (was: Can AMANDA be configured "per client"?)

[Chris Nighswonger]

Why not form a document git repo to house just Amanda docs?

Kind regards,
Chris
On Thu, Nov 8, 2018 at 7:45 AM Stefan G. Weichinger  wrote:
>
> Am 08.11.18 um 12:46 schrieb Gene Heskett:
> > On Thursday 08 November 2018 05:02:30 Stefan G. Weichinger wrote:
> >
> > For those who might be interested, the link on my web page that leads
> > to "Genes-os9-stf", now has a new readme for GenesAmandaHelper, and a
> > fresh backup of that whole thing as 00029etcetc. Adjust to suit your
> > system.  Its been in use here since 2002. Currently working with
> > amanda-3.5.1.
>
>
> A small suggestion here:
>
> instead of posting the script to the list over and over again (thanks
> for doing so! no offense intended!) we could think of collecting
> knowledge and tools like this and maybe provide stuff via a github-repo
> or so (as done by other oss-projects ...).
>
> Currently 57 forks of the zmanda/amanda repo exist, let's choose one and
> commit our tricks etc there.
>
> We can't wait for betsol afai see ...
>
> Feedback welcome here.
>
> (to be clear: I don't say "fork amanda" here, I just say "let's collect
> the spread hints and tips shared via the mailing list and build up some
> knowledge base there")
>
> -
>
> Additionally I think of adding and maintaining updated versions of the
> vtapes-howto there etc
>
> Stefan

Re: sharing scripts (was: Can AMANDA be configured "per client"?)

[Stefan G. Weichinger]

Am 08.11.18 um 12:46 schrieb Gene Heskett:
> On Thursday 08 November 2018 05:02:30 Stefan G. Weichinger wrote:
> 
> For those who might be interested, the link on my web page that leads 
> to "Genes-os9-stf", now has a new readme for GenesAmandaHelper, and a 
> fresh backup of that whole thing as 00029etcetc. Adjust to suit your 
> system.  Its been in use here since 2002. Currently working with 
> amanda-3.5.1.


A small suggestion here:

instead of posting the script to the list over and over again (thanks
for doing so! no offense intended!) we could think of collecting
knowledge and tools like this and maybe provide stuff via a github-repo
or so (as done by other oss-projects ...).

Currently 57 forks of the zmanda/amanda repo exist, let's choose one and
commit our tricks etc there.

We can't wait for betsol afai see ...

Feedback welcome here.

(to be clear: I don't say "fork amanda" here, I just say "let's collect
the spread hints and tips shared via the mailing list and build up some
knowledge base there")

-

Additionally I think of adding and maintaining updated versions of the
vtapes-howto there etc

Stefan

Can AMANDA be configured "per client"?

[Stefan G. Weichinger]

Am 07.11.18 um 18:25 schrieb Chris Miller:
> Hi Austin,
> 
> Thanks very much. Your comments have been very helpful, and I appreciate
> the obviously considerable amount of time you spent to help me. I'm much
> farther along on this project as a result. I have no idea how I'm going
> to verify that everything is working the way I expect it to work, but I
> guess I will become much more familiar with how to manage AMANDA as I
> spend more time. AmCheck tells me that I only have one problem. I think
> AMANDA can't find the vtapes, so I need to learn much more about vtapes.
> This is an area that I understand theoretically, but I'm having trouble
> turning this theory into practice.Is there a good discussion of vtapes
> somewhere?
> 
> 
> 
> I have this line in amanda.conf:
> 
> tapetype "NAS"
> tpchanger "chg-disk:/etc/amanda/mail.tclc.org/dst"
> labelstr "vtape.[0-9][0-9]"
> 
> 
> 
> I am apparently not doing what I want to do, which is point AMANDA to my
> NAS:
> 
> bash-4.2$ ls -al /etc/amanda/mail.tclc.org/

You are free to do as you like but I recommend the following (my own way
of doing it, more standard ...)

/etc should contain only config

Not vtapes, not data, not logs.

I prefer mounted filesystems under /mnt, and logs under /var/log (or in
systemd journal ... another topic)

I mount my NAS or external disks under /mnt, like in

# /etc/fstab

UUID=5a5a9927-995f-4f0f-98ff-d222561f84ff /mnt/externaldisk1 ext4
relatime,noauto,user 0 1

chown these dirs (= mounted fs) to your amandauser to allow amanda
rw-access.

and then define your chg-disk changer as in:

tpchanger "chg-disk:/mnt/externaldisk1"

proceed from there ...

Did you read:

https://wiki.zmanda.com/index.php/How_To:Set_Up_Virtual_Tapes#Configuration

(maybe it needs updates as well)

?