from:"A R"

Depending on what I'm testing and its importance I may just # cp 
tapelist.yesterday tapelist or manually alter it.

-Original Message-
From: Debra S Baddorf  
Sent: Monday, November 26, 2018 3:25 PM
To: Cuttler, Brian R (HEALTH) 
Cc: Debra S Baddorf ; Debra S Baddorf ; 
amanda-users 
Subject: Re: Configuration Rollback [Was: Reusable]

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


> On Nov 26, 2018, at 2:19 PM, Cuttler, Brian R (HEALTH) 
>  wrote:
>
> Deb,
>
> I'm with you, periodically I have to test something, or will start an 
> additional backup to help move data after a failure of some sort but in 
> general I allow cron to start # amdump once/day. My understanding matches 
> yours, balance will get thrown off, amanda may advance dumps but you chew up 
> a lot of tape and do a lot of I/O for little overall gain if you are running 
> multiple dumps as a matter of course.

When I have something that failed/was missed  OR a new node or DLE to add,  I 
do amdump config —no-taper  node  DLE so test the dump,  but leave the results 
on my holding disk.  It’ll be flushed when tonight’s backup starts.
So I don’t HAVE to chew up tape, just to test things.   :)

Deb Baddorf


>
> I have even gone so far as run run multiple dumps across a very small 
> (perhaps "1") DLE to test include/exclude or get a new dumptype (snapshot) or 
> compress(pig/parallel zip) tested, but do not run multiple dumps as a matter 
> of routine.
>
> In my mind running many small DLEs can be self-defeating, as can running very 
> few very large once, each hitting a different set of constraints.
>
> My samba shares are on separate ZFS mount points and I snapshot them. My home 
> directories are also on separate ZFS mount points but individual backups were 
> untenable so I glob them by letter, but that means I can't do snapshots.
>
> Based on the latest emails I think Chris may have moved on, but he has these 
> additional answers for when he cycles back.
>
> Thanks,
> Brian
>
>
> -Original Message-
> From: Debra S Baddorf 
> Sent: Monday, November 26, 2018 3:00 PM
> To: amanda-users 
> Cc: Debra S Baddorf ; Debra S Baddorf 
> ; Cuttler, Brian R (HEALTH) 
> 
> Subject: Re: Configuration Rollback [Was: Reusable]
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
>
>>
>> -Original Message-
>> From: owner-amanda-us...@amanda.org  
>> On Behalf Of Debra S Baddorf
>> Sent: Monday, November 26, 2018 2:04 PM
>> To: amanda-users 
>> Cc: Debra S Baddorf 
>> Subject: Re: Configuration Rollback [Was: Reusable]
>>
>> ATTENTION: This email came from an external source. Do not open attachments 
>> or click on links from unknown senders or unexpected emails.
>>
>>
>>> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger 
>>>  wrote:
>>>
>>> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie  wrote:
>>> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote:
>>>> Hi Folks,
>>>>
>>>> I have written some very small DLEs so I can rip through weeks of 
>>>> backups in minutes. I've learned some things.
>>>
>>
>> Am I wrong in thinking that you cannot do extra backups,  to get to the end 
>> of your  “dumpcycle” faster?
>> Dumpcycle is explicitly in days,  not number of times run.   Isn’t it?
>>
>> Deb Baddorf
>> Fermilab
>>
>>
>>
>> On Nov 26, 2018, at 1:21 PM, Cuttler, Brian R (HEALTH) 
>>  wrote:
>>
>> Deb,
>>
>> Not sure if I'm understanding your question. If so I believe Amanda was 
>> built with the concept of a once/day run schedule taking into account 
>> runs/cycle as well as days/dumpcycle (for instance 5 run days in a one week 
>> dump cycle).
>>
>> Brian
>
> Yes, I agree.  At one point,  Chris was trying to speed this up by doing 21 
> runs in 10 minutes or so.
> Perhaps he has stopped that,  and people are just continuing to quote that 
> line (above).   It’s that line that’s bothering me.
>
> He did ask  "Can I specify "dumpcycle" as an elapsed count rather than an 
> elapsed time?”
> Per the wiki help files,  dumpcycle seems to be explicitly in “days”  and 
> cannot be changed or sped up.
> (  
> https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.
> com_url-3Fk-3D42d018d223e76922.42d2e1e7-2D4a9f6eb7b4f1e3bb-26u-3Dhttps
> -3A__wiki.zmanda.com_index.php_Dumpcycle=DwIGaQ=gRgGjJ3BkIsb5y6s49
> QqsA=HMrKaRiCv4jddln9fLPIOw=

RE: Configuration Rollback [Was: Reusable]

Deb,

I'm with you, periodically I have to test something, or will start an 
additional backup to help move data after a failure of some sort but in general 
I allow cron to start # amdump once/day. My understanding matches yours, 
balance will get thrown off, amanda may advance dumps but you chew up a lot of 
tape and do a lot of I/O for little overall gain if you are running multiple 
dumps as a matter of course.

I have even gone so far as run run multiple dumps across a very small (perhaps 
"1") DLE to test include/exclude or get a new dumptype (snapshot) or 
compress(pig/parallel zip) tested, but do not run multiple dumps as a matter of 
routine.

In my mind running many small DLEs can be self-defeating, as can running very 
few very large once, each hitting a different set of constraints.

My samba shares are on separate ZFS mount points and I snapshot them. My home 
directories are also on separate ZFS mount points but individual backups were 
untenable so I glob them by letter, but that means I can't do snapshots.

Based on the latest emails I think Chris may have moved on, but he has these 
additional answers for when he cycles back.

Thanks,
Brian

-Original Message-
From: Debra S Baddorf  
Sent: Monday, November 26, 2018 3:00 PM
To: amanda-users 
Cc: Debra S Baddorf ; Debra S Baddorf ; 
Cuttler, Brian R (HEALTH) 
Subject: Re: Configuration Rollback [Was: Reusable]

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

>
> -Original Message-
> From: owner-amanda-us...@amanda.org  On 
> Behalf Of Debra S Baddorf
> Sent: Monday, November 26, 2018 2:04 PM
> To: amanda-users 
> Cc: Debra S Baddorf 
> Subject: Re: Configuration Rollback [Was: Reusable]
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
>
>> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger 
>>  wrote:
>>
>> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie  wrote:
>> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote:
>>> Hi Folks,
>>>
>>> I have written some very small DLEs so I can rip through weeks of 
>>> backups in minutes. I've learned some things.
>>
>
> Am I wrong in thinking that you cannot do extra backups,  to get to the end 
> of your  “dumpcycle” faster?
> Dumpcycle is explicitly in days,  not number of times run.   Isn’t it?
>
> Deb Baddorf
> Fermilab
>
>
>
> On Nov 26, 2018, at 1:21 PM, Cuttler, Brian R (HEALTH) 
>  wrote:
>
> Deb,
>
> Not sure if I'm understanding your question. If so I believe Amanda was built 
> with the concept of a once/day run schedule taking into account runs/cycle as 
> well as days/dumpcycle (for instance 5 run days in a one week dump cycle).
>
> Brian

Yes, I agree.  At one point,  Chris was trying to speed this up by doing 21 
runs in 10 minutes or so.
Perhaps he has stopped that,  and people are just continuing to quote that line 
(above).   It’s that line that’s bothering me.

He did ask  "Can I specify "dumpcycle" as an elapsed count rather than an 
elapsed time?”
Per the wiki help files,  dumpcycle seems to be explicitly in “days”  and 
cannot be changed or sped up.
(  
https://protect2.fireeye.com/url?k=42d018d223e76922.42d2e1e7-4a9f6eb7b4f1e3bb=https://wiki.zmanda.com/index.php/Dumpcycle
  )

Chris also asked  "Are "dumpcycle" and "runspercycle" conflicting with each 
other?”
Even if you occasionally do extra amdump runs  (I do),  that doesn’t bother the 
“runspercycle” count.  It still results in   “at least one level 0 within
dumpcycle days”.Runspercycle just lets amanda gauge numbers for balance 
adjusting, and maybe promoting a DLE to do an early level 0.
Doing 21 runs in NN minutes will use up all your vtapes,  but will not force 
more than 1 level 0.

Maybe I’m being pedantic,  and he’s looking at other issues now.  If so, 
nevermind me!
:)

Deb Baddorf

RE: Configuration Rollback [Was: Reusable]

Deb,

Not sure if I'm understanding your question. If so I believe Amanda was built 
with the concept of a once/day run schedule taking into account runs/cycle as 
well as days/dumpcycle (for instance 5 run days in a one week dump cycle).

Brian

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Debra S Baddorf
Sent: Monday, November 26, 2018 2:04 PM
To: amanda-users 
Cc: Debra S Baddorf 
Subject: Re: Configuration Rollback [Was: Reusable]

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

> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger  
> wrote:
>
> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie  wrote:
> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote:
> > Hi Folks,
> >
> > I have written some very small DLEs so I can rip through weeks of 
> > backups in minutes. I've learned some things.
>

Am I wrong in thinking that you cannot do extra backups,  to get to the end of 
your  “dumpcycle” faster?
Dumpcycle is explicitly in days,  not number of times run.   Isn’t it?

Deb Baddorf
Fermilab

RE: Another dumper question

I believe maxdumps is max concurrent dumps across all clients.

You might have 10 clients each with an inparallel of 2, giving 20 possible 
concurrent dumps, but because of server limitations you might set maxdumps to 
something between 2 and 20.

-Original Message-
From: Chris Nighswonger  
Sent: Monday, November 26, 2018 1:57 PM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: Another dumper question

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


inparallel 10

maxdumps not listed, so I'm assuming the default of 1 is being observed.

I'm not sure that the maxdumps parameter would affect dumping DLEs from 
multiple clients in parallel, though. The manpage states, "The maximum number 
of backups from a single host that Amanda will attempt to run in parallel." 
That seems to indicate that this parameter controls parallel dumps of DLEs on a 
single client.

Kind regards,
Chris
On Mon, Nov 26, 2018 at 1:50 PM Cuttler, Brian R (HEALTH) 
 wrote:
>
> Did you check your maxdumps and inparallel parameters?
>
> -Original Message-
> From: owner-amanda-us...@amanda.org  On 
> Behalf Of Chris Nighswonger
> Sent: Monday, November 26, 2018 1:34 PM
> To: amanda-users@amanda.org
> Subject: Another dumper question
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
>
> So in one particular configuration I have the following lines:
>
> inparallel 10
> dumporder "STSTSTSTST"
>
> I would assume that that amanda would spawn 10 dumpers in parallel and 
> execute them giving priority to largest size and largest time alternating. I 
> would assume that amanda would do some sort of sorting of the DLEs based on 
> size and time, set them in descending order, and the run the first 10 based 
> on the list thereby utilizing all 10 permitted dumpers in parallel.
>
> However, based on the amstatus excerpt below, it looks like amanda simply 
> starts with the largest size and runs the DLEs one at a time, not making 
> efficient use of parallel dumpers at all. This has the unhappy results at 
> times of causing amdump to be running when the next backup is executed.
>
> I have changed the dumporder to STSTStstst for tonight's run to see if that 
> makes any  difference. But I don't have much hope it will.
>
> Any thoughts?
>
> Kind regards,
> Chris
>
>
>
>
> From Mon Nov 26 01:00:01 EST 2018
>
> 1   4054117k waiting for dumping
> 1  6671k waiting for dumping
> 1   222k waiting for dumping
> 1  2568k waiting for dumping
> 1  6846k waiting for dumping
> 1125447k waiting for dumping
> 1 91372k waiting for dumping
> 192k waiting for dumping
> 132k waiting for dumping
> 132k waiting for dumping
> 132k waiting for dumping
> 132k waiting for dumping
> 1290840k waiting for dumping
> 1 76601k waiting for dumping
> 186k waiting for dumping
> 1 71414k waiting for dumping
> 0  44184811k waiting for dumping
> 1   281k waiting for dumping
> 1  6981k waiting for dumping
> 150k waiting for dumping
> 1 86968k waiting for dumping
> 1 81649k waiting for dumping
> 1359952k waiting for dumping
> 0 198961004k dumping 159842848k ( 80.34%) (7:23:39)
> 1 73966k waiting for dumping
> 1821398k waiting for dumping
> 1674198k waiting for dumping
> 0 233106841k dump done (7:23:37), waiting for writing to tape
> 132k waiting for dumping
> 132k waiting for dumping
> 1166876k waiting for dumping
> 132k waiting for dumping
> 1170895k waiting for dumping
> 1162817k waiting for dumping
> 0 failed: planner: [Request to client failed: Connection timed out]
> 132k waiting for dumping
> 132k waiting for dumping
> 053k waiting for dumping
> 0  77134628k waiting for dumping
> 1  2911k waiting for dumping
> 136k waiting for dumping
> 132k waiting for dumping
> 1 84935k waiting for dumping
>
> SUMMARY  part  real  estimated
>size   size
> partition   :  43
> estimated   :  42559069311k
> flush   :   0 0k
> failed  :   10k   (  0.00%)
> wait for dumping:  40128740001k   ( 23.03%)
> dumping to tape :   00k   (  0.00%)
> dumping :   1 159842848k 198961004k ( 80.34%) ( 28.59%)
> dumped  :   1 233106841k 231368306k (100.75%) ( 41.70%)
> wait for writing:   1 233106841k 23

RE: Another dumper question

Did you check your maxdumps and inparallel parameters?

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Nighswonger
Sent: Monday, November 26, 2018 1:34 PM
To: amanda-users@amanda.org
Subject: Another dumper question

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

So in one particular configuration I have the following lines:

inparallel 10
dumporder "STSTSTSTST"

I would assume that that amanda would spawn 10 dumpers in parallel and execute 
them giving priority to largest size and largest time alternating. I would 
assume that amanda would do some sort of sorting of the DLEs based on size and 
time, set them in descending order, and the run the first 10 based on the list 
thereby utilizing all 10 permitted dumpers in parallel.

However, based on the amstatus excerpt below, it looks like amanda simply 
starts with the largest size and runs the DLEs one at a time, not making 
efficient use of parallel dumpers at all. This has the unhappy results at times 
of causing amdump to be running when the next backup is executed.

I have changed the dumporder to STSTStstst for tonight's run to see if that 
makes any  difference. But I don't have much hope it will.

Any thoughts?

Kind regards,
Chris

>From Mon Nov 26 01:00:01 EST 2018

1   4054117k waiting for dumping
1  6671k waiting for dumping
1   222k waiting for dumping
1  2568k waiting for dumping
1  6846k waiting for dumping
1125447k waiting for dumping
1 91372k waiting for dumping
192k waiting for dumping
132k waiting for dumping
132k waiting for dumping
132k waiting for dumping
132k waiting for dumping
1290840k waiting for dumping
1 76601k waiting for dumping
186k waiting for dumping
1 71414k waiting for dumping
0  44184811k waiting for dumping
1   281k waiting for dumping
1  6981k waiting for dumping
150k waiting for dumping
1 86968k waiting for dumping
1 81649k waiting for dumping
1359952k waiting for dumping
0 198961004k dumping 159842848k ( 80.34%) (7:23:39)
1 73966k waiting for dumping
1821398k waiting for dumping
1674198k waiting for dumping
0 233106841k dump done (7:23:37), waiting for writing to tape
132k waiting for dumping
132k waiting for dumping
1166876k waiting for dumping
132k waiting for dumping
1170895k waiting for dumping
1162817k waiting for dumping
0 failed: planner: [Request to client failed: Connection timed out]
132k waiting for dumping
132k waiting for dumping
053k waiting for dumping
0  77134628k waiting for dumping
1  2911k waiting for dumping
136k waiting for dumping
132k waiting for dumping
1 84935k waiting for dumping

SUMMARY  part  real  estimated
   size   size
partition   :  43
estimated   :  42559069311k
flush   :   0 0k
failed  :   10k   (  0.00%)
wait for dumping:  40128740001k   ( 23.03%)
dumping to tape :   00k   (  0.00%)
dumping :   1 159842848k 198961004k ( 80.34%) ( 28.59%)
dumped  :   1 233106841k 231368306k (100.75%) ( 41.70%)
wait for writing:   1 233106841k 231368306k (100.75%) ( 41.70%)
wait to flush   :   0 0k 0k (100.00%) (  0.00%)
writing to tape :   0 0k 0k (  0.00%) (  0.00%)
failed to tape  :   0 0k 0k (  0.00%) (  0.00%)
taped   :   0 0k 0k (  0.00%) (  0.00%)
9 dumpers idle  : 0
taper status: Idle
taper qlen: 1
network free kps: 0
holding space   : 436635431k ( 50.26%)
chunker0 busy   :  6:17:03  ( 98.28%)
 dumper0 busy   :  6:17:03  ( 98.28%)
 0 dumpers busy :  0:06:34  (  1.72%)   0:  0:06:34  (100.00%)
 1 dumper busy  :  6:17:03  ( 98.28%)   0:  6:17:03  (100.00%)

RE: Taper scan algorithm did not find an acceptable volume.

2018-11-20 Thread Cuttler, Brian R (HEALTH)

I prelabel my tables, both physical and virtual.

Amanda will mount it and report that it isn't an amanda tape. I've never 
configured automatic labeling.


-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Debra S Baddorf
Sent: Tuesday, November 20, 2018 2:14 PM
To: Chris Miller 
Cc: Debra S Baddorf ; amanda-users 
Subject: Re: Taper scan algorithm did not find an acceptable volume.

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


> On Nov 20, 2018, at 9:54 AM, Chris Miller  wrote:
>
> Hi Jon,
>
> - Original Message -
>> From: "Jon LaBadie"
>> To: "amanda-users" 
>> Sent: Monday, November 19, 2018 1:44:35 PM
>> Subject: Re: Taper scan algorithm did not find an acceptable volume.
>
>> As a general approach, an admin should not run new software systems 
>> until its dependices are independently verified.  For example client 
>> backups depand on a working network.  You should confirm the clients 
>> can reach the server and visa-versa.
>
> This is confirmed. From my AMANDA server, I can see each of my NAS as a SaMBa 
> share. I can ping each of my clients from the AMANDA server, and smbclient -L 
> let's me browse their filesystems. I don't think connectivity is my problem. 
> I think I am fighting my own ignorance exhibited in a badly configured AMANDA 
> server. I seek advice of detecting and correcting this very simple 
> configuration:
>
>mailto "bac...@tclc.org"   # space separated list of 
> operators at your site
>dumpuser "amandabackup"# the user to run dumps under
>org "Mail.TCLC.org"
>
>infofile "/var/amanda/info"
>logdir   "/var/amanda/Mail.TCLC.org"
>indexdir "/var/amanda/index"
>
>tapetype "NAS"
>tapedev  "chg-disk://etc/amanda/Mail.TCLC.org/dst"
>holdingdisk hd
>dumpcycle 1week
>runspercycle 7
>tapecycle 21
>
>define holdingdisk hd {
>directory "/var/amanda/hold"
>}
>
>includefile "advanced.conf"
>includefile "/etc/amanda/template.d/dumptypes"
>includefile "/etc/amanda/template.d/tapetypes"
>
>
>
>
>> You are setting up a vtape library, tapes to fill the library slots, 
>> and a changer to manipulate the vtapes in the library.  You should 
>> exercise these components with amanda commands before trying to 
>> backup your clients.
>>
>> Hmm, does amanda have any commands to exercise the changer and library?
>
> I assume that this is a rhetorical question. In my case it is a valid 
> question that I can't answer, but the answer to which may solve my problem. I 
> now know about "amadmin", and "amtape", and "locate am | grep "^am" | grep 
> bin" has revealed many more which justify greater familiarity, but I have no 
> idea how to proceed testing my vtape config. I would be appreciative if you 
> could give me an example of how to do this.
>
> Thanks for the help, Jon.
> --
> Chris.
>

When installing a new tape drive or tape library  (physical tapes, for me)
I read ~18 years ago  (can’t find where, anymore)   that I should exercise the
tape commands manually first.   Then attempt to get amanda to use them.

To whit:
amtape  slot 1
amtape config slot 2
amtape config slot 15   (jump around)
amtape config slot next
amtape config slot first   (either 0 or 1,  or whatever the first slot it’s 
been allowed)
amtape config slot last (the last slot)

I pre-label all my tapes, so I was able to do the above commands,  and see 
succcess
before proceeding to amanda commands.   Dunno if it will mount an unlabeled 
vtape?
But you need to have the above working first.

It couldn’t *hurt*  to prelabel all your vtapes,  but I know you don’t want to. 
 That may be
why it’s failing???I’ve never ventured into “unlabeled tape”  territory.   
Others?

Deb Baddorf
Fermilab

RE: tape pools, wrapping my mind around them

I believe that you would define tape pool of 80 for each, with regular 
expressions you may be able to have the same label string format but different 
tape number ranges.
Maybe like this?

Sales POOL1[0-9][0-9]
Support POOL2[0-9][0-9]
Research POOL3[0-9][0-9]

For sanity I think I'd define 3 tape pools in the one changer. You spend time 
loading and unloading tapes to find the pool and tapes you want, but since this 
is done without having to access a physical tape drive or robot it will take 
virtually no time at all.

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Jon LaBadie
Sent: Thursday, November 15, 2018 3:25 PM
To: amanda-users@amanda.org
Subject: tape pools, wrapping my mind around them

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


I currently have 240 Vtapes in a single changer.
Suppose I have 3 "departments", sales, research, and support.

Could I create 3 dumptype definitions so that all "sales" DLEs are backed up to 
a tape pool consisting of vtapes 1-80, "research" to vtapes 81-160, and 
"support" to vtapes 161-240?

If so, then a single config could handle keeping the various data separated 
while still maintaining balance etc.  Of course, is the balance on a tape pool 
basis or on a total configuration basis?

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

RE: Clients that return something else

I think if you want a disk image you want the native OS disk image utility, 
(file-system-type)dump. Dump, ufsdump, xfsdump, etc. Amanda supports this.

Do you ever need a disk image other than the boot volume? I realize some 
special applications may have file types that are not recognized for backup by 
tar, but that would be pretty rare.

From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Miller
Sent: Thursday, November 15, 2018 2:23 PM
To: amanda-users 
Subject: Re: Clients that return something else


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

Hi Brian
From: "Cuttler, Brian R (HEALTH)" 
mailto:brian.cutt...@health.ny.gov>>
To: "Chris Miller" mailto:c...@tryx.org>>, "amanda-users" 
mailto:amanda-users@amanda.org>>
Sent: Thursday, November 15, 2018 10:54:49 AM
Subject: RE: Clients that return something else
Why pipe dd to tar when you can just run tar?
Good question. tar works at the filesystem level but dd works at the disk block 
level and I'm not aware of any way that tar can create a disk image, so I need 
to read the disk with dd. AMANDA expects a tar saveset, so I need to pipe 
anything I create to tar.



Er – I think the answer is “yes”, but you may have to roll your own.
Yeah, so do I. I'm just not exactly sure how I tell the client what to do. It 
appears that the dumptype uses something symbolic, and leaves the client up to 
its own devices to determine what it means. I could also do this, but I'd 
really like to be able to define the script on the server. Also, it's not 
exactly clear to me how the client understands what "GNUTAR" or "DUMP" means 
locally -- something must see "GNUTAR" and conclude, "Oh, he wants to run 
/usr/sbin/tar". For example, if I could put "BASH" in my dumptype definition 
for "program", and include that code somehow, that would be perfect! Ever hear 
of anything like that?

Thanks for the help, Brian.
--
Chris.

V:916.974.0424
F:916.974.0428

RE: Clients that retunr something else


I’m configured amanda to run native client utilities gnutar, dump, star (shilly 
tar), er something else.

There are certain known and available/approved things you can do, but the 
bottom line is always – Amanda is an intelligent, scheduling, wrapper, 
client-server using OS native tools.

I think I was thinking pigzip (name?) rather than gzip.

Why pipe dd to tar when you can just run tar?

Note – some versions of gtar are considered broken for Amanda, don’t recall the 
versions or the specific reason (might have had to do with argument handling) 
but that is also likely ancient history.

For zfs file systems we’ve also utilized the snapshot option, perhaps out of 
reach because of the way you’ve globbed your DLEs together.

Er – I think the answer is “yes”, but you may have to roll your own.

From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Miller
Sent: Thursday, November 15, 2018 1:31 PM
To: amanda-users 
Subject: Clients that retunr something else


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

Hi Folks,

Is it possible to have the client run something else besides "tar", like, for 
example, "dd | tar"? Can I specify this from the server? Of course, it goes 
without saying that I need to be able to do the same thing on a Windows client, 
and now I've just said it, so maybe it needed to be said.

Thanks for the help,
--
Chris.

V:916.974.0424
F:916.974.0428

RE: Configuration confusion

I suppose you could have a small modification to your config file every day.

(scripted to run dynamically, # date has very useful output formatting)

# amdump config-type-1-day-${dayname}

With 7 dumps/week and three configs he can have 21 different backup files, 
completely defeating the scheduling but getting exactly the result he wants.

-Original Message-
From: Debra S Baddorf  
Sent: Thursday, November 15, 2018 1:39 PM
To: Cuttler, Brian R (HEALTH) 
Cc: Debra S Baddorf ; Charles Curley 
; amanda-users 
Subject: Re: Configuration confusion

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


If you’ve disable level 0 backups in the setup,  *WILL*  it do a level 0,  even 
if you try to force it?
I have one hge config that is set up this way.   I have to edit the 
amanda.conf  and REMOVE the  “incr-only” lines
when I want to force a level 0.   Specially since you HAVE to start with a 
level 0, initially.
I’m pretty sure I’ve tried to force some level 0’s and found they failed,  till 
I removed the  “incr-only”  bits.

Deb Baddorf

> On Nov 15, 2018, at 12:16 PM, Cuttler, Brian R (HEALTH) 
>  wrote:
>
> Alternatively - configure all DLE to be non-fulls, disable level 0 backups 
> entirely and run cron jobs to force level 0 dumps on particular DLEs.
> That way you can get level 0 when you want it to occur an no other DLE will 
> advance to a level 0 on its own.
>
> # amadmin config force client DLE
>
> -Original Message-
> From: owner-amanda-us...@amanda.org  On 
> Behalf Of Charles Curley
> Sent: Thursday, November 15, 2018 12:31 PM
> To: amanda-users 
> Subject: Re: Configuration confusion
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
>
> On Thu, 15 Nov 2018 09:03:00 -0800 (PST) Chris Miller  wrote:
>
>> If I run three backups, serial or otherwise, then do they know about 
>> each other? Meaning, is AMANDA smart enough to know not to run more 
>> than one level 0 dump per night? The problem is that level 0 backups 
>> take several hours and if I run multiple then I will still be 
>> completing last nights backup when everybody comes in the next 
>> morning. That would be embarrassing. "Sorry, I didn't complete my 
>> work last night, so you can't continue yours."
>
> Ah, that helps. My experience is in a SOHO environment, so take with the salt 
> shaker handy.
>
> The different configurations don't know about each other at all. So you could 
> in theory have a night in which all three run level 0 backups.
> The only way I know to get that kind of co-ordination is to have one 
> configuration which then backs up all three machines. Unfortunately your 
> requirement not to mix the backups due to custodial and security requirements 
> may kill that idea.
>
> Another thing to look at is to break your DLEs up into lots of smaller DLEs. 
> You'll get more level 0 backups, but they'll be spread around the week more 
> evenly.
>
> Or consider having a longer tape cycle. That means fewer level 0 backups in 
> any one week.
>
> --
> "When we talk of civilization, we are too apt to limit the meaning of the 
> word to its mere embellishments, such as arts and sciences; but the true 
> distinction between it and barbarism is, that the one presents a state of 
> society under the protection of just and well-administered law, and the other 
> is left to the chance government of brute force."
> - The Rev. James White, Eighteen Christian Centuries, 1889 Key 
> fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__charlescurley.com
> =DwIDAg=gRgGjJ3BkIsb5y6s49QqsA=HMrKaRiCv4jddln9fLPIOw=fnbC4Yi7
> 6_5ky_32Tf9A5Geluildi-avCP3JC0hU2RA=oia-zSsMzlRk8WRCNW_-9vpn6VWUX7Vm
> XSyeRVdmgcM=
>

RE: Configuration confusion

From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Miller
Sent: Thursday, November 15, 2018 12:29 PM
To: amanda-users 
Subject: Re: Configuration confusion

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

Hi Brian,
From: "Cuttler, Brian R (HEALTH)" 
mailto:brian.cutt...@health.ny.gov>>
To: "Cuttler, Brian R (HEALTH)" 
mailto:brian.cutt...@health.ny.gov>>, "Chris 
Miller" mailto:c...@tryx.org>>, "amanda-users" 
mailto:amanda-users@amanda.org>>
Sent: Wednesday, November 14, 2018 9:08:26 AM
Subject: RE: Configuration confusion
Tape custody – means what, retention policy or storage of the tape when not in 
the drive/juke?
Yes. Simplest is local custody. Off site custody comes in two media flavors -- 
local media and cloud. Off site costs, so we want to minimize this, as well as 
increases the response time for restorations. You get the idea. I don't use 
tapes; I use removable disks, optical media,and usb keydrives. General this is 
determined by the client, so when I plan this, I simply consider which client 
backups need to be sequestered where. This gives me a configuration where I can 
think in terms of "client  gets backedup to NAS ", where NAS  has 
different properties and different dispositions.

  *   Yes, I understand. I have worked at sites where offsite was someone’s 
house (tapes never came back in the right cycle, seems if you use them as hills 
under your train set you might not return the oldest tapes but bring back a 
mix). Other sites had tapes stored in the fire protected computer room, still 
others had them in a room in another part of the building, but it is a very big 
building.

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

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

Each Amanda config will look to level nightly data, but you will have nights 
with relatively little and nights with relatively large data volume swings, er 
think wave interference from physics. You eliminate a lot of that by combining 
disklists into a single configuration.
Yes! "Each Amanda config will look to level nightly data ..."  This is my 
principle question, and I seek to level the nightly data across all configs on 
a given night, which I recognize can't be done, so I seek to combine my 
multiple configs into a single config which specifies multiple sets of DLEs 
being mapped to multiple tapedev, if that can be done. For example, if the 
definition of tapedev had a "DLE ..." argument, and AMANDA were capable of this 
additional dimension of scheduling.

  *   See reply I put in subsequent email by Charles Curley that was a response 
to you.

Amanda will backup a new DLE at level 0 the first time it sees it. If you are 
worried about running long you will want to phase in the DLEs across several 
evenings. You may want to add the largest on Friday night, assuming that no one 
cares how late Amanda runs into Saturday. You will want to avoid adding 
multiple large DLEs on a single night, add a large and a small each night until 
they are all added.
"Phasing" my backup jobs may be my only choice, as that is exactly the problem 
I seek to avoid and I have been admonished to not try to subvert the scheduler 
by forcing level 0 backups to happen on my schedule. As I continue to discuss 
this, I am more and more convinced that AMANDA cannot schedule in two 
dimensions {(backups / night) X (nights / cycle)}

So, suppose I wanted to force my level 0 backups to happen at my discretion, so 
I can level my nightly run times. How would I do that?

Thanks for the help, Brian.
--
Chris.

V:916.974.0424
F:916.974.0428

RE: Configuration confusion

Alternatively - configure all DLE to be non-fulls, disable level 0 backups 
entirely and run cron jobs to force level 0 dumps on particular DLEs.
That way you can get level 0 when you want it to occur an no other DLE will 
advance to a level 0 on its own.

# amadmin config force client DLE

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Charles Curley
Sent: Thursday, November 15, 2018 12:31 PM
To: amanda-users 
Subject: Re: Configuration confusion

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

On Thu, 15 Nov 2018 09:03:00 -0800 (PST) Chris Miller  wrote:

> If I run three backups, serial or otherwise, then do they know about 
> each other? Meaning, is AMANDA smart enough to know not to run more 
> than one level 0 dump per night? The problem is that level 0 backups 
> take several hours and if I run multiple then I will still be 
> completing last nights backup when everybody comes in the next 
> morning. That would be embarrassing. "Sorry, I didn't complete my work 
> last night, so you can't continue yours."

Ah, that helps. My experience is in a SOHO environment, so take with the salt 
shaker handy.

The different configurations don't know about each other at all. So you could 
in theory have a night in which all three run level 0 backups.
The only way I know to get that kind of co-ordination is to have one 
configuration which then backs up all three machines. Unfortunately your 
requirement not to mix the backups due to custodial and security requirements 
may kill that idea.

Another thing to look at is to break your DLEs up into lots of smaller DLEs. 
You'll get more level 0 backups, but they'll be spread around the week more 
evenly.

Or consider having a longer tape cycle. That means fewer level 0 backups in any 
one week.

--
"When we talk of civilization, we are too apt to limit the meaning of the word 
to its mere embellishments, such as arts and sciences; but the true distinction 
between it and barbarism is, that the one presents a state of society under the 
protection of just and well-administered law, and the other is left to the 
chance government of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889 Key fingerprint = 
CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB https://charlescurley.com

RE: Configuration confusion

2018-11-14 Thread Cuttler, Brian R (HEALTH)

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

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

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

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

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

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

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


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

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

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

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

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


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

Hi Folks,

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

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

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

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

RE: Configuration confusion

2018-11-14 Thread Cuttler, Brian R (HEALTH)

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

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

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

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


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

Hi Folks,

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

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

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

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

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

Thanks for the help,
--
Chris.

V:916.974.0424
F:916.974.0428

RE: Monitor and Manage

2018-11-14 Thread Cuttler, Brian R (HEALTH)

Chris,

How many work areas? How many tape drives?

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

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

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

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

Brian


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



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


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

Hi Folks,

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

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

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

In short, how do I monitor and mange AMANDA?

Thanks for the help,
--
Chris.

V:916.974.0424
F:916.974.0428

RE: Breaking DLEs up

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


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,

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



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<http://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<mailto:amanda-users@amanda.org>
Subject: Re: Breaking DLEs up


ATTENTION: This email came from an external source. Do not open attac

RE: Breaking DLEs up

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<mailto: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> 
mailto:owner-amanda-us...@amanda.org>> On Behalf 
Of Chris Nighswonger
Sent: Thursday, November 8, 2018 11:12 AM
To: amanda-users@amanda.org<mailto: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

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> 
mailto:owner-amanda-us...@amanda.org>> On Behalf 
Of Chris Nighswonger
Sent: Thursday, November 8, 2018 11:12 AM
To: amanda-users@amanda.org<mailto: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

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: dumporder

Yah, the plot is a very helpful tool. You can get it to work harder if you can 
enlarge the work area or add an additional work area.

Also you might want to check your chunk size, tendency, at least when I started 
out, was for many smaller files, I increased the size of the chunks in the 
holding area and believe it help to improve performance as there were few files 
and fewer file creates/accesses/deletes later on.

From: Chris Nighswonger 
Sent: Tuesday, November 6, 2018 2:38 PM
To: Cuttler, Brian R (HEALTH) 
Cc: ned.danie...@duke.edu; amanda-users@amanda.org
Subject: Re: dumporder

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

Setting the output to postscript (-p) and then converting to pdf (ps2pdf) 
worked the trick.

It looks like my holding disk maxes out.

[20181106020001.jpg]

Christopher Nighswonger
Faculty Member
Network & Systems Director
Foundations Bible College & Seminary
www.foundations.edu<https://protect2.fireeye.com/url?k=5fb1533cbfe0ffe5.5fb3aa09-e5969cc601a99a3a=http://www.foundations.edu>
www.fbcradio.org<https://protect2.fireeye.com/url?k=7e89f7371429ff69.7e8b0e02-990af0384ddad8fd=http://www.fbcradio.org>
-
NOTICE: The information contained in this electronic mail message is intended 
only for the use of the intended recipient, and may also be protected by the 
Electronic Communications Privacy Act, 18 USC Sections 2510-2521. If the reader 
of this message is not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please reply to 
the sender, and delete the original message. Thank you.

On Tue, Nov 6, 2018 at 2:26 PM Cuttler, Brian R (HEALTH) 
mailto:brian.cutt...@health.ny.gov>> wrote:
Xhost, and environmental variable DISPLAY, plus your output needs to be x11.
You can also write a pdf file and print it, or view with an appropriate viewer.

-Original Message-
From: owner-amanda-us...@amanda.org<mailto:owner-amanda-us...@amanda.org> 
mailto:owner-amanda-us...@amanda.org>> On Behalf 
Of Chris Nighswonger
Sent: Tuesday, November 6, 2018 1:18 PM
To: ned.danie...@duke.edu<mailto:ned.danie...@duke.edu>
Cc: amanda-users@amanda.org<mailto:amanda-users@amanda.org>
Subject: Re: dumporder

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

This seems to work:

amplot /var/backups/campus/log/amdump.1

Running under the amanda user.

However, the issue now is the attempt to write the output to the X11 terminal:

gnuplot: unable to open display ''
gnuplot: X11 aborted.

Not sure what all that's about. So I'm doing a bit of hacking on the gnuplot 
script to have it write the results out to a png file.

Chris
On Tue, Nov 6, 2018 at 12:29 PM Ned Danieley 
mailto:ned.danie...@duke.edu>> wrote:
>
> On Tue, Nov 06, 2018 at 11:50:57AM -0500, Chris Nighswonger wrote:
> > Digging around a bit, it appears that it might be a reference to a
> > file which is missing. From amplot.g, line 62 we see:
> >
> > # file title has the parameters that this program needs load 'title'
> > plot"run_queue" title "Run Queue" with lines,\
> > "tape_queue" title "Tape Queue" with lines,\
> > "finished"  title "Dumps Finished" with lines,\
> > "bandw_free" title "Bandwidth Allocated" with lines, \
> > "disk_alloc" title "%Disk Allocated" with lines, \
> > "tape_wait" title "%Tape Wait" with lines,\
> > "tape_idle" title "Taper Idle" with lines,\
> > "dump_idle" title "Dumpers Idle" with lines
> >
> > Where is a developer when you need one? :-P
>
> looks like the awk script is supposed to generate 'title'. on my
> system, I have to run amplot as user 'amanda'. that means that I have
> to be in a directory where amanda has write permission, otherwise
> title can't be generated. my home directory doesn't work, but a temp
> dir that's chmod 777 does.
>
> --
> Ned Danieley (ned.danie...@duke.edu<mailto:ned.danie...@duke.edu>)
> Department of Biomedical Engineering
> Box 90281, Duke University
> Durham, NC  27708   (919) 660-5111
>
> http://dilbert.com/strips/comic/2012-02-11/

RE: dumporder

Xhost, and environmental variable DISPLAY, plus your output needs to be x11.
You can also write a pdf file and print it, or view with an appropriate viewer.

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Nighswonger
Sent: Tuesday, November 6, 2018 1:18 PM
To: ned.danie...@duke.edu
Cc: amanda-users@amanda.org
Subject: Re: dumporder

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


This seems to work:

amplot /var/backups/campus/log/amdump.1

Running under the amanda user.

However, the issue now is the attempt to write the output to the X11 terminal:


gnuplot: unable to open display ''
gnuplot: X11 aborted.

Not sure what all that's about. So I'm doing a bit of hacking on the gnuplot 
script to have it write the results out to a png file.

Chris
On Tue, Nov 6, 2018 at 12:29 PM Ned Danieley  wrote:
>
> On Tue, Nov 06, 2018 at 11:50:57AM -0500, Chris Nighswonger wrote:
> > Digging around a bit, it appears that it might be a reference to a 
> > file which is missing. From amplot.g, line 62 we see:
> >
> > # file title has the parameters that this program needs load 'title'
> > plot"run_queue" title "Run Queue" with lines,\
> > "tape_queue" title "Tape Queue" with lines,\
> > "finished"  title "Dumps Finished" with lines,\
> > "bandw_free" title "Bandwidth Allocated" with lines, \
> > "disk_alloc" title "%Disk Allocated" with lines, \
> > "tape_wait" title "%Tape Wait" with lines,\
> > "tape_idle" title "Taper Idle" with lines,\
> > "dump_idle" title "Dumpers Idle" with lines
> >
> > Where is a developer when you need one? :-P
>
> looks like the awk script is supposed to generate 'title'. on my 
> system, I have to run amplot as user 'amanda'. that means that I have 
> to be in a directory where amanda has write permission, otherwise 
> title can't be generated. my home directory doesn't work, but a temp 
> dir that's chmod 777 does.
>
> --
> Ned Danieley (ned.danie...@duke.edu)
> Department of Biomedical Engineering
> Box 90281, Duke University
> Durham, NC  27708   (919) 660-5111
>
> http://dilbert.com/strips/comic/2012-02-11/

RE: dumporder

I think you need to provide the name of the amconfig. I believe it reads 
amanda.conf.

-Original Message-
From: Chris Nighswonger  
Sent: Tuesday, November 6, 2018 11:51 AM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: dumporder

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


Digging around a bit, it appears that it might be a reference to a file which 
is missing. From amplot.g, line 62 we see:

# file title has the parameters that this program needs load 'title'
plot"run_queue" title "Run Queue" with lines,\
"tape_queue" title "Tape Queue" with lines,\
"finished"  title "Dumps Finished" with lines,\
"bandw_free" title "Bandwidth Allocated" with lines, \
"disk_alloc" title "%Disk Allocated" with lines, \
"tape_wait" title "%Tape Wait" with lines,\
"tape_idle" title "Taper Idle" with lines,\
    "dump_idle" title "Dumpers Idle" with lines

Where is a developer when you need one? :-P

On Tue, Nov 6, 2018 at 11:45 AM Cuttler, Brian R (HEALTH) 
 wrote:
>
> It has been a while, title might be the org string from amanda.conf?
> I'm sorry, it has been years since I ran it regularly.
>
> -Original Message-
> From: Chris Nighswonger 
> Sent: Tuesday, November 6, 2018 11:42 AM
> To: Cuttler, Brian R (HEALTH) 
> Cc: amanda-users@amanda.org
> Subject: Re: dumporder
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
>
> The amplot utility is new to me. Here is what it says when I attempt to run 
> it:
>
> root@scriptor:~# amplot
> /var/log/amanda/server/campus/amdump.20181106020001.debug
> Displaying graph on the screen,  for next graph : MISSING SPACE 
> DECLARATION "title", line 62: Cannot open script file 'title'
>
> I have both gnuplot and gawk installed on the backup server.
>
> On Tue, Nov 6, 2018 at 11:10 AM Cuttler, Brian R (HEALTH) 
>  wrote:
> >
> > Chris,
> >
> > There is an amplot utility that I used to run a lot, it would show me what 
> > I was constrained on, often holding space, which if you are running a bunch 
> > of large dumps to start off with could constrain dumping later on.
> >
> >
> > -Original Message-
> > From: owner-amanda-us...@amanda.org  
> > On Behalf Of Chris Nighswonger
> > Sent: Tuesday, November 6, 2018 11:02 AM
> > To: amanda-users@amanda.org
> > Subject: Re: dumporder
> >
> > ATTENTION: This email came from an external source. Do not open attachments 
> > or click on links from unknown senders or unexpected emails.
> >
> >
> > On Mon, Nov 5, 2018 at 1:31 PM Chris Nighswonger 
> >  wrote:
> > >
> > > Is there any wisdom available on optimization of dumporder?
> > >
> >
> > After looking over the feedback from Brian and Austin and reviewing the 
> > actual sizes of the DLEs, I ended up with this sort of thing:
> >
> > inparallel 15
> > dumporder "STs"
> >
> > Which resulted in a reduced time over what I have been seeing. Here are 
> > some stats from amstatus for this config. It looks like I could drop about 
> > half of the dumpers and still be fine. Any idea what causes the dumpers 
> > over the first five to be utilized less?
> >
> >  dumper0 busy   :  5:13:42  ( 97.98%)
> >  dumper1 busy   :  1:12:09  ( 22.54%)
> >  dumper2 busy   :  0:40:30  ( 12.65%)
> >  dumper3 busy   :  0:33:44  ( 10.54%)
> >  dumper4 busy   :  0:03:47  (  1.19%)
> >  dumper5 busy   :  0:37:32  ( 11.73%)
> >  dumper6 busy   :  0:02:00  (  0.62%)
> >  dumper7 busy   :  0:00:57  (  0.30%)
> >  dumper8 busy   :  0:05:54  (  1.85%)
> >  dumper9 busy   :  0:04:38  (  1.45%)
> > dumper10 busy   :  0:00:16  (  0.08%)
> > dumper11 busy   :  0:01:39  (  0.52%)
> > dumper12 busy   :  0:00:01  (  0.01%)
> >  0 dumpers busy :  0:02:43  (  0.85%)   0:  0:02:43  
> > (100.00%)
> >  1 dumper busy  :  3:39:13  ( 68.47%)   0:  3:39:13  
> > (100.00%)
> >  2 dumpers busy :  0:23:10  (  7.24%)   0:  0:23:10  
> > (100.00%)
> >  3 dumpers busy :  1:07:57  ( 21.22%)   0:  1:07:57  
> > (100.00%)
> >  4 dumpers busy :  0:02:09  (  0.67%)   0:  0:02:09  ( 
> > 99.99%)
> >  5 dumpers busy :  0:01:07  (  0.35%)

RE: dumporder

It has been a while, title might be the org string from amanda.conf?
I'm sorry, it has been years since I ran it regularly.

-Original Message-
From: Chris Nighswonger  
Sent: Tuesday, November 6, 2018 11:42 AM
To: Cuttler, Brian R (HEALTH) 
Cc: amanda-users@amanda.org
Subject: Re: dumporder

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


The amplot utility is new to me. Here is what it says when I attempt to run it:

root@scriptor:~# amplot
/var/log/amanda/server/campus/amdump.20181106020001.debug
Displaying graph on the screen,  for next graph : MISSING SPACE DECLARATION 
"title", line 62: Cannot open script file 'title'

I have both gnuplot and gawk installed on the backup server.

On Tue, Nov 6, 2018 at 11:10 AM Cuttler, Brian R (HEALTH) 
 wrote:
>
> Chris,
>
> There is an amplot utility that I used to run a lot, it would show me what I 
> was constrained on, often holding space, which if you are running a bunch of 
> large dumps to start off with could constrain dumping later on.
>
>
> -Original Message-
> From: owner-amanda-us...@amanda.org  On 
> Behalf Of Chris Nighswonger
> Sent: Tuesday, November 6, 2018 11:02 AM
> To: amanda-users@amanda.org
> Subject: Re: dumporder
>
> ATTENTION: This email came from an external source. Do not open attachments 
> or click on links from unknown senders or unexpected emails.
>
>
> On Mon, Nov 5, 2018 at 1:31 PM Chris Nighswonger 
>  wrote:
> >
> > Is there any wisdom available on optimization of dumporder?
> >
>
> After looking over the feedback from Brian and Austin and reviewing the 
> actual sizes of the DLEs, I ended up with this sort of thing:
>
> inparallel 15
> dumporder "STs"
>
> Which resulted in a reduced time over what I have been seeing. Here are some 
> stats from amstatus for this config. It looks like I could drop about half of 
> the dumpers and still be fine. Any idea what causes the dumpers over the 
> first five to be utilized less?
>
>  dumper0 busy   :  5:13:42  ( 97.98%)
>  dumper1 busy   :  1:12:09  ( 22.54%)
>  dumper2 busy   :  0:40:30  ( 12.65%)
>  dumper3 busy   :  0:33:44  ( 10.54%)
>  dumper4 busy   :  0:03:47  (  1.19%)
>  dumper5 busy   :  0:37:32  ( 11.73%)
>  dumper6 busy   :  0:02:00  (  0.62%)
>  dumper7 busy   :  0:00:57  (  0.30%)
>  dumper8 busy   :  0:05:54  (  1.85%)
>  dumper9 busy   :  0:04:38  (  1.45%)
> dumper10 busy   :  0:00:16  (  0.08%)
> dumper11 busy   :  0:01:39  (  0.52%)
> dumper12 busy   :  0:00:01  (  0.01%)
>  0 dumpers busy :  0:02:43  (  0.85%)   0:  0:02:43  (100.00%)
>  1 dumper busy  :  3:39:13  ( 68.47%)   0:  3:39:13  (100.00%)
>  2 dumpers busy :  0:23:10  (  7.24%)   0:  0:23:10  (100.00%)
>  3 dumpers busy :  1:07:57  ( 21.22%)   0:  1:07:57  (100.00%)
>  4 dumpers busy :  0:02:09  (  0.67%)   0:  0:02:09  ( 99.99%)
>  5 dumpers busy :  0:01:07  (  0.35%)   0:  0:01:07  ( 99.98%)
>  6 dumpers busy :  0:00:03  (  0.02%)   0:  0:00:03  ( 99.59%)
>  7 dumpers busy :  0:00:43  (  0.22%)   0:  0:00:24  ( 56.35%)
> 5:  0:00:09  ( 22.36%)
> 4:  0:00:08  ( 18.89%)
> 1:  0:00:01  (  2.37%)
>  8 dumpers busy :  0:00:20  (  0.10%)   0:  0:00:19  ( 96.50%)
>  9 dumpers busy :  0:01:51  (  0.58%)   0:  0:01:51  ( 99.98%)
> 10 dumpers busy :  0:00:41  (  0.22%)   0:  0:00:37  ( 89.71%)
> 5:  0:00:02  (  7.13%)
> 4:  0:00:01  (  3.09%)
> 11 dumpers busy :  0:00:07  (  0.04%)   5:  0:00:07  ( 99.54%)
> 12 dumpers busy :  0:00:00  (  0.00%)
> 13 dumpers busy :  0:00:00  (  0.00%)
>
> I am going to give things another week or so and then try breaking up some of 
> the very large DLEs in the config.

RE: dumporder

Note on that - you want to maximize throughput, not maximize the number of 
running dumpers.

More dumpers moving data is usually good, but more isn't always better.

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Cuttler, Brian R (HEALTH)
Sent: Tuesday, November 6, 2018 11:11 AM
To: Chris Nighswonger ; amanda-users@amanda.org
Subject: RE: dumporder

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

Chris,

There is an amplot utility that I used to run a lot, it would show me what I 
was constrained on, often holding space, which if you are running a bunch of 
large dumps to start off with could constrain dumping later on.

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Nighswonger
Sent: Tuesday, November 6, 2018 11:02 AM
To: amanda-users@amanda.org
Subject: Re: dumporder

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

On Mon, Nov 5, 2018 at 1:31 PM Chris Nighswonger  
wrote:
>
> Is there any wisdom available on optimization of dumporder?
>

After looking over the feedback from Brian and Austin and reviewing the actual 
sizes of the DLEs, I ended up with this sort of thing:

inparallel 15
dumporder "STs"

Which resulted in a reduced time over what I have been seeing. Here are some 
stats from amstatus for this config. It looks like I could drop about half of 
the dumpers and still be fine. Any idea what causes the dumpers over the first 
five to be utilized less?

 dumper0 busy   :  5:13:42  ( 97.98%)
 dumper1 busy   :  1:12:09  ( 22.54%)
 dumper2 busy   :  0:40:30  ( 12.65%)
 dumper3 busy   :  0:33:44  ( 10.54%)
 dumper4 busy   :  0:03:47  (  1.19%)
 dumper5 busy   :  0:37:32  ( 11.73%)
 dumper6 busy   :  0:02:00  (  0.62%)
 dumper7 busy   :  0:00:57  (  0.30%)
 dumper8 busy   :  0:05:54  (  1.85%)
 dumper9 busy   :  0:04:38  (  1.45%)
dumper10 busy   :  0:00:16  (  0.08%)
dumper11 busy   :  0:01:39  (  0.52%)
dumper12 busy   :  0:00:01  (  0.01%)
 0 dumpers busy :  0:02:43  (  0.85%)   0:  0:02:43  (100.00%)
 1 dumper busy  :  3:39:13  ( 68.47%)   0:  3:39:13  (100.00%)
 2 dumpers busy :  0:23:10  (  7.24%)   0:  0:23:10  (100.00%)
 3 dumpers busy :  1:07:57  ( 21.22%)   0:  1:07:57  (100.00%)
 4 dumpers busy :  0:02:09  (  0.67%)   0:  0:02:09  ( 99.99%)
 5 dumpers busy :  0:01:07  (  0.35%)   0:  0:01:07  ( 99.98%)
 6 dumpers busy :  0:00:03  (  0.02%)   0:  0:00:03  ( 99.59%)
 7 dumpers busy :  0:00:43  (  0.22%)   0:  0:00:24  ( 56.35%)
5:  0:00:09  ( 22.36%)
4:  0:00:08  ( 18.89%)
1:  0:00:01  (  2.37%)
 8 dumpers busy :  0:00:20  (  0.10%)   0:  0:00:19  ( 96.50%)
 9 dumpers busy :  0:01:51  (  0.58%)   0:  0:01:51  ( 99.98%)
10 dumpers busy :  0:00:41  (  0.22%)   0:  0:00:37  ( 89.71%)
5:  0:00:02  (  7.13%)
4:  0:00:01  (  3.09%)
11 dumpers busy :  0:00:07  (  0.04%)   5:  0:00:07  ( 99.54%)
12 dumpers busy :  0:00:00  (  0.00%)
13 dumpers busy :  0:00:00  (  0.00%)

I am going to give things another week or so and then try breaking up some of 
the very large DLEs in the config.

RE: dumporder

Chris,

There is an amplot utility that I used to run a lot, it would show me what I 
was constrained on, often holding space, which if you are running a bunch of 
large dumps to start off with could constrain dumping later on.

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Nighswonger
Sent: Tuesday, November 6, 2018 11:02 AM
To: amanda-users@amanda.org
Subject: Re: dumporder

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

On Mon, Nov 5, 2018 at 1:31 PM Chris Nighswonger  
wrote:
>
> Is there any wisdom available on optimization of dumporder?
>

After looking over the feedback from Brian and Austin and reviewing the actual 
sizes of the DLEs, I ended up with this sort of thing:

inparallel 15
dumporder "STs"

Which resulted in a reduced time over what I have been seeing. Here are some 
stats from amstatus for this config. It looks like I could drop about half of 
the dumpers and still be fine. Any idea what causes the dumpers over the first 
five to be utilized less?

 dumper0 busy   :  5:13:42  ( 97.98%)
 dumper1 busy   :  1:12:09  ( 22.54%)
 dumper2 busy   :  0:40:30  ( 12.65%)
 dumper3 busy   :  0:33:44  ( 10.54%)
 dumper4 busy   :  0:03:47  (  1.19%)
 dumper5 busy   :  0:37:32  ( 11.73%)
 dumper6 busy   :  0:02:00  (  0.62%)
 dumper7 busy   :  0:00:57  (  0.30%)
 dumper8 busy   :  0:05:54  (  1.85%)
 dumper9 busy   :  0:04:38  (  1.45%)
dumper10 busy   :  0:00:16  (  0.08%)
dumper11 busy   :  0:01:39  (  0.52%)
dumper12 busy   :  0:00:01  (  0.01%)
 0 dumpers busy :  0:02:43  (  0.85%)   0:  0:02:43  (100.00%)
 1 dumper busy  :  3:39:13  ( 68.47%)   0:  3:39:13  (100.00%)
 2 dumpers busy :  0:23:10  (  7.24%)   0:  0:23:10  (100.00%)
 3 dumpers busy :  1:07:57  ( 21.22%)   0:  1:07:57  (100.00%)
 4 dumpers busy :  0:02:09  (  0.67%)   0:  0:02:09  ( 99.99%)
 5 dumpers busy :  0:01:07  (  0.35%)   0:  0:01:07  ( 99.98%)
 6 dumpers busy :  0:00:03  (  0.02%)   0:  0:00:03  ( 99.59%)
 7 dumpers busy :  0:00:43  (  0.22%)   0:  0:00:24  ( 56.35%)
5:  0:00:09  ( 22.36%)
4:  0:00:08  ( 18.89%)
1:  0:00:01  (  2.37%)
 8 dumpers busy :  0:00:20  (  0.10%)   0:  0:00:19  ( 96.50%)
 9 dumpers busy :  0:01:51  (  0.58%)   0:  0:01:51  ( 99.98%)
10 dumpers busy :  0:00:41  (  0.22%)   0:  0:00:37  ( 89.71%)
5:  0:00:02  (  7.13%)
4:  0:00:01  (  3.09%)
11 dumpers busy :  0:00:07  (  0.04%)   5:  0:00:07  ( 99.54%)
12 dumpers busy :  0:00:00  (  0.00%)
13 dumpers busy :  0:00:00  (  0.00%)

I am going to give things another week or so and then try breaking up some of 
the very large DLEs in the config.

RE: dumporder

2018-11-05 Thread Cuttler, Brian R (HEALTH)

Depends on how many dumpers you are using, I like of like TSTSTSts, or 
something like that. Also very much depends on the size/length of the relative 
dumps, but I do like to kick off some of the longest ones early.

Caveat – I haven’t done enough experimentation to know that what I’m doing is 
actually reasonable.

From: owner-amanda-us...@amanda.org  On Behalf 
Of Chris Nighswonger
Sent: Monday, November 5, 2018 1:31 PM
To: amanda-users 
Subject: dumporder


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

Is there any wisdom available on optimization of dumporder?

Kind regards,
Chris

Re: ipv4 vs ipv6

2018-05-14 Thread Cuttler, Brian R (HEALTH)

Ingo,

I’m sorry, I carelessly and stupidly copied the wrong set of lines from tcpdump.

The tcpdump was performed on the client, this shows a failure from the client 
to the server showing “TCP(6)”
Which I think is the problem. The server is IPv4 only, xinetd specified the 
flag as “IPv4” and the inbound traffic is IPv4.

Sorry for the earlier error.

Brian


11:29:40.183354 IP (tos 0xc0, ttl 64, id 11278, offset 0, flags [none], proto 
ICMP (1), length 80)
biowork2.health1.hcom.health.state.ny.us > flower.wadsworth.org: ICMP host 
biowork2.health1.hcom.health.state.ny.us unreachable - admin prohibited, length 
60
  IP (tos 0x0, ttl 64, id 9375, offset 0, flags [DF], proto TCP (6), length 
52)
flower.wadsworth.org.516 > biowork2.health1.hcom.health.state.ny.us.amanda: 
Flags [S], cksum 0xfc6b (correct), seq 2828866963, win 49640, options [mss 
1460,nop,wscale 0,nop,nop,sackOK], length 0


From: Ingo Schaefer <i...@ingo-schaefer.de>
Date: Monday, May 14, 2018 at 3:16 PM
To: "Cuttler, Brian R (HEALTH)" <brian.cutt...@health.ny.gov>, 
"amanda-users@amanda.org" <amanda-users@amanda.org>
Subject: AW: ipv4 vs ipv6


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

Hello Brian,

Your tcpdump Output is just ARP traffic for getting the ethernet address to the 
IP address.

And according to the length in tcpdump output I would say it is requesting the 
ethernet address to an IPv4 IP address.

So nothing wrong there.

Regards,
Ingo

Gesendet von meinem BlackBerry 10-Smartphone.
Von: Cuttler, Brian R (HEALTH)
Gesendet: Montag, 14. Mai 2018 17:44
An: amanda-users@amanda.org
Betreff: ipv4 vs ipv6



Hello Amanda users,

For some reason I’m not seeing much/any Amanda traffic, I did re-register with 
a new email address last month…

Installing Amanda-client on an ununtu system, when I run # amcheck from the 
server I’m seeing the following in tcpdump output.


flower.wadsworth.org.516 > biowork2.health1.hcom.health.state.ny.us.amanda: 
Flags [R], cksum 0x3d33 (correct), seq 2828866964, win 49640, length 0

11:29:44.054702 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
flower.wadsworth.org tell biowork2.health1.hcom.health.state.ny.us, length 28

11:29:44.054796 ARP, Ethernet (len 6), IPv4 (len 4), Reply flower.wadsworth.org 
is-at 00:14:4f:21:10:c2 (oui Unknown), length 46

That is, Amanda-client is being activated by IPv4 but responding using IPv6. I 
know that is mentioned in the mail archives and I have checked, re-installed 
xinetd on the client and verified flags are IPv4.


root@biowork2:/etc/ufw/applications.d# more /etc/xinetd.d/amanda

# default: on

#

# description: Amanda services for Amanda server and client.

#



service amanda

{

disable = no

flags   = IPv4

socket_type = dgram

protocol= udp

wait= no

user= amandabackup

group   = disk

groups  = yes

#server  = /usr/lib/amanda/amandad

server  = /usr/lib/x86_64-linux-gnu/amanda/amandad

server_args = -auth=bsdtcp amdump amindexd amidxtaped

}

Either I’m missing a step or I’m not chasing the correct problem.

Any help would be appreciated.

Brian

Brian Cuttler, Wadsworth Center/NYS Dept of Health
Albany, NY 12201

ipv4 vs ipv6

2018-05-14 Thread Cuttler, Brian R (HEALTH)


Hello Amanda users,

For some reason I’m not seeing much/any Amanda traffic, I did re-register with 
a new email address last month…

Installing Amanda-client on an ununtu system, when I run # amcheck from the 
server I’m seeing the following in tcpdump output.


flower.wadsworth.org.516 > biowork2.health1.hcom.health.state.ny.us.amanda: 
Flags [R], cksum 0x3d33 (correct), seq 2828866964, win 49640, length 0

11:29:44.054702 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
flower.wadsworth.org tell biowork2.health1.hcom.health.state.ny.us, length 28

11:29:44.054796 ARP, Ethernet (len 6), IPv4 (len 4), Reply flower.wadsworth.org 
is-at 00:14:4f:21:10:c2 (oui Unknown), length 46

That is, Amanda-client is being activated by IPv4 but responding using IPv6. I 
know that is mentioned in the mail archives and I have checked, re-installed 
xinetd on the client and verified flags are IPv4.


root@biowork2:/etc/ufw/applications.d# more /etc/xinetd.d/amanda

# default: on

#

# description: Amanda services for Amanda server and client.

#



service amanda

{

disable = no

flags   = IPv4

socket_type = dgram

protocol= udp

wait= no

user= amandabackup

group   = disk

groups  = yes

#server  = /usr/lib/amanda/amandad

server  = /usr/lib/x86_64-linux-gnu/amanda/amandad

server_args = -auth=bsdtcp amdump amindexd amidxtaped

}

Either I’m missing a step or I’m not chasing the correct problem.

Any help would be appreciated.

Brian

Brian Cuttler, Wadsworth Center/NYS Dept of Health
Albany, NY 12201

updated amanda client

2018-04-17 Thread Cuttler, Brian R (HEALTH)

We did a server update, which replaced old libraries, so we did an update to 
the Amanda install.

After updating (possibly incorrectly) the security.conf, we still have a 
getpeername error.

Not sure how to fix this, not seeing anything directly related in the archives.

Any help would be appreciated.

Thank you,
Brian



[root@netd /tmp/amanda/amandad]# more amandad.20180417104331.debug

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: pid 57255 ruid 210 euid 210 
version 3.3.9: start at Tue Apr 17 10:43:31 2018

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: 
security_getdriver(name=BSDTCP) returns 0x280d61a8

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: version 3.3.9

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: build: 
VERSION="Amanda-3.3.9"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:BUILT_DATE="Sun 
Apr 8 11:38:59 UTC 2018" BUILT_MACH=""

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:BUILT_REV="6535" 
BUILT_BRANCH="tags" CC="cc"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: paths: 
bindir="/usr/local/bin" sbindir="/usr/local/sbin"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
libexecdir="/usr/local/libexec/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
amlibexecdir="/usr/local/libexec/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
AMANDA_DBGDIR="/tmp/amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
RDEV_PREFIX="/dev/r" DUMP="/sbin/dump"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:XFSDUMP=UNDEF 
XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
SAMBA_CLIENT="/usr/bin/smbclient"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
GNUTAR="/usr/local/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
UNCOMPRESS_PATH="/usr/bin/gzip"  LPRCMD=UNDEF  MAILER=UNDEF

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
listed_incr_dir="/usr/local/var/amanda/gnutar-lists"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: defs:  
DEFAULT_SERVER="111i386-quarterly-job-16"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
DEFAULT_CONFIG="DailySet1"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
DEFAULT_TAPE_SERVER="111i386-quarterly-job-16"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
DEFAULT_TAPE_DEVICE="" NEED_STRSTR AMFLOCK_POSIX

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:AMFLOCK_FLOCK 
AMFLOCK_LOCKF AMFLOCK_LNLOCK AMANDA_DEBUG_DAYS=4

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:BSD_SECURITY 
USE_AMANDAHOSTS CLIENT_LOGIN="amanda"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:CHECK_USERID 
HAVE_GZIP COMPRESS_SUFFIX=".gz"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:
UNCOMPRESS_OPT="-dc"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad:CONFIGURE_ARGS=" 
'--libexecdir=/usr/local/libexec/amanda' '--without-amlibexecdir' 
'--with-amandahosts' '--with-fqdn' '--with-dump-honor-nodump' 
'--disable-glibtest' '--with-user=amanda' '--with-group=amanda' 
'--with-bsdtcp-security' '--with-bsdudp-security' '--with-ssh-security' 
'--disable-installperms' 
'--with-security-file=/usr/local/etc/amanda/security.conf' 
'--with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists' 
'--with-gnutar=/usr/local/bin/gtar' '--without-server' 
'--with-amandates=/usr/local/var/amanda/amandates' '--prefix=/usr/local' 
'--localstatedir=/var' '--mandir=/usr/local/man' '--disable-silent-rules' 
'--infodir=/usr/local/info/' '--build=i386-portbld-freebsd11.1' 
'build_alias=i386-portbld-freebsd11.1' 'CC=cc' 'CFLAGS=-O2 -pipe  
-fstack-protector -fno-strict-aliasing' 'LDFLAGS=  -fstack-protector' 'LIBS=' 
'CPPFLAGS=' 'CPP=cpp' 'PERL=/usr/local/bin/perl-amanda' 'PKG_CONFIG=pkgconf'"

Tue Apr 17 10:43:31 2018: thd-0x28a1ee00: amandad: getpeername returned: Socket 
is not connected

Dump failures

Good day all. I'm a fairly new amanda user, I used the 15 minute backup 
guide for my setup. During the first week my backups seemed to have gone 
off without a hitch as indicated by the backup reports. Now beginning on 
Monday I've been getting failed backup reports, as follows:


*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
epsilon.bleh.com /var/www lev 1 STRANGE


STATISTICS:
Total Full Incr.
  
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:02
Dump Time (hrs:min) 0:01 0:00 0:01
Output Size (meg) 79.9 0.0 79.9
Original Size (meg) 919.2 0.0 919.2
Avg Compressed Size (%) 8.7 -- 8.7 (level:#disks ...)
Filesystems Dumped 3 0 3 (1:3)
Avg Dump Rate (k/s) 1110.8 -- 1110.8

Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
Filesystems Taped 0 0 0

Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --


FAILED AND STRANGE DUMP DETAILS:

/-- epsilon.bleh.com /var/www lev 1 STRANGE
sendbackup: start [epsilon.bleh.com:/var/www level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./cacti/log/cacti.log: file changed as we read it
| Total bytes written: 946503680 (903MiB, 14MiB/s)
sendbackup: size 924320
sendbackup: end
\


DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s
-- - 
-

epsilon.bleh /etc/nagios 1 0 0 10.0 0:01 1.3 N/A N/A
epsilon.bleh /var/www 1 903 75 8.3 1:08 1132.5 N/A N/A
gamma.bleh.com /websites 1 17 5 28.1 0:05 979.1 N/A N/A

(brought to you by Amanda version 2.5.0p2)


I'm starting to think that I might have ran too many testing backups 
after the implementation and might have thrown the vtape usage off 
course if it's technically possible. I ran amflush daily as amanda and 
there were no results from it, the report I got said the same thing. I'm 
also concerned with the strange dump failure for cacti, due to its 
nature and the fact that it is configured to spread the load out evenly 
it is probably constantly writing data to the rra files, so I need to 
make sure I'm getting reliable dumps. Any additional insight in my 
paltry problems would help as I will be spending the day researching it 
on my end. Thanks!

Re: Dump failures


Jean-Louis Martineau wrote:

What is your tapecycle?
How many vtapes do you have?
What is the output of amcheck?

Jean-Louis

Mike R wrote:
Good day all. I'm a fairly new amanda user, I used the 15 minute 
backup guide for my setup. During the first week my backups seemed to 
have gone off without a hitch as indicated by the backup reports. Now 
beginning on Monday I've been getting failed backup reports, as follows:


*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
epsilon.bleh.com /var/www lev 1 STRANGE


STATISTICS:
Total Full Incr.
  
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:02
Dump Time (hrs:min) 0:01 0:00 0:01
Output Size (meg) 79.9 0.0 79.9
Original Size (meg) 919.2 0.0 919.2
Avg Compressed Size (%) 8.7 -- 8.7 (level:#disks ...)
Filesystems Dumped 3 0 3 (1:3)
Avg Dump Rate (k/s) 1110.8 -- 1110.8

Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
Filesystems Taped 0 0 0

Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --


FAILED AND STRANGE DUMP DETAILS:

/-- epsilon.bleh.com /var/www lev 1 STRANGE
sendbackup: start [epsilon.bleh.com:/var/www level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./cacti/log/cacti.log: file changed as we read it
| Total bytes written: 946503680 (903MiB, 14MiB/s)
sendbackup: size 924320
sendbackup: end
\


DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s
-- - 
-

epsilon.bleh /etc/nagios 1 0 0 10.0 0:01 1.3 N/A N/A
epsilon.bleh /var/www 1 903 75 8.3 1:08 1132.5 N/A N/A
gamma.bleh.com /websites 1 17 5 28.1 0:05 979.1 N/A N/A

(brought to you by Amanda version 2.5.0p2)


I'm starting to think that I might have ran too many testing backups 
after the implementation and might have thrown the vtape usage off 
course if it's technically possible. I ran amflush daily as amanda and 
there were no results from it, the report I got said the same thing. 
I'm also concerned with the strange dump failure for cacti, due to its 
nature and the fact that it is configured to spread the load out 
evenly it is probably constantly writing data to the rra files, so I 
need to make sure I'm getting reliable dumps. Any additional insight 
in my paltry problems would help as I will be spending the day 
researching it on my end. Thanks!





Thank you for your response.

dumpcycle 4 weeks
runspercycle 20
tapecycle 25 tapes

there are 25 slots in my vtape directory (I believe a slot = a tape 
correct?)


[r...@sigma daily]# su - amanda
-bash-3.2$ /usr/sbin/amflush daily
Scanning /opt/dumps...
  20091117010001: found Amanda directory.
  20091118010001: found Amanda directory.

Multiple Amanda directories, please pick one by letter:
  A. 20091117010001
  B. 20091118010001
Select directories to flush [A..B]: [ALL]

Today is: 20091118
Flushing dumps in 20091117010001, 20091118010001 using tape changer 
chg-disk.

Expecting a new tape.  (The last dumps were to tape daily-09)
Are you sure you want to do this [yN]? y
Running in background, you can log off now.
You'll get mail when amflush is finished.

RESULT

*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: a new tape.


Also I have posted my config here: http://pastebin.ca/1676675

Also, when setting up the system I followed these directions:

http://www.zmanda.com/quick-backup-setup.html

Thank you for your help!

Re: Dump failures


Jean-Louis Martineau wrote:

What's the complete output of: amcheck -s daily


Mike R wrote:

Jean-Louis Martineau wrote:

What is your tapecycle?
How many vtapes do you have?
What is the output of amcheck?

Jean-Louis

Mike R wrote:
Good day all. I'm a fairly new amanda user, I used the 15 minute 
backup guide for my setup. During the first week my backups seemed 
to have gone off without a hitch as indicated by the backup reports. 
Now beginning on Monday I've been getting failed backup reports, as 
follows:


*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
epsilon.bleh.com /var/www lev 1 STRANGE


STATISTICS:
Total Full Incr.
  
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:02
Dump Time (hrs:min) 0:01 0:00 0:01
Output Size (meg) 79.9 0.0 79.9
Original Size (meg) 919.2 0.0 919.2
Avg Compressed Size (%) 8.7 -- 8.7 (level:#disks ...)
Filesystems Dumped 3 0 3 (1:3)
Avg Dump Rate (k/s) 1110.8 -- 1110.8

Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
Filesystems Taped 0 0 0

Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --


FAILED AND STRANGE DUMP DETAILS:

/-- epsilon.bleh.com /var/www lev 1 STRANGE
sendbackup: start [epsilon.bleh.com:/var/www level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./cacti/log/cacti.log: file changed as we read it
| Total bytes written: 946503680 (903MiB, 14MiB/s)
sendbackup: size 924320
sendbackup: end
\


DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s
-- - 
-

epsilon.bleh /etc/nagios 1 0 0 10.0 0:01 1.3 N/A N/A
epsilon.bleh /var/www 1 903 75 8.3 1:08 1132.5 N/A N/A
gamma.bleh.com /websites 1 17 5 28.1 0:05 979.1 N/A N/A

(brought to you by Amanda version 2.5.0p2)


I'm starting to think that I might have ran too many testing backups 
after the implementation and might have thrown the vtape usage off 
course if it's technically possible. I ran amflush daily as amanda 
and there were no results from it, the report I got said the same 
thing. I'm also concerned with the strange dump failure for cacti, 
due to its nature and the fact that it is configured to spread the 
load out evenly it is probably constantly writing data to the rra 
files, so I need to make sure I'm getting reliable dumps. Any 
additional insight in my paltry problems would help as I will be 
spending the day researching it on my end. Thanks!





Thank you for your response.

dumpcycle 4 weeks
runspercycle 20
tapecycle 25 tapes

there are 25 slots in my vtape directory (I believe a slot = a tape 
correct?)


[r...@sigma daily]# su - amanda
-bash-3.2$ /usr/sbin/amflush daily
Scanning /opt/dumps...
  20091117010001: found Amanda directory.
  20091118010001: found Amanda directory.

Multiple Amanda directories, please pick one by letter:
  A. 20091117010001
  B. 20091118010001
Select directories to flush [A..B]: [ALL]

Today is: 20091118
Flushing dumps in 20091117010001, 20091118010001 using tape changer 
chg-disk.

Expecting a new tape.  (The last dumps were to tape daily-09)
Are you sure you want to do this [yN]? y
Running in background, you can log off now.
You'll get mail when amflush is finished.

RESULT

*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: a new tape.


Also I have posted my config here: http://pastebin.ca/1676675

Also, when setting up the system I followed these directions:

http://www.zmanda.com/quick-backup-setup.html

Thank you for your help!






[r...@sigma daily]# su - amanda
-bash-3.2$ /usr/sbin/amcheck -s daily
Amanda Tape Server Host Check
-
Holding disk /opt/dumps: 1246831 MB disk space available, using 1246731 MB
slot 5: read label `daily-05', date `20091110'
slot 6: read label `daily-06', date `2009'
slot 7: read label `daily-07', date `20091112'
slot 8: read label `daily-08', date `20091113'
slot 9: read label `daily-09', date `20091116'
slot 10: not an amanda tape (Read 0 bytes)
slot 11: not an amanda tape (Read 0 bytes)
slot 12: not an amanda tape (Read 0 bytes)
slot 13: not an amanda tape (Read 0 bytes)
slot 14: not an amanda tape (Read 0 bytes)
slot 15: not an amanda tape (Read 0 bytes)
slot 16: not an amanda tape (Read 0 bytes)
slot 17: not an amanda tape (Read 0 bytes)
slot 18: not an amanda tape (Read 0 bytes)
slot 19: not an amanda tape (Read 0 bytes)
slot 20: not an amanda tape (Read 0 bytes)
slot 21: not an amanda tape (Read 0 bytes)
slot 22: not an amanda tape (Read 0 bytes)
slot 23

Re: Dump failures


Jean-Louis Martineau wrote:

What are in those slots?
use 'amlabel' to label them.

Jean-Louis

slot 10: not an amanda tape (Read 0 bytes)
slot 11: not an amanda tape (Read 0 bytes)
slot 12: not an amanda tape (Read 0 bytes)
slot 13: not an amanda tape (Read 0 bytes)
slot 14: not an amanda tape (Read 0 bytes)
slot 15: not an amanda tape (Read 0 bytes)
slot 16: not an amanda tape (Read 0 bytes)
slot 17: not an amanda tape (Read 0 bytes)
slot 18: not an amanda tape (Read 0 bytes)
slot 19: not an amanda tape (Read 0 bytes)
slot 20: not an amanda tape (Read 0 bytes)
slot 21: not an amanda tape (Read 0 bytes)
slot 22: not an amanda tape (Read 0 bytes)
slot 23: not an amanda tape (Read 0 bytes)
slot 24: not an amanda tape (Read 0 bytes)
slot 25: not an amanda tape (Read 0 bytes)






Hmm, I'm noticing the command that I was instructed to use to label the 
tapes are as follows from http://www.zmanda.com/quick-backup-setup.html


7.Just as with physical tapes, the virtual tapes now need to be 
labeled. (Please note that the output below has been truncated.)


bash-3.00$ for ((i=1; $i=9;i++)); do amlabel DailySet1 DailySet1-0$i 
slot $i; done

changer: got exit: 0 str: 1 file://space/vtapes/DailySet1/slots
labeling tape in slot 1 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
rewinding, writing label DailySet1-01, checking label, done.
...
changer: got exit: 0 str: 9 file://space/vtapes/DailySet1/slots
labeling tape in slot 9 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
rewinding, writing label DailySet1-09, checking label, done.

-bash-3.00$ for ((i=10; $i=25;i++)); do amlabel DailySet1 DailySet1-$i 
slot $i; done

changer: got exit: 0 str: 10 file://space/vtapes/DailySet1/slots
labeling tape in slot 10 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
 rewinding, writing label DailySet1-10, checking label, done.
...
changer: got exit: 0 str: 25 file://space/vtapes/DailySet1/slots
labeling tape in slot 25 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
rewinding, writing label DailySet1-25, checking label, done.


/SNIP

SO I guess that was what was culpable of the initial problem but I think 
I might have screwed it up even worse. I noticed that the relabeling 
command that was provided in the how-to only had disk 1-9 set for the 
labeling and obviously, like a lemming, i simply copy and pasted it from 
the manual. Thinking I could fix the problem with the following command:


for ((i=10; $i=25;i++)); do /usr/sbin/amlabel daily daily-0$i slot $i; done

Now my amcheck is showing the following

Holding disk /opt/dumps: 1246830 MB disk space available, using 1246730 MB
slot 25: read label `daily-025', date `20091118'
slot 1: read label `daily-01', date `20091109'
slot 2: read label `daily-02', date `20091109'
slot 3: read label `daily-03', date `20091109'
slot 4: read label `daily-04', date `20091109'
slot 5: read label `daily-05', date `20091110'
slot 6: read label `daily-06', date `2009'
slot 7: read label `daily-07', date `20091112'
slot 8: read label `daily-08', date `20091113'
slot 9: read label `daily-09', date `20091116'
slot 10: read label `daily-010', date `X'

NOTE: skipping tape-writable test
Tape daily-010 label ok
Server check took 0.410 seconds

The flush worked but I think I screwed up the labeling of the vtapes in 
the process

Re: Dump failures


Mike R wrote:

Jean-Louis Martineau wrote:

What are in those slots?
use 'amlabel' to label them.

Jean-Louis

slot 10: not an amanda tape (Read 0 bytes)
slot 11: not an amanda tape (Read 0 bytes)
slot 12: not an amanda tape (Read 0 bytes)
slot 13: not an amanda tape (Read 0 bytes)
slot 14: not an amanda tape (Read 0 bytes)
slot 15: not an amanda tape (Read 0 bytes)
slot 16: not an amanda tape (Read 0 bytes)
slot 17: not an amanda tape (Read 0 bytes)
slot 18: not an amanda tape (Read 0 bytes)
slot 19: not an amanda tape (Read 0 bytes)
slot 20: not an amanda tape (Read 0 bytes)
slot 21: not an amanda tape (Read 0 bytes)
slot 22: not an amanda tape (Read 0 bytes)
slot 23: not an amanda tape (Read 0 bytes)
slot 24: not an amanda tape (Read 0 bytes)
slot 25: not an amanda tape (Read 0 bytes)






Hmm, I'm noticing the command that I was instructed to use to label the 
tapes are as follows from http://www.zmanda.com/quick-backup-setup.html


7.Just as with physical tapes, the virtual tapes now need to be 
labeled. (Please note that the output below has been truncated.)


bash-3.00$ for ((i=1; $i=9;i++)); do amlabel DailySet1 DailySet1-0$i 
slot $i; done

changer: got exit: 0 str: 1 file://space/vtapes/DailySet1/slots
labeling tape in slot 1 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
rewinding, writing label DailySet1-01, checking label, done.
...
changer: got exit: 0 str: 9 file://space/vtapes/DailySet1/slots
labeling tape in slot 9 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
rewinding, writing label DailySet1-09, checking label, done.

-bash-3.00$ for ((i=10; $i=25;i++)); do amlabel DailySet1 DailySet1-$i 
slot $i; done

changer: got exit: 0 str: 10 file://space/vtapes/DailySet1/slots
labeling tape in slot 10 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
 rewinding, writing label DailySet1-10, checking label, done.
...
changer: got exit: 0 str: 25 file://space/vtapes/DailySet1/slots
labeling tape in slot 25 (file://space/vtapes/DailySet1/slots):
rewinding, reading label, not an amanda tape (Read 0 bytes)
rewinding, writing label DailySet1-25, checking label, done.


/SNIP

SO I guess that was what was culpable of the initial problem but I think 
I might have screwed it up even worse. I noticed that the relabeling 
command that was provided in the how-to only had disk 1-9 set for the 
labeling and obviously, like a lemming, i simply copy and pasted it from 
the manual. Thinking I could fix the problem with the following command:


for ((i=10; $i=25;i++)); do /usr/sbin/amlabel daily daily-0$i slot $i; 
done


Now my amcheck is showing the following

Holding disk /opt/dumps: 1246830 MB disk space available, using 1246730 MB
slot 25: read label `daily-025', date `20091118'
slot 1: read label `daily-01', date `20091109'
slot 2: read label `daily-02', date `20091109'
slot 3: read label `daily-03', date `20091109'
slot 4: read label `daily-04', date `20091109'
slot 5: read label `daily-05', date `20091110'
slot 6: read label `daily-06', date `2009'
slot 7: read label `daily-07', date `20091112'
slot 8: read label `daily-08', date `20091113'
slot 9: read label `daily-09', date `20091116'
slot 10: read label `daily-010', date `X'

NOTE: skipping tape-writable test
Tape daily-010 label ok
Server check took 0.410 seconds

The flush worked but I think I screwed up the labeling of the vtapes in 
the process




So should I be concerned about this? Are the tapes alright based on the 
results of the relabeling and is incorrect labeling something I should 
be concerned about? Any suggestions on my /var/www dump that reports 
problems due to files changing?

Re: to disk to tape?

2007-05-11 Thread R Ransbottom

On Thu, May 10, 2007 at 07:08:02PM -0400, Gene Heskett wrote:
 On Thursday 10 May 2007, R Ransbottom wrote:

 The web docs suggest splitting up your vtape space

 Amanda handles vtape with the same intelligence it uses on a regular fixed 
 size tape.  Amanda will promote a full backup that isn't quite due in order 
 to help maintain an approximately equal tape usage every night.  In fact, for 
 those that come into the amanda arena, expecting to be able to do 
 incremental's monday-thursday, and a complete full on friday nights are in 
 for a somewhat rude shock because you have to bend over backwards, and write 
 scripts that beat her about the brow in order to achieve that hugely tape 
 wasting schedule.  That simply is not in the amanda view of how things work 
 from the original conception well over a decade ago.

I understood all of that; but I don't know how much intelligence Amanda
brings to physical tapes.  I have an small assortment of devices that can 
be dedicated to backups:  a few DVD-RWs, a few CD-RWs, and a pair of 20gig DATs,
Is it a good idea to have a set of tapes that encompass these various
devices?  Would Amanda burn a DVD one day and use the DAT when
the DVD is too small?

Thanks.

Be well,
rir

to disk to tape?

2007-05-10 Thread R Ransbottom

I have gotten so far as getting my first vtape written
and have lots of questions brewing.

The web docs suggest splitting up your vtape space
into vtapes of the same size.  Is this required; doe
Amanda intelligently handle vtapes of various sizes?

Be well,
rir

Hardware Compatibility Question...

2007-02-09 Thread A R

Hi All,

I have been tasked with updating my company's aging backup equipment. I am 
planning on purchasing a new server to run amanda along with a new robotic tape 
library with two LTO-3 drives.  I just want to make sure that the hardware I 
have selected will work with amanda and the Linux distribution that I have 
selected for this project.  I have about 10 TB of data to back up weekly.  Here 
is what I have in mind:

Server:
OS: Debian Linux
2U - 6 SATA HD slots
Pentium dual core processor (anyone have trouble with dual core?)
2GB RAM (too much? to little?)
2TB of HD spooling space, RAID0 w/four 500GB drives
120GB of operating system space on RAID1 with two 120GB drives
LSI Logic LSI22320 Ultra320 SCSI Dual Channel PCIx card

Loader:
Overland ARCvault24 w/ two LTO-3 tape drives

I guess the main questions I'm trying to figure out are... Is this server 
appropriate for the task at hand and is the tape equipment that I have selected 
compatible with amanda?  I tried calling Overland, but apparently they have 
never tested Amanda against the ARCvault, but it clearly works with the 
Powerloader without trouble.  I see no mention of the ARCvault anywhere on this 
group, so I figured I'd ask and see if anyone out there has had any experience 
with that particular loader. 

Thank you very much for your time.

~Andy   




 

Have a burning question?  
Go to www.Answers.yahoo.com and get answers from real people who know.

Different issue this time: Rate-limiting?

2006-12-04 Thread Ian R. Justman



Hi, listfolk.

I managed to get things working on limiting the files I want in a given 
set, but it hasn't solved my larger problem, the ethernet interface goes 
down during the course of the backup, but bounces back online.  From 
what I've been able to garner via Google, the machine, a Sun Ultra 5, 
appears to suffer a design defect that if the network interface is under 
heavy load, the interface will shut down, then shortly thereafter, it'll 
come back online.  Our NetSaint server will sometimes send (false) 
notifications showing that the server machine is down then back up.


Any ideas on how to get AMANDA to take it easy when sending data to the 
backup server?  I'd rather do it at the application layer if possible.


Thanks!

--Ian.

Re: Wildcards in disklist--revisited, only using exclusions:

2006-11-15 Thread Ian R. Justman


Ian R. Justman wrote:


Hello.

Tried using includes again, and still I'm having the same problem.  It's 
backing up nothing.  In fact, one item was still using the exclude 
method and it still backed up everything.


And for what it's worth, the version of GNU tar that's running on that 
machine shows the following when I do a gtar --version:


tar (GNU tar) 1.15.1

Anything I need to be aware of with this version of GNU tar?

Thanks.


Perhaps I should clarify this message:

I tried to use wildcards both in the exclude and include contexts in 
 disklist stanzas, both with and without trailing slashes.  I seem to 
be running into the same result each time.  If I use the include 
statement, nothing gets backed up with each stanza I use those wildcards 
in.  If I use excludes, everything gets backed up as many times as there 
are stanzas.


It doesn't seem to matter whether I have the trailing slash or not. 
What I'm curious about now is whether it's a GNU tar issue, in which 
case I should change which version of GNU tar I'm running, or if it's 
something I'm doing wrong.  It all seems to have something to do with 
what's in files referenced by the --files-from/--exclude-from gtar flags.


The players in this case are as follows:

Machine in question being backed up:

Sun Ultra 5 running Solaris 2.6 (SunOS 5.6)
AMANDA 2.5.0p2 which I built myself
GNU tar 1.15.1 from Sunfreeware.com

Machine which is holding the backups:

Dual Pentium II system running FreeBSD 4.8
AMANDA 2.5.0p2 using the amanda-server-2.5.0p2 port

The disklist on the FreeBSD machine has the following in the disklist 
pertinent to the affected host:


trillian /var/spool/PO/mailbox/0-99 /var/spool/PO/mailbox {
  user-tar
  include ./[0-9]/ ./[1-9][0-9]
} 1

[...]

trillian /var/spool/PO/mailbox/100-199 /var/spool/PO/mailbox {
  user-tar
  include ./1[0-9][0-9]
} 1

[...]

trillian /var/spool/PO/mailbox/200-299 /var/spool/PO/mailbox {
  user-tar
  include /.2[0-9][0-9]
} 1

[...]

trillian /var/spool/PO/mailbox/300-399 /var/spool/PO/mailbox {
  user-tar
   include ./3[0-9][0-9]
} 1

[...]

trillian /var/spool/PO/mailbox/400-499 /var/spool/PO/mailbox {
  user-tar
  include ./4[0-9][0-9]
} 1

[...]

trillian /var/spool/PO {
  user-tar
  exclude ./mailbox
} 1
trillian /etc user-tar

I removed the trailing slashes in the wildcarded lines per Jean-Louis' 
suggestion and it's still not working.  The only stanzas for this 
machine which actually work are the last two.  The first one is because 
it does not specify any wildcards in the exclude statement.  The 
second one is because I outright back up that entire directory hierarchy.


At this point, am I missing anything that might be of any help?

Is there anything I'm doing wrong at all or should I be using a 
different version of gtar since it seems to be the root of the problem, 
and if so, which version?


Thanks for any help on this matter.

--Ian.

Re: Wildcards in disklist--revisited, only using exclusions:

2006-11-14 Thread Ian R. Justman


Jean-Louis Martineau wrote:

Hi Ian,

Remove the trailling '/' from your include/exclude.

Jean-Louis


Hello.

Tried using includes again, and still I'm having the same problem.  It's 
backing up nothing.  In fact, one item was still using the exclude 
method and it still backed up everything.


And for what it's worth, the version of GNU tar that's running on that 
machine shows the following when I do a gtar --version:


tar (GNU tar) 1.15.1

Anything I need to be aware of with this version of GNU tar?

Thanks.

--Ian.

Wildcards in disklist--revisited, only using exclusions:

2006-11-09 Thread Ian R. Justman



Hi, all.

To summarize, I'm trying to back up a hashed spool of mailboxes on our 
mailserver at work.  The top directory of that spool has five hundred 
directories numbered 0-499 and I want to back them up a hundred at a 
time over the length of the backup process.


The first time I tried, this was according to a suggestion I found in 
the list archive.  The backup failed because it was looking for the 
wildcards as literal parts of the pathname and not actually globbing 
as it should.  For example, if I give ./[0-9]/,it would look for 
pathnames containing ./[0-9]/ actually in them, not expanding them as 
the wildcards I expressed them to be.  The net result is that the mail 
spool does not get backed up at all because it cannot find that 
pathname.  The pathnames are in a file passed to the machine in 
question, trillian, then referenced by gtar's --from-file.


This time, I tried using wildcards in exclude lines.  Here's my revised 
disk list entries (the actual directories to be backed up are commented 
out for reference's sake):


trillian /var/spool/PO/mailbox/0-99 /var/spool/PO/mailbox {
  user-tar
#  include ./[0-9]/ ./[1-9][0-9]/
  exclude ./[1-4][0-9][0-9]/
} 1

[...]

trillian /var/spool/PO/mailbox/100-199 /var/spool/PO/mailbox {
  user-tar
#  include ./1[0-9][0-9]/
  exclude ./[0-9]/ ./[1-9][0-9]/ ./[2-4][0-9][0-9]/
} 1

[...]

trillian /var/spool/PO/mailbox/200-299 /var/spool/PO/mailbox {
  user-tar
#  include /.2[0-9][0-9]/
  exclude ./[0-9]/ ./[1-9][0-9]/ ./[1,3-4][0-9][0-9]/
} 1

[...]

trillian /var/spool/PO/mailbox/300-399 /var/spool/PO/mailbox {
  user-tar
#   include ./3[0-9][0-9]/
  exclude ./[0-9]/ ./[1-9][0-9]/ ./[1-2,4][0-9][0-9]/
} 1

[...]

trillian /var/spool/PO/mailbox/400-499 /var/spool/PO/mailbox {
  user-tar
#  include ./4[0-9][0-9]/
  exclude ./[0-9]/ ./[1-9][0-9]/ ./[1-3][0-9][0-9]/
} 1

This time, the directories to be excluded end up in the same type of 
file as above, but are fed via --exclude-from rather than --from-file. 
I looked at the /tmp/amanda/sendbackup.*.exclude files and the 
exclusions are getting in as they should.


However, they're not being PARSED as they should be.

For each stanza, it backs up ALL five hundred directories.  For the 
entire disklist file, it would back up the hierarchy a complete five 
times.  Apparently because it can't find the specified pathname 
component(s) I'm specifying.  And I suspect that again, you cannot have 
wildcards in the --exclude-from file like you can't from the --from-file 
file.  I can't help thinking it's a gtar bug and I can't be sure whether 
if it's a gtar bug or if it's that way by design, i.e. you can only 
explicitly give directories or files while forbidding globbing.  gtar is 
taking those two files and interpreting them literally, not performing 
any globbing as specified.


What am I doing wrong here?  All I want to do in each case is limit it 
to a certain one hundred directories and I'd like to use 
well-established wildcards/globbing to enumerate them.


Thanks for any help.

--Ian.

Re: amdump issues involving wildcards--quoted wildcards appear to be sent to, and thus being interpreted literally by, gtar

2006-11-07 Thread Ian R. Justman


Mitch Collinsworth wrote:


On Thu, 2 Nov 2006, Ian R. Justman wrote:

My conjecture of what's happening is that the gtar command is being 
run with quotes around the items in the include statement in my 
disklist file, causing gtar to not perform any globbing and, instead, 
look for any pathname with actual brackets and globbing characters in it.


Have a look in /tmp/amanda/sendbackup.xxx.debug.  That should show you
what the command line arguments being used look like.

-Mitch


Sorry for taking so long to reply since things've been pretty hectic 
around here.


Anyway, what originally started this was this thread on 
marc.theaimsgroup.com:


http://marc.theaimsgroup.com/?l=amanda-usersm=108514231301508w=2
and the thread that ensues

Here's what I get when I look at the appropriate files affecting one of 
those backups:


# less runtar.20061107001110.debug
runtar: debug 1 pid 7776 ruid 30 euid 0: start at Tue Nov  7 00:11:10 2006
gtar: version 2.5.0p2
running: /usr/local/bin/gtar: gtar --create --file - --directory 
/var/spool/PO/mailbox --one-file-system 
--listed-incremental/usr/local/var/amanda/gnutar-lists 
/trillian_var_spool_PO_mailbox_0-99_1.new --sparse --ignore-failed-read 
--totals --exclude-from 
/tmp/amanda/sendbackup._var_spool_PO_mailbox_0-99.20061107001110 
.exclude --files-from 
/tmp/amanda/sendbackup._var_spool_PO_mailbox_0-99.20061107001110.include

runtar: pid 7776 finish time Tue Nov  7 00:11:11 2006

# less 
/tmp/amanda/sendbackup._var_spool_PO_mailbox_0-99.20061107001110.include

./[0-9]/
./[1-9][0-9]/

This begs the question:  Can a file as designated by --files-from 
contain wildcards?  Apparently, they cannot.  Apparently GNU Tar is 
looking for directories with literal names beginning with ./[0-9]/ and 
./[0-9][0-9]/ rather than globbing them to ./0/, ./1/, [...], ./9/, 
./10/, ./11/, [...], ./98/, and ./99/


At first glance, GNU tar's documentation appears to say I cannot.

What it all boils down to is this looks less and less like an AMANDA 
problem and more and more like a GNU tar problem.


Not having wildcard/globbing like this is not very helpful if I have a 
large number of directories here (in this case, 500 of them) and 
enumerating them 100 individually at a time is an extreme nuisance.  If 
anything else, I'd love to know if I'm doing something wrong.  Though if 
worst comes to worse, I have some ideas based on the distribution copy 
of disklist of what I can do in lieu of any wildcards should I be 
required to, yet keep my disklist looking reasonably neat and easy to 
manage.


Thanks in advance for any tips.

--Ian.

amdump issues involving wildcards--quoted wildcards appear to be sent to, and thus being interpreted literally by, gtar

2006-11-02 Thread Ian R. Justman



Hi, all.

I have an issue which is starting to vex me.  I'm backing up a mail 
spool on a Sun UltraSPARC 5 which is getting rather big.  Plus I have to 
do it in such a way that causes the interface not to get upset.  If I 
stuff a lot of data through it, it'll shut the interface down, but it'll 
come back up.  To combat this, I'm doing small sections of it throughout 
the backup session.  Apparently, the issue I'm observing is a known 
issue of UltraSPARC 5 boxen.


The mail spool uses a hashed directory setup with directories numbered 
from 0 through 499 with directories within, much like Maildirs, but not. 
 Here's a snippet from my disklist:


trillian /var/spool/PO/mailbox/0-99 /var/spool/PO/mailbox {
  user-tar
  include ./[0-9]/ ./[1-9][0-9]/
} 1
.
.
.
trillian /var/spool/PO/mailbox/100-199 /var/spool/PO/mailbox {
  user-tar
  include ./1[0-9][0-9]/
} 1
.
.
.
trillian /var/spool/PO/mailbox/100-199 /var/spool/PO/mailbox {
  user-tar
  include ./2[0-9][0-9]/
} 1
.
.
.
(etc)

Near as I can figure, the commands being sent to the other machine 
(using oversimplified flags for the sake of brevity) is something to the 
effect of:


cd /var/spool/PO/mailbox
tar cvf - ./1[0-9][0-9]/

If I hand-run the tar command without the quotes, it'll work just fine. 
 However the moment I use these configuration stanzas, it won't work. 
Advice comes partly from the example disklist, partly from a few posts 
to the mailing list about wildcards.


The rest of the backups work fine, including one other for this host 
which specifically excludes the mailbox hierarchy.


My conjecture of what's happening is that the gtar command is being run 
with quotes around the items in the include statement in my disklist 
file, causing gtar to not perform any globbing and, instead, look for 
any pathname with actual brackets and globbing characters in it.


Any suggestions?

Thanks!

--Ian.

RE: tapestatus file growing huge

2006-07-21 Thread Scott R. Burns

This is an optional file you can enable in the chg-scsi changer. I have a
similar changer (HPDAT24x6). The file records SCSI command interaction. Here
is my file:

number_configs  1
eject   0   # Tapedrives need an eject command
sleep   30  # Seconds to wait until the tape gets ready
cleanmax50  # How many times could a cleaning tape get used

changeridentC1553A
changerdev  /dev/ch0
debug   9:0
#
# Next comes the data for drive 0
#
config  0
drivenum0
dev /dev/nrst0  # the device that is used for the tapedrive
0
scsitapedev /dev/rst0
startuse0   # The slots associated with the drive 0
enduse  4   #
statfile/usr/pkg/etc/amanda/st0-slot  # The file where the actual
slot i
s stored
cleancart   5   # the slot where the cleaningcartridge for drive 0
is lo
cated
cleanfile   /usr/pkg/etc/amanda/st0-clean # The file where the cleanings
are
 recorded
usagecount  /usr/pkg/etc/amanda/totaltime
tapestatus  /usr/pkg/etc/amanda/st0-status

# This is the end


Here is a sample of an output for our tape ncti08 on Jul 23, 2005

 20050723  ncti08 
Write Error Counters Page
Total Errors Corrected = 1
Total Times E. Processed   = 103
Total Bytes Processed  = 4294967249
Total Unrecoverable Errors = 0

Read Error Counters Page
Total Errors Corrected = 0
Total Times E. Processed   = 0
Total Bytes Processed  = 6
Total Unrecoverable Errors = 0

Scott...

Scott Burns
Plantwatch Inc. / NETCON Technologies Inc.
Voice: +1.519.652.0401 x229
Fax: +1.519.652.9275
E-Mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
Web: www.plantwatch.com / www.netcontech.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Gene Heskett
Sent: Friday, July 21, 2006 10:58 AM
To: amanda-users@amanda.org
Subject: Re: tapestatus file growing huge

On Friday 21 July 2006 10:34, Jon LaBadie wrote:
On Fri, Jul 21, 2006 at 10:46:51AM +0100, Rodrigo Ventura wrote:
 Today the server disk went out of space because the tapestatus file
 grew over several GiGs. It seems to be related with upgrading amanda
 to 2.5.0p2. The contents are lines like tape status =  Any
 clues?

I'm unfamiliar with a tapestatus file.
Which file is that?

I'm just as puzzled, I now have the latest 2.5.1p1-20060719 installed 
and I have no such file either.

Would the OP please supply the full path to this file?

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

Loss of tape labels

2006-07-04 Thread Scott R. Burns









I had a condition for the last few days where a DLE was too
large to fit on a tape. The system thought it was OK and tried to write it as
my tapetype settings was slightly larger than the actual tape. I am not sure if
this is a coincidence or not but the next few days the tapes that it had tried
to write too and given up due to size were reported as not an Amanda tape
by amcheck. We are going to test this but does anyone know if this is a known
issue where the amlabel gets trashed in this case? I had thought the
tapes were dying for the last little while but now I am wondering if this may
be the case.



I am on NetBSD/i386 2.0.2/Amanda 2.4.4p4 with a HP DAT 24x6
changer.



Thanks



Scott



Scott Burns

Plantwatch Inc. / NETCON Technologies Inc.

Voice: +1.519.652.0401 x229

Fax: +1.519.652.9275

E-Mail: [EMAIL PROTECTED]
/ [EMAIL PROTECTED]

Web: www.plantwatch.com
/ www.netcontech.com

Failure when DLE is slightly larger than the tape

2006-07-02 Thread Scott R. Burns









It would appear I have my tape size set to be slightly
larger than the tape really is (HP DAT24x6 changer). The issue I have now is a
dump failed for a large DLE and is sitting on disk, this dump is just slightly
larger than the tape so most likely putting in another tape and flushing it is
just going to fail again.



If I lower the tape size in the config, cleanup some files
on that DLE things will work again but that DLE dump will be stuck on the
holding disk forever.



What is the proper way to deal with this? Correct
my Amanda config problems obviously, cleanup the disk so it will fit on one
tape, cleanup that DLE files from the holding disk, mark that DLE as requiring
a full dump next run and just let Amanda run normally?



I am waiting for a bit before I jump onto the tape splitting
version as this is my production server for the entire company and I am a
little shy of something so new.



Thanks in advance.



Scott



Scott Burns

Plantwatch Inc. / NETCON Technologies Inc.

Voice: +1.519.652.0401 x229

Fax: +1.519.652.9275

E-Mail: [EMAIL PROTECTED]
/ [EMAIL PROTECTED]

Web: www.plantwatch.com
/ www.netcontech.com

Change to mount point names in disklist

2006-05-08 Thread Scott R. Burns









I am considering changing my current setup from device names
to mount point names. I have a Daily config and a Monthly
config which forces full dumps which are never overwritten and stored offsite.
My question is WRT index/restore issues if I change my disklist now. I have 25
tapes in my Daily rotation, will I have problems restoring if I change from
say: sd0f to /data4. Does this come into play in
index lookup for amrecover?



Thanks

Scott



Scott Burns

NETCON Technologies Inc.

Voice: +1.519.652.0401

Fax: +1.519.652.9275

E-Mail: [EMAIL PROTECTED]

Web: www.netcontech.com

Re: mail problems

2006-03-19 Thread Chrisopher R Davis

I believe you can sort this out by editing an alias file somewhere - I'm 
actually nowhere near a linux box to verify where it is - /etc/alias?  
But there's a file out there that redirects mail to those system 
accounts to root - you can remove the amanda entry from this file and be 
good to go.  I changed this about a year ago so my memory is a little fuzzy.




Chris

Jon LaBadie wrote:


On Sun, Mar 19, 2006 at 01:45:39AM -0500, Gene Heskett wrote:
 


On Sunday 19 March 2006 01:22, Jon LaBadie wrote:
   


Not directly amanda related, but affecting amanda.

On two linux systems, SuSE 10.0 and FC4,
I'm trying to use the distro's version of amanda.

However I can't get mail delivered to the amanda user.
It is not specific to amanda, seems to be any system user
(i.e. a user with uid below 500 or some other number).
Instead, mail addressed to amanda/lp/mysql/... are all
delivered to root's mailbox.

Gotta be a config param I've not found.
 


Obvious Q Jon, who is the crontab entry mailing it to.
   



amanda.

It is not the amanda config, nor an actual amanda problem.
Any mail to any system user, from inside, from outside,
mailed by software like amanda, or mailed using the mail
program directly from the command line, ends up in roots
mailbox.

Interestingly it is on both the SuSE 10.0 and the FC4 boxes
and one, I think, runs postfix while the other runs sendmail.

f.y.i.The reboot of the client did indeed fix the problem without me having to change any of the timeout settings. I only refrained from doing this because my timeouts were more than high enough already and as the backup size hadn't suddenly changed, the backups should have worked with their current settings.Would love to know what the reboot does to sort the problem. Prior to the reboot I had killed off all the amanda owned processes but still the backups failed. The reboot suggestion from Gene sorted it however.Thank you for your input Gene and amanda-users!Shabs.Gene Heskett [EMAIL PROTECTED] wrote: On Friday 27 January 2006 06:05, shoaib r wrote:I've had backups working for over 2 mon!
ths
now. A system reboot started daily failures on the remote machine: Report says: == FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR host1NAK : amandad busy host01 /export RESULTS MISSING etc... amandad.debug says: amandad: time 30.009: dgram_recv: timeout after 30 secondsamandad: error receiving message: timeoutamandad: time 30.010: error receiving message: timeout No changes made to amanda.conf or any other configuration. The tape server is backing its filesystems up sucessfully. However the one and only remote server is not. Does anyone have any ideas? Thank youISTR I've had that happen once or twice, not recently, because a zombie was left on the client, possibly due to a timeout error. A reboot of the client should fix that. And you !
might add
a bit to the timeout values in your amanda.conf just for insurance. An additional 25% should be enough, if indeed that was the cause.-- Cheers, GenePeople having trouble with vz bouncing email to me should add the word'online' between the 'verizon', and the dot which bypasses vz'sstupid bounce rules. I do use spamassassin too. :-)Yahoo.com and AOL/TW attorneys please note, additions to the abovemessage by Gene Heskett are:Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Yahoo! Photos NEW, now offering a quality print service from just 8p a photo.

Re: amandad busy

2006-01-30 Thread shoaib r

sorry I should have mentioned, I'm using Solaris 9.My etimeout is set to -8000 (which has been ok for months) but i still think its way to much. I didnt change it as this is the error i'm getting now:  FAILURE AND STRANGE DUMP SUMMARY:  planner: ERROR Estimate timeout from host01  host01 /u01 lev 0 FAILED [disk /u01, all estimate timed out]  host01 /opt lev 0 FAILED [disk /opt, all estimate timed out]  host01 /var lev 0 FAILED [disk /var, all estimate timed out]  host01 /usr lev 0 FAILED [disk /usr, all estimate timed out]  host01 / lev 0 FAILED [disk /, all estimate timed out]  host01 /export lev 0 FAILED 20060124 [too many dumper retry]Will schedule a reboot in and see how it goes.The above error would indicate to me that the etimeout isn't high eno!
 ugh but
 its already at 8000secs (133mins)!! Dont understand that.Thanks for input so far guys.shabs  Salvatore Enrico Indiogine [EMAIL PROTECTED] wrote:  2006/1/27, shoaib r <[EMAIL PROTECTED]>: I've had backups working for over 2 months now. A system reboot started daily failures on the remote machine: The tape server is backing its filesystems up sucessfully. However the one and only remote server is not. Does anyone have any ideas? Thank youJust a shot in the dark, but a reboot will usually boot the newlyinstalled kernel if you have something like yum update set onautomatic.Check e.g. /var/log/messages, uname -r, dmesgI am assuming you run Linux and use yum. Simila!
 r things
 could havehappened with automatic apt-get upgrade.--Enrico IndiogineParasol LaboratoryTexas AM University[EMAIL PROTECTED][EMAIL PROTECTED]979-845-3937  
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

amandad busy

2006-01-27 Thread shoaib r

I've had backups working for over 2 months now.A system reboot started daily failures on the remote machine:Report says:  ==FAILURE AND STRANGE DUMP SUMMARY:  planner: ERROR host1NAK : amandad busy  host01 /export RESULTS MISSING  etc...amandad.debug says:    amandad: time 30.009: dgram_recv: timeout after 30 secondsamandad: error receiving message: timeoutamandad: time 30.010: error receiving message: timeoutNo changes made to amanda.conf or any other configuration.The tape server is backing its filesystems up sucessfully. However the one and only remote server is not.Does anyone have any ideas?Thank
 you
		Yahoo! Photos  NEW, now offering a quality print service from just 8p a photo.

RE: Problems with chg-scsi

2006-01-25 Thread Scott R. Burns

From what I remember chio.

Scott...

Scott Burns
NETCON Technologies Inc.
Voice: +1.519.652.0401
Fax: +1.519.652.9275
E-Mail: [EMAIL PROTECTED]
Web: www.netcontech.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Ian Turner
Sent: Wednesday, January 25, 2006 4:37 PM
To: Eric Schnoebelen
Cc: amanda-users@amanda.org
Subject: Re: Problems with chg-scsi

Eric,

On Wednesday 25 January 2006 02:22 pm, Eric Schnoebelen wrote:
   NetBSD and FreeBSD do have very functional changer management
 command line tools and system call interfaces, and both the
 command line and system call interfaces are very stable.

MTX works on all the BSDs, as far as I know. I guess you need to use the
ports 
system to install it? What is the native changer management tool?

Thanks,

--Ian
-- 
Zmanda: Open Source Data Protection and Archiving.
http://www.zmanda.com

RE: Problems with chg-scsi

2006-01-19 Thread Scott R. Burns

NetBSD/i386 is my platform (think of it as FreeBSD only better :-)).
/dev/rst0 is the raw device, the n prefix version is the no-rewind version.

I am sure the author can explain the changerident field more. I think is
kind of like a quirk table where it maps the expected result from each scsi
command used by chg-scsi.

Scott...

Scott Burns
NETCON Technologies Inc.
Voice: +1.519.652.0401
Fax: +1.519.652.9275
E-Mail: [EMAIL PROTECTED]
Web: www.netcontech.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Gene Heskett
Sent: Thursday, January 19, 2006 12:06 AM
To: amanda-users@amanda.org
Subject: Re: Problems with chg-scsi

On Wednesday 18 January 2006 23:03, Scott R. Burns wrote:
Works fine for me (NetBSD/i386 2.0.2, HP DAT24x6 on some Adaptec card
 in a Compaq ML370. Key for reliable operation for me was:

1) the changerident field being set to something. For my environment
C1553A is as close as I could get to my changer from the list of
 known devices.

Changerident?  That name doesn't grep in the 
amanda-23.4.5p120051218/example dir where a sample chg-scsi.conf lives.

And I wonder how much diff there is between the 6 slot C1553 and the 4 
slot seagate 4586np.  Other than the seagate stacks the tapes 
vertically and from pix, it looks like the hp handles them horizontally 
somehow.

However, in the docs dir, there is a .txt file, chgscsi.txt, that does 
describe this, unforch this file was apparently added after I'd given 
up, its dated: May 13  2005 chgscsi.txt.  By then I'd bought a 200GB 
pata drive and partitioned it for /var, swap  180GB as /amandatapes.  
I have 10GB of swap  haven't ever used more than 10 megs of it.  
Gigabyte of ram though.

2) the definition of both dev (/dev/nrst0) and scsitapedev
 (/dev/rst0).

Thats not a linux device name.  Solaris?

Other than that is works fine now, never dumps and I have no rewind
 issues with both of these device lines setup.

$ 0.02 Canadian :-)

Scott..

Scott Burns
NETCON Technologies Inc.
Voice: +1.519.652.0401
Fax: +1.519.652.9275
E-Mail: [EMAIL PROTECTED]
Web: www.netcontech.com

-Original Message-

[...]

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

RE: Problems with chg-scsi

2006-01-19 Thread Scott R. Burns

As with others this is just what I started with back then. I don't really
remember what version of Amanda that was back then but somehow I went in
that direction and have not had reason to look elsewhere.

Scott...

Scott Burns
NETCON Technologies Inc.
Voice: +1.519.652.0401
Fax: +1.519.652.9275
E-Mail: [EMAIL PROTECTED]
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jon LaBadie
Sent: Thursday, January 19, 2006 10:53 AM
To: amanda-users@amanda.org
Subject: Re: Problems with chg-scsi

On Thu, Jan 19, 2006 at 06:58:11AM -0500, Scott R. Burns wrote:
 NetBSD/i386 is my platform (think of it as FreeBSD only better :-)).

Just an observation;
nearly all who responded to Ian query saying they still use chg-scsi
and who mentioned their OS, indicated it was one of the BSD variants.

Is there something about the BSD environment that encourages
the use of chg-scsi vs. the other changer scripts?
Maybe no or difficult port of mtx?

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

RE: Problems with chg-scsi

2006-01-18 Thread Scott R. Burns

Works fine for me (NetBSD/i386 2.0.2, HP DAT24x6 on some Adaptec card in a
Compaq ML370. Key for reliable operation for me was:

1) the changerident field being set to something. For my environment
C1553A is as close as I could get to my changer from the list of known
devices. 

2) the definition of both dev (/dev/nrst0) and scsitapedev (/dev/rst0).

Other than that is works fine now, never dumps and I have no rewind issues
with both of these device lines setup.

$ 0.02 Canadian :-)

Scott..

Scott Burns
NETCON Technologies Inc.
Voice: +1.519.652.0401
Fax: +1.519.652.9275
E-Mail: [EMAIL PROTECTED]
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Gene Heskett
Sent: Wednesday, January 18, 2006 6:50 PM
To: amanda-users@amanda.org
Subject: Re: Problems with chg-scsi

On Wednesday 18 January 2006 13:47, Ian Turner wrote:
Hello,

Is anyone out there using chg-scsi instead of chg-mtx or chg-zd-mtx?
 If so, can you tell me why? I've been testing it quite a bit, but
 there seem to be a large number of problems -- the code is ridden
 with bad device references, fixed buffer overflows, and the like. I'm
 more than happy to fix it, but only if someone can articulate why we
 have chg-scsi at all.

I did use it for a while, but like you, I had problems, primarily 
control, as in it did not seem to ever issue a rewind, which meant if 
you did am amcheck, and it advanced the changer and found the tape, it 
left the tape sitting after the header, so when amdump went to check, 
it wasn't an amanda tape since neither one was able to rewind the tape, 
but only run the changer mechanism.  And of course, when amcheck did 
it, and found the tape, then amdump couldn't, and amcheck couldn't 
because in recycling the magazine, it never made it back to the right 
slot unless amcheck was run twice.  The end result was that I had to 
wrap the amcheck script in a shell script that rewound the tape before 
the amcheck, and again after it so amdump could find the right label.  
Now, if amdump did find the right label, it would rewind it and rewrite 
it with the new date.  That part worked fine.  But neither one could do 
an initial rewind at the time I was fighting with it.

So yes, chg-scsi has issues.  I'm now using the FILE: device, works 
great.

As for buffer issues, I didn't see anything in about 4-5 years that 
would make me think there was a problem in that area.  Long enough to 
wear out 5 of those Seagate 4586n DDS2 changers.

Let me know.

Cheers,

--Ian

My $0.02 Ian...

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

RE: newbie Q: DUMP: The ENTIRE dump is aborted.

2005-11-19 Thread Scott R. Burns

Looks like you are trying to tell dump to dump a subdirectory rather than a
volume/partition ?

I assume /home/mysql is not a mount point for a drive but a sub-dir on a
paritiion.

Change your disklist entry (DLE) to be the name of a drive.

On my machine an example of one drive would be:

In my disklist:

ncti103 sd2g comp-user 2


From my Unix df command:

/dev/sd2g 8258270   562030   7283326 7%/data9

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Yan Seiner
Sent: Saturday, November 19, 2005 12:22 PM
To: amanda-users@amanda.org
Subject: newbie Q: DUMP: The ENTIRE dump is aborted.


I've set up amanda as best as I know how

amcheck reports everything is OK.  Permissions, etc. all seem OK.

But when I try to run amdump I get:

FAIL dumper localhost /home/mysql 20051119 0 [/sbin/dump returned 1]
 sendbackup: start [localhost:/home/mysql level 0]
 sendbackup: info BACKUP=/sbin/dump
 sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/sbin/restore -f... -
 sendbackup: info COMPRESS_SUFFIX=.gz
 sendbackup: info end
 |   DUMP: You can't update the dumpdates file when dumping a
subdirectory
 |   DUMP: The ENTIRE dump is aborted.
 sendbackup: error [/sbin/dump returned 1]
INFO taper tape SeinerHome02 kb 0 fm 0 [OK]
FINISH driver date 20051119 time 81.367

Any ideas on where to start?  I don't want to clutter the list with
long files So where do I need to look?  Or what should I provide
to the list so you can advise?

Thanks,

--Yan

RE: amanda over wireless network

2005-11-17 Thread Scott R. Burns

Could it be that Amanda has a maximum retries that was exceeded ?

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Paul Yeatman
Sent: Thursday, November 17, 2005 9:03 PM
To: Paul Bijnens
Cc: Amanda user's group
Subject: Re: amanda over wireless network


H, I set the server side etimeout to 2600s.  Still get (from an
amstatus)

pjmac:/0 planner: [Estimate timeout from pjmac]

and the amanda report now gives this (mind you, this client
is the only entry in this test config)

Estimate Time (hrs:min)2:10

2 hours and 10 minutes!

The message from amandad on the client is virtually the same

snip
amandad: time 0.038: running service
/usr/local/libexec/amanda/2.4.5p1/sendsize
amandad: time 1244.905: sending REP packet:

Amanda 2.4 REP HANDLE 000-30F3BC2A5500 SEQ 1132261451
OPTIONS features=feff9ffe7f;
/ 0 SIZE 17648480


amandad: time 1254.905: dgram_recv: timeout after 10 seconds
amandad: time 1254.905: waiting for ack: timeout, retrying
amandad: time 1264.906: dgram_recv: timeout after 10 seconds
amandad: time 1264.906: waiting for ack: timeout, retrying
amandad: time 1274.906: dgram_recv: timeout after 10 seconds
amandad: time 1274.906: waiting for ack: timeout, retrying
amandad: time 1284.906: dgram_recv: timeout after 10 seconds
amandad: time 1284.906: waiting for ack: timeout, retrying
amandad: time 1294.907: dgram_recv: timeout after 10 seconds
amandad: time 1294.907: waiting for ack: timeout, giving up!
amandad: time 1294.907: pid 29584 finish time Thu Nov 17 14:52:41 2005

Shouldn't the approx. 1255s required to get the estimate fall clearly
within the 2600s allowed?

Not sure where things are going wrong now

Paul
--
Paul Yeatman   (858) 534-9896[EMAIL PROTECTED]
 ==
 ==Proudly brought to you by Mutt==
 ==

RE: 2.4.5: dumping directly to tape failure: no retry?

2005-11-01 Thread Scott R. Burns

I observed this same issue with:

2.4.4p4
NetBSD/i386
HP DAT24*6

My last DLE was  than the remaining tape, but would fit entirely on the
next empty tape in the changer as it was the only remaining DLE. It was
reported as retrying but never did. In this case my holding space was  the
compressed size of this DLE but it would fit onto tape.

Ultimately I found enough drive space to reserve for a holding space  than
this DLE size but I would like to gain that back if this issue could be
fixed.

Search the archives for detailed reporting on the problem by me.

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jean-Francois Malouin
Sent: Tuesday, November 01, 2005 11:37 AM
To: AMANDA users
Subject: 2.4.5: dumping directly to tape failure: no retry?


Hi,

[ BTW, I noticed a thread addressing this question yesterday or so
  but I don't want to hijack it... ]

I just upgraded to 2.4.5 and noticed that if a DLE is sent directly to
tape it is not retried if it hits EOT (a full dump that won't fit in
the holdding space). I have runtapes = 10 and never run into this
problem before, or at least with the previous version I was running,
2.4.4p3-20040805. OS: irix-6.5.x with an STK L80 library and LTO1
Ultriums.

Here is some excerpts form the amdump logfile. In the following look
at yorick:/data/mril/mril2. It's the one that failed.

To me it looks like it was being dumped directly to tape label
stk_40-conf2-28, it hit EOT and was not retried. amanda
just went on with the other DLEs in her schedule.


amdump logfile:


taper: slot 11: date 20050925 label stk_40-conf2-28 (exact label match)
taper: read label `stk_40-conf2-28' date `20050925'
taper: wrote label `stk_40-conf2-28' date `20051101'
driver: result time 98.468 from taper: TAPER-OK

[...]

FAILED QUEUE: empty
DONE QUEUE:

[...]

 10: yorick /data/mril/mril2

[...]

ANALYZING ESTIMATES...

[...]

GENERATING SCHEDULE:

DUMP yorick feff9ffe7f /data/mril/mril2 20051101 2 0
1970:1:1:0:0:0 958730408789 3 2005:10:28:10:51:39 95873040 281565

[ a full dump of ~92GB is scheduled ]


[...]

driver: send-cmd time 15078.866 to dumper0: FILE-DUMP 01-00029
/holddisk/conf2/stk_40/20051101031508/shadow._.1 shadow
feff9ffe0f / NODEVICE 1 2005:10:30:12:33:6 2097056 DUMP 265696
|;bsd-auth;index;

[...]

driver: finished-cmd time 15241.837 taper wrote shadow:/
driver: dumping yorick:/data/mril/mril2 directly to tape
driver: send-cmd time 15241.838 to taper: PORT-WRITE 00-00031 yorick
feff9ffe7f /data/mril/mril2 0 20051101
driver: result time 15241.842 from taper: PORT 16614
driver: send-cmd time 15241.842 to dumper0: PORT-DUMP 00-00031 16614
yorick feff9ffe7f /data/mril/mril2 NODEVICE 0 1970:1:1:0:0:0 DUMP
|;bsd-auth;index;

   [ Here EOT is encountered, next tape is loaded
 and then 3 DLEs are dumped to tape but not the one
that hit EOT ]

taper: writing end marker. [stk_40-conf2-28 ERR kb 103821568 fm 16]
changer: opening pipe to: /opt/amanda/amanda2/libexec/chg-zd-mtx -info
changer: got exit: 0 str: 11 10 1 1
changer_query: changer return was 10 1 1
changer_query: searchable = 1
changer_find: looking for stk_40-conf2-29 changer is searchable = 1
changer_search: stk_40-conf2-29
changer: opening pipe to: /opt/amanda/amanda2/libexec/chg-zd-mtx
-search stk_40-conf2-29
changer: got exit: 0 str: 12 /hw/tape/tps12d2nrnsv
taper: slot 12: date 20050926 label stk_40-conf2-29 (exact label match)
taper: read label `stk_40-conf2-29' date `20050926'
taper: wrote label `stk_40-conf2-29' date `20051101'
dumper: driver: result time 23806.848 from dumper0: FAILED 00-00031
[data write : Broken pipe]
driver: result time 23806.849 from taper: TRY-AGAIN 00-00031 [writing
file: No space left on device]
driver: error time 23806.888 serial gen mismatch
driver: dumping yorick:/data/noel/noel1 directly to tape
driver: send-cmd time 23806.888 to taper: PORT-WRITE 00-00032 yorick
feff9ffe7f /data/noel/noel1 1 20051101

[...]

driver: result time 23806.891 from taper: PORT 16475
driver: send-cmd time 23806.891 to dumper0: PORT-DUMP 00-00032 16475
yorick feff9ffe7f /data/noel/noel1 NODEVICE 1 2005:10:30:15:52:23 DUMP
|;bsd-auth;index;
driver: state time 23806.891 free kps: 1023791 space: 52428800 taper:
writing idle-dumpers: 9 qlen tapeq: 0 runq: 2 roomq: 0 wakeup: 86400
driver-idle: not-idle
driver: interface-state time 23806.891 if : free 1022391 if LE0: free
400 if LOCAL: free 1000
driver: hdisk-state time 23806.891 hdisk 0: free 52428800 dumpers 0
dumper: time 8564.873taper: s: streamtream_accept: connection from
_client127.0.0.1: connected to .16650127.0.0.1taper: t.16475
ry_socksize: dumper: receive stream_clientbuffer size is : our side is
32768

Re: Backup of client failing

2005-10-21 Thread shoaib r

Apologies for not keeping my last posting on the list (unintentional - I just hit reply rather than selecting reply-all from the drop-down list)

The client does not have a disklist file and I'm pretty sure its not a server for anything else.

Your 2nd assumption of a stuck amandad process on the client was correct. I've killed the amanda processes and tried again except this time I've included only one filesystem from the tape server and one from the client server - that completed fine. No problems. But when I include all the filesystems on the client machine, I get the same error all overagain:

--
--
amandad: time 4199.964: received other packet, NAKing it addr: peer 51.108.14.49 dup 51.108.14.49, port: peer 824 dup 841amandad: time 4199.964: sending nack:Amanda 2.4 NAK HANDLE 000-000344C0 SEQ 1129883130ERROR amandad busy
amandad: time 4215.041: got packet:Amanda 2.4 REQ HANDLE 000-00034708 SEQ 1129883131SECURITY USER amandaSERVICE sendbackupOPTIONS features=feff9ffe7f;hostname=ptpreq01;GNUTAR /export 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;no-record;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;
amandad: time 4215.041: received other packet, NAKing it addr: peer 51.108.14.49 dup 51.108.14.49, port: peer 824 dup 841amandad: time 4215.041: sending nack:Amanda 2.4 NAK HANDLE 000-00034708 SEQ 1129883131ERROR amandad busy--
--Paul Bijnens [EMAIL PROTECTED] wrote:
Please keep the discussion on the list, there may be otherpeople with tips of the solution, and it may help otherpeople with the same problem.shoaib r wrote: The debug logs gave me this as the only error:  /tmp/amanda/amandad.20051021010122.debug  Amanda 2.4 NAK HANDLE 000-000344C0 SEQ 1129852801 ERROR amandad busy  amandad: time 3615.713: got packet:  Amanda 2.4 REQ HANDLE 000-00034708 SEQ 1129852802 The "amandad busy" means that the server did sent a request whilethe client was still busy with processing another request.That could happen when you have more than one amandaserver andthe amandad on the client is already busy with another server.!
 Make
 sure a client has all his disklist entries in only one server.Or you could have a stuck amandad client, still handling some requestfrom the previous test. Kill all the amanda processes on the client,and try again.-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, ** F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... ** ... "Are you sure?" ... YES ... Phew ... I'm out
 
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

Backup of client failing

2005-10-20 Thread shoaib r

Hi

Does anyone have an ideas why my client box doesn't get backed up? amcheck come back fine, but the backups do not complete.

the tapeserver communicates ok with the client via inetd.

If I specify just the filesystems on the tapeserver, the backups complete sucessfully within 7 minutes.

But when I include the client server (cleint01) filesystems, things time out. I've played around with all the timeout settings in amanda.conf with no progress at all.

planner: FAILED client01 /u01 20051018 0 [disk /u01, all estimate timed out]planner: FAILED client01 /opt 20051018 0 [disk /opt, all estimate timed out]planner: FAILED client01 /var 20051018 0 [disk /var, all estimate timed out]planner: FAILED client01 /usr 20051018 0 [disk /usr, all estimate timed out]planner: FAILED client01 / 20051018 0 [disk /, all estimate timed out]
Any ideas?

Thanks

Shabs
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

RE: Need help diagnosing hostname problems

2005-10-19 Thread Scott R. Burns

I presume you have already checked items such as a host file entry that
maybe you made when first installing/debugging Amanda ?

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of KEVIN ZEMBOWER
Sent: Wednesday, October 19, 2005 11:57 AM
To: amanda-users@amanda.org
Subject: Need help diagnosing hostname problems


I had an amanda setup that worked fine until two weeks ago, when I had to
change the network addresses of all my hosts and move them into a separate
DMZ, using a different, new DNS. Now, I'm not able to get one host to
respond, and the output is puzzling:

[EMAIL PROTECTED]:/tmp/amanda-dbg$ amcheck -c DBackup

Amanda Backup Client Hosts Check

ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed]
Client check: 2 hosts checked in 0.702 seconds, 1 problem found

(brought to you by Amanda 2.4.4p3)
[EMAIL PROTECTED]:/tmp/amanda-dbg$ dig www.jhuccp.org

;  DiG 9.2.4  www.jhuccp.org
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 41347
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.jhuccp.org.IN  A

;; ANSWER SECTION:
www.jhuccp.org. 3600IN  A   10.253.192.204

;; Query time: 2 msec
;; SERVER: 10.23.2.10#53(10.23.2.10)
;; WHEN: Wed Oct 19 11:36:58 2005
;; MSG SIZE  rcvd: 48

[EMAIL PROTECTED]:/tmp/amanda-dbg$

I'm puzzled by the response in amcheck, ERROR: www.jhuccp.org: [addr
10.253.192.205: hostname lookup failed] compared to the correct response in
dig, ;; ANSWER SECTION: www.jhuccp.org. 3600IN  A
10.253.192.204. The IP address that amcheck responded with, 10.253.192.205,
is the IP for the tapehost itself, cn2. Is amcheck complaining that
10.253.192.204 doesn't resolve to www.jhuccp.org (it shouldn't;
www.jhuccp.org is 205), or is it complaining that 10.253.192.205 doesn't
resolve correctly to the name of the tapehost?

I tried to check the debug files generated in /tmp/amanda-dbg/. There were
four files generated from 'amcheck -c DBackup', but none of them seemed to
contain any information regarding this failure.

Thanks for any suggestions or advice in working on this problem.

-Kevin Zembower



-
E. Kevin Zembower
Internet Systems Group manager
Johns Hopkins University
Bloomberg School of Public Health
Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD  21202
410-659-6139

Re: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?

2005-10-06 Thread shoaib r

Yes this was the debug file resulting from the "start manually and wait30 seconds" . As yet I have no debug file produced from inetd.Paul Bijnens [EMAIL PROTECTED] wrote:
shoaib r wrote: This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT  server (bkpclient):  amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct 5  13:08:50 2005 amandad: version 2.4.5... amandad: time 30.005: dgram_recv: timeout after 30 secondsWas this the debug file resulting from the "start manually and wait30 seconds" test? Or was it the result of amandad invoked by inetd?-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, ** quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, cl!
 ose, bye,
 /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... ** ... "Are you sure?" ... YES ... Phew ... I'm out 
		Yahoo! Messenger 
 NEW - crystal clear PC to PC 
calling worldwide with voicemail

Re: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?

2005-10-06 Thread shoaib r

Fair enough, I'll check again.

f.y.i I ran a snoop from the client (bkpclient) whilst running an "amcheck -c daily" on the server (tapesvr) and this is what I got:

tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)Paul Bijnens [EMAIL PROTECTED] wrote:
shoaib r wrote: Yes this was the debug file resulting from the "start manually and wait 30 seconds" . As yet I have no debug file produced from inetd.Then I would conclude that you have a problem with your inetd configuration.-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, ** F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, !
 ...
 ** ... "Are you sure?" ... YES ... Phew ... I'm out 
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

RE: amrecover questions ?

2005-10-06 Thread Scott R. Burns

try adding localhost root to the file.

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 11:55 AM
To: amanda-users@amanda.org
Subject: amrecover questions ?



Hi Listserv,
I am trying to get amrecover to work.  I keep getting this message :

 # amrecover daily
AMRECOVER Version 2.4.4p2. Contacting server on localhost ...
220 lnxdev AMANDA index server (2.4.4p2) ready.
500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED]
amandahostsauth failed
***1159*** [EMAIL PROTECTED]:/etc/amanda/daily] *** uid=0 ***

Here is what my .amandahosts looks like :

#  cat  .amandahosts
lnxdev.ncci.com root

Here is what my .rhosts looks like :

#  cat  .rhosts
+

Any ideas ??

TIA

Bernie Wu
[EMAIL PROTECTED]




The information contained in this e-mail message is intended only for 
the personal and confidential use of the recipient(s) named above. This 
message may be an attorney-client communication and/or work product and 
as such is privileged and confidential. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it 
to the intended recipient, you are hereby notified that you have 
received this document in error and that any review, dissemination, 
distribution, or copying of this message is strictly prohibited. If you 
have received this communication in error, please notify us immediately 
by e-mail, and delete the original message.

RE: amadmin questions #1

2005-10-06 Thread Scott R. Burns

Are you looking for a file to restore ? If so amrecover is the way to go. It
will find the file for you. You may even specify a date to look for (ie.
before this date, in case you know it was corrupted say 2 days ago you can
ask it for the version from 3 days ago).

If you specifically want the list of all files on those tapes then if you
have indexing turned on you could look under each DLE entry in the index
directory and cat the unzipped listings kepted there for the dates the
backup used those tapes. That is the data amrecover uses anyway and it is
much easier as it find the right tape (you specify which date you want to
restore from).

I don't know of any other way.

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 3:54 PM
To: amanda-users@amanda.org
Subject: amadmin questions #1



Hi Listserv,
How can I see what files are in tape dump600 or dump200 ?  The output of my
amadmin follows:


[EMAIL PROTECTED] amadmin daily info

Current info for lnxdev.ncci.com /caplan/unixdata/accdata:
  Stats: dump rates (kps), Full:  8879.0,  -1.0,  -1.0
Incremental:  10471.0,  -1.0,  -1.0
  compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
  Dumps: lev datestmp  tape file   origK   compK secs
  0  20051005  dump600 1  408440  408440   46
  1  20051006  dump200 1   83770   837708
[EMAIL PROTECTED]


The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message
is not the intended recipient or an agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
by e-mail, and delete the original message.

WARNING: hostxxx: selfcheck request timed out. Host down?

Hi folks

I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet.

Am I missing something?

My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the disklist file.

I've checked inetd.conf and /etc/services according to advice and they seem fine:

Any help would be appreciated.

Thanks

Shabs
		Yahoo! Messenger 
 NEW - crystal clear PC to PC 
calling worldwide with voicemail

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

Thanks for the responses so far folks

Ok. I have 2 hosts tapesrv and bkpclient The error message is:

+ running on tapesvr +
$ amcheck -c daily
Amanda Backup Client Hosts CheckWARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?Client check: 2 hosts checked in 30.072 seconds, 1 problem found
(brought to you by Amanda 2.4.5)

There is no firewall between tapesvr and bkpclient.

When I start amandad from the bkpclient as user amanda it does indeed sit there for 30secs and then terminates.

I get nothing useful or conspicuous lets say from /tmp/amanda/*.debug

My .amandahosts file goes like this on "tapesvr" :

tapesvramandatapesvrrootbkpclient.b.c.uk amandabkpclient.b.c.uk root
I'm not sure about the commands in solaris of how to check if the connections are comming in.

Thx
Shabs
Paul Bijnens [EMAIL PROTECTED] wrote:
shoaib r wrote: I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet. Am I missing something?We miss the exact error messages. :-) My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the disklist file. I've checked inetd.conf and /etc/services according to advice and they seem fine:Is the amandad client started and gives an error or isn't it startedat all?What happens when you start the amandad client from a command line?It should sit there for 30 seconds and than terminate. Or do you getany error message there.Verify that the amandad program is indeed started by inetd.<BR!
>Any
output in /tmp/amanda/*.debug on the client?-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, ** F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... ** ... "Are you sure?" ... YES ... Phew ... I'm out
How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo!
Photos

RE: Tapelist issue only using 3 tape out of a tapecycle of 10.

2005-10-05 Thread Scott R. Burns

Could your tapecycle be smaller now than when you labelled the tapes? I am
not sure exactly the effect this would have but if it were reduced it may
ignore the other tapes 

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Chuck Amadi Systems
Administrator
Sent: Wednesday, October 05, 2005 5:07 AM
To: Amanda List
Cc: Chuck
Subject: Tapelist issue only using 3 tape out of a tapecycle of 10.


Hi I have noticed that the backup schedule as changed somehow and is
only using DailySet108 to DailySet110 (3 tapes) is there away to check
and force it to use the next tape after DailySet110 which should be
DailySet101. I did relabel a faulty tape recently.

finaceserver:/etc/amanda/DailySet1 # less tapelist
20051005 DailySet109 reuse
20050930 DailySet108 reuse
20050929 DailySet107 reuse
20050922 DailySet106 reuse
20050916 DailySet105 reuse
20050915 DailySet104 reuse
20050909 DailySet103 reuse
20050908 DailySet102 reuse
20050907 DailySet101 reuse
20050906 DailySet110 reuse


I did Replace a tape DailySet107 which Amanda reports a tape to be
faulty, the label could not be read on the tape, or the data could not
be saved on the tape. It is time to replace the tape.

In order to keep the set of tapes consistant, the new tape should have
the same label as the old tape. So I used the label DailySet107.

 1. Connect on Amanda server, first as root, then change to the user
amanda, with the command su.
 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line
containing the label,(DailySet107) Usually the line is the last
one of the file.
 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the
same way. Usually the line is the one before the last.
 4. prepare a new tape and write the label on it with the command:
amlabel normal DailySet107.
 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that
the line with the label is back, but it is now at the top of the
file, and the number at the begining is 0. Just move that line
to the bottom of the file. This worked So I assumed.

Cheers

--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

Just in case it makes any difference to what you know already, the backups for tapesrv are working just fine.

I've checked inetd.conf, services, .amandahosts etc and their permissions and ownerships against a completey separate configuration that works. All seems to be fine:

--- On tapesrv ---
/etc/services:
amanda 10080/udp # Amanda backupamandaidx 10082/tcp # Amanda backup index
/etc/inetd.conf:
amandaidx stream tcp nowait amanda /usr/local/amanda/libexec/amindexd \amindexdamidxtape stream tcp nowait amanda /usr/local/amanda/libexec/amidxtaped \amidxtapedamanda dgram udp wait amanda /usr/local/amanda/libexec/amandad \amandad
Does the interface column in disklist make any difference?

Have I missed anything out?

Appreciate you help so far.

ShabsAlexander Jolk [EMAIL PROTECTED] wrote:
shoaib r wrote: Thanks for the responses so far folks  Ok. I have 2 hosts tapesrv and bkpclient The error message is:   + running on tapesvr + $ amcheck -c daily Amanda Backup Client Hosts Check  WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5) Actually, it is tapesrv.bc.uk that's timing out and not bkpclient. Forget about bkpclient, it seems to work just fine; look into /tmp/amanda/ on tapesrv, that's where your problem is. And yes, even local backup (from a disk on tapesrv to a tape on tapesrv) go over a net connection, so check inetd, xinetd, services etc. *on
 tapesrv*.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
		Yahoo! Messenger 
 NEW - crystal clear PC to PC 
calling worldwide with voicemail

Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?

Note: forwarded message attached.
		How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! 
Photos---BeginMessage---
This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient):

amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct 5 13:08:50 2005amandad: version 2.4.5amandad: build: VERSION="Amanda-2.4.5"amandad: BUILT_DATE="Wed Aug 17 17:42:57 BST 2005"amandad: BUILT_MACH="SunOS dptsdsda02 5.9 Generic_117171-02 sun4u sparc SUNW,Sun-Fire-480R"amandad: CC="gcc"amandad: CONFIGURE_COMMAND="'./configure' '--prefix=/usr/local/amanda' '--with-user=amanda' '--with-group=amanda'"amandad: paths: bindir="/usr/local/amanda/bin"amandad: sbindir="/usr/local/amanda/sbin"amandad: libexecdir="/usr/local/amanda/libexec"amandad: mandir="/usr/local/amanda/man"
 AMANDA_TMPDIR="/tmp/amanda"amandad: AMANDA_DBGDIR="/tmp/amanda"amandad: CONFIG_DIR="/usr/local/amanda/etc/amanda"amandad: DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"amandad: DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore"amandad: VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEFamandad: VXDUMP=UNDEF VXRESTORE=UNDEFamandad: SAMBA_CLIENT="/usr/local/samba/bin/smbclient"amandad: GNUTAR="/usr/local/bin/tar" COMPRESS_PATH="/usr/bin/gzip"amandad: UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp"amandad:
 MAILER="/usr/bin/mailx"amandad: listed_incr_dir="/usr/local/amanda/var/amanda/gnutar-lists"amandad: defs: DEFAULT_SERVER="dptsdsda02" DEFAULT_CONFIG="DailySet1"amandad: DEFAULT_TAPE_SERVER="dptsdsda02"amandad: DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHMamandad: LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODEamandad: AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTSamandad: CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIPamandad: COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"amandad: COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"amandad: time 30.005: dgram_recv: timeout after 30 secondsamand!
 ad: error
 receiving message: timeoutamandad: time 30.006: error receiving message: timeoutamandad: time 30.006: pid 7021 finish time Wed Oct 5 13:09:20 2005Alexander Jolk [EMAIL PROTECTED] wrote:
shoaib r wrote: sorry Alexander  My mistake. As I'm working on a gov't project, I had to change the  hostnames for aliases for the amanda mailing list. I basically vut and  paste the wrong alias.  Here is the actual error mesage:  $ amcheck -c daily Amanda Backup Client Hosts Check  WARNING: bkupclient.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5)OK, so let's get back to the mailing list. Please do look into /tmp/amanda/ on the failing client, and send any information therein to the list.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.---End Message---

Re: WARNING: hostxxx: selfcheck request timed out. Host down?