Amanda Backup

[Kaushal Shriyan]

Hi AlL

Can I prirotise the backup in Amanda, I mean first HOST A, Then HOST B
and next on words or can I specify in the disklist file

Please advice 

Thanks in Advance

-- 
Regards,

Kaushal Shriyan
Technical Engineer
Red Hat India Pvt. Ltd.
1st Floor,'C'Wing,
Fortune2000,
Bandra Kurla Complex,
Bandra(East),
Mumbai 400051.
Maharashtra
India
Tel: +91-22-3987
Fax: +91-22-39878899
Cell   : +91-9820367783
E-mail : [EMAIL PROTECTED]



signature.asc
Description: This is a digitally signed message part

Amanda Backup

[Kaushal Shriyan]

In My office amanda does a full backup regularly for 3 days but why is
it not switching over to a incremental backup after the full backup is
run for first time

any help

-- 

Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318
Cell : +91-9820367783

Amanda Backup

[Kaushal Shriyan]

Hi All

Wanted to know about amanda tape viz to check what will be the next run
for a particular hostname, diskname. 

How do i check that

Any Help

-- 

Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318

Amanda Backup

[Kaushal Shriyan]

I have following queries in the amanda Backup

1)
[EMAIL PROTECTED] amanda]$ amadmin DailySet1 balance
new disk indus.mumbai.redhat.com://account.mumbai.redhat.com/C ignored.

Why do i get this 


2) I get this  whwn i run amadmin DailySet1 due


Overdue 12619 days:
indus.mumbai.redhat.com://account.mumbai.redhat.com/D
Overdue 12619 days: illusions.mumbai.redhat.com:/home/amit

Can anyone clarify this on the above point


-- 

Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318
Cell : +91-9820367783



signature.asc
Description: This is a digitally signed message part

amanda Backup

[Kaushal Shriyan]

Hi Paul

I am facing some issues with the backup process of the amanda
it writes data to the tape. lets say it has written to the tape when i
am restoring from the tape to the hard disk
a folder abc, now inside the abc folder there is no contents why is it
happening  but when i check the orginal folder the contents are there.

please help as it a matter of concern for me 

Would appreciate if you can reply me fast, I have also attached my
amanda.conf file for your ready reference

please advice


-- 

Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318
Cell : +91-9820367783



signature.asc
Description: This is a digitally signed message part

amanda backup

[Kaushal Shriyan]

Hi

Lets say i have /home/test folder being backed up by amanda 
as i have mentioned in the disklist file. Now if i have to
exclude some files(not to backup )from the /home/test folder how do i do
that.

please help


-- 
Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318
Cell : +91-9820367783

Amanda Backup

[Kaushal Shriyan]

Hi All

Wanted to know about the time schedule of backups. Can i take backup
during the working hours or is it compulsory to take in the night when
there is no I/O operation.

-- 
Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318

Amanda backup

[Mangala Gunadasa]

I have been getting the following error messages on the amanda backup log file.

FAILURE AND STRANGE DUMP SUMMARY:
  hadg   /var lev 0 FAILED [missing result for /var in hadg response]
  hadg   /dev/dsk/c0t3d0s0 lev 0 FAILED [missing result for /dev/dsk/c0t3d0s0 in 
hadg response]
  hadg   /opt lev 0 FAILED [missing result for /opt in hadg response]
  etest  /dg1/qa1 lev 0 STRANGE
  etest  /dg1/qa2 lev 0 FAILED [nak error:unexpected ack packet]
  etest  /dg lev 0 FAILED [nak error:unexpected ack packet]
  eprod  /opt lev 0 FAILED [nak error:unexpected ack packet]
  etest  /dg/dghome lev 0 STRANGE

If any body can help me to identify the above problems, I'd be much appreciated.

Thanks,

Mangala.

Re: Amanda Backup

[Paul Bijnens]

Kaushal Shriyan wrote:
Can I prirotise the backup in Amanda, I mean first HOST A, Then HOST B
and next on words or can I specify in the disklist file
Not completely, but you have some control.
First there is the "priority" directive in the dumptype definition.
Here "priority" is not time related (common misconception), but,
when amanda has no tape to write, it falls back to degraded mode,
doing incrementals to holdingdisk.  If there is not enough space,
amanda chooses which to drop according to the priority
("priority low" is dropped first).
If you want time-based priority, you can add the "starttime" directive
to some dumptypes. The starttime indicates that backups will not start
until after this time of the day.  YOu can defined two dumptypes,
one without starttime (i.e. backups will start as soon as amdump 
starts), and one with a delayed starttime (then hopefully all the others
have already started). If you run amdump at e.g. 00:05 past midnight,
you can define these two dumptypes:

define dumptype normal {
global
}
define dumptype delayed {
normal
starttime 200   # start at 2:00 am
}
You'll have to find out experimentally at what time it is safe to
start with the lower priority DLE's.  You'll have to understand
the relations between number of "inparallel" dumpers, and several
constraints that inhibit amanda to start another dump, like spindle,
"maxdumps" in the dumptype, bandwith and holdingdisk space.
"amplot" is your friend here, together with an careful examination
of the dump.X file.
That said, many people (like me) would like to start the longest
dumps first, not because they are more important, but that they are
finished by the time people start to work again, and so that they can
be put first on tape (avoiding restarting such a large dump because it
bumped into end of tape -- longest are probably among the largest too).
For that simple case, no need to add starttime, just change the default
dumporder:
inparallel 8# or anything you  like
dumporder ""# as many T's as you have "inparallel"
taperalgo largestfit# why isn't this the default?
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amanda Backup

[Jon LaBadie]

On Wed, Mar 02, 2005 at 10:58:08AM +0100, Paul Bijnens wrote:
> Kaushal Shriyan wrote:
> >
> >Can I prirotise the backup in Amanda, I mean first HOST A, Then HOST B
> >and next on words or can I specify in the disklist file
> 
> Not completely, but you have some control.
> 
...
> 
> If you want time-based priority, you can add the "starttime" directive
> to some dumptypes. The starttime indicates that backups will not start
> until after this time of the day.  YOu can defined two dumptypes,
> one without starttime (i.e. backups will start as soon as amdump 
> starts), and one with a delayed starttime (then hopefully all the others
> have already started). If you run amdump at e.g. 00:05 past midnight,
> you can define these two dumptypes:
> 
> define dumptype normal {
> global
> }
> define dumptype delayed {
> normal
> starttime 200 # start at 2:00 am
> }
> 

I've not played with 'starttime' but reading your note got me thinking
that having absolute times as arguments could be an administrative pain
if the amdump was run at varying times.

Is there any way of specifying a relative value?  Say "starttime +30"
so it would begin no less than 30 min after the first dump starts.
I guess it couldn't be after amdump starts because the estimate and
planning stage varies in length.


OK Jon, follow your own, oft given, advice, RTFM  

Well there certainly is nothing in the man page describing relative
values, so I suspect I answered my own query.  Perhaps it would be
a good "Wish List" item.

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

Re: Amanda Backup

[Gene Heskett]

On Wednesday 02 March 2005 11:03, Jon LaBadie wrote:
>On Wed, Mar 02, 2005 at 10:58:08AM +0100, Paul Bijnens wrote:
>> Kaushal Shriyan wrote:
>> >Can I prirotise the backup in Amanda, I mean first HOST A, Then
>> > HOST B and next on words or can I specify in the disklist file
>>
>> Not completely, but you have some control.
>
>...
>
>> If you want time-based priority, you can add the "starttime"
>> directive to some dumptypes. The starttime indicates that backups
>> will not start until after this time of the day.  YOu can defined
>> two dumptypes, one without starttime (i.e. backups will start as
>> soon as amdump starts), and one with a delayed starttime (then
>> hopefully all the others have already started). If you run amdump
>> at e.g. 00:05 past midnight, you can define these two dumptypes:
>>
>> define dumptype normal {
>> global
>> }
>> define dumptype delayed {
>> normal
>> starttime 200 # start at 2:00 am
>> }
>
>I've not played with 'starttime' but reading your note got me
> thinking that having absolute times as arguments could be an
> administrative pain if the amdump was run at varying times.
>
>Is there any way of specifying a relative value?  Say "starttime
> +30" so it would begin no less than 30 min after the first dump
> starts. I guess it couldn't be after amdump starts because the
> estimate and planning stage varies in length.
>
>
>OK Jon, follow your own, oft given, advice, RTFM  
>
>Well there certainly is nothing in the man page describing relative
>values, so I suspect I answered my own query.  Perhaps it would be
>a good "Wish List" item.

Agreed Jon. I think the variable amount of time that it took amanda to 
get done with the main run was the reason I kept at it, exploring 
other scripting ways to achieve what I wanted to do.  Which I think 
I've done although the scripts look pretty ragged cause I rarely 
delete something, just comment it out. :(

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: Amanda Backup

[Paul Bijnens]

Jon LaBadie wrote:
Is there any way of specifying a relative value?  Say "starttime +30"
so it would begin no less than 30 min after the first dump starts.
I guess it couldn't be after amdump starts because the estimate and
planning stage varies in length.

To solve the problem of prioritizing the order of certain dumps,
"starttime" (even with a relative time) is just a kludge, I believe.
I wonder why people would like to specify the order.
The reason I wanted it was to fill my tapes to 100%, and for the
taperalgo to work well, the larger dumps should be taped first.
Otherwise, you end up with all small dumps being finished and taped
already, filling the tape just enough so that any of the larger
dumps does not fit anymore, wasting a lot of tape (and time).
Maybe we need another directive for dumptype like "order {first|last}",
so that you can specify certain dumps to be started first, and others
to be started last; all the rest in between.  (Up to "inparrallel" dumps
can be started "first".)
What I also would like to see is to schedule certain DLE's close to
each other (e.g. because they contain parts of a database that has to
stopped before dumping the first DLE and started after the last DLE --
don't extend downtime by scheduling other DLE's inbetween).
Maybe a directive "group" giving a name to each group.
And while Santa-Claus is listening, I would also like a directive to
execute some scripts at start and end of each "group" (a name of a
script which must be located on that client), possibly with arguments
provided on one (the first?) of the group members.
host.com.tv /oradata1 {
comp-user-tar
order first
group db1 {
atstart /usr/local/bin/dbstop PRD immediate
atend   /usr/local/bin/dbstart PRD
}
}
host.com.tv /oradata2 {
comp-user-tar
group db1   # is a member of group named "db1"
}
I know, Santa Claus does not exist...
But Stefan saves these mails, isn't it?
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amanda Backup

[Stefan G. Weichinger]

Hi, Jon,

on Mittwoch, 02. März 2005 at 17:03 you wrote to amanda-users:

JL> Is there any way of specifying a relative value?  Say "starttime +30"
JL> so it would begin no less than 30 min after the first dump starts.
JL> I guess it couldn't be after amdump starts because the estimate and
JL> planning stage varies in length.

JL> OK Jon, follow your own, oft given, advice, RTFM  

JL> Well there certainly is nothing in the man page describing relative
JL> values, so I suspect I answered my own query.  Perhaps it would be
JL> a good "Wish List" item.

It is relative when you read http://www.amanda.org/docs/using.html
(still not formatted completely ...):

>The starttime dumptype parameter delays a backup some amount of
>time after AMANDA is started. The value is entered as HHMM, so 230,
>for instance, would wait 2.5 hours. This may be used to delay
>backups of some areas until they are known to be idle.

The manpage says:

> starttime "int"
> Default:  none.   Backups  will not start until after this time of
> day.  The value should be hh*100+mm, e.g. 6:30PM (18:30) would be
> entered as 1830.

No relativity here, you're right.

CVS-Changelog:

> Allow certain dumptypes to be kicked off at specific times.
> Add a new, optional, parameter to the dumptype description in
> the config file.  The parameter is called "starttime" and takes
> one argument which is a time of day (local timezone) formated
> as either hhmm or hmm (no `.'s, no `:'s, just an integer).
> define dumptype comp-user-2am {
> comment "Non-root partitions on fast machines"
> options compress-fast
> priority medium
> starttime 0200
> }
> Any partitions listed in disklist with this dumptype will be
> fired off no earlier than 2am.  If 2am today is less than 43200
> seconds past (12 hours ago) it will assume you meant 2am today
> and fire the dumps off right away.  But if 2am today is more
> than 12 hours in the past, it will wait till 2am tomorrow.
> Patch from Brad Huntting <[EMAIL PROTECTED]>.

This was AMANDA 2.3.0.4 ...

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Amanda Backup

[Stefan G. Weichinger]

Hi, Paul,

on Mittwoch, 02. März 2005 at 10:58 you wrote to amanda-users:

PB> taperalgo largestfit# why isn't this the default?

No problem with setting this the default AFAIK.
If noone else comes up with objections I'll edit that file in CVS
soon.
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Amanda Backup

[Stefan G. Weichinger]

Hi, Paul,

on Mittwoch, 02. März 2005 at 18:13 you wrote to amanda-users:

PB> To solve the problem of prioritizing the order of certain dumps,
PB> "starttime" (even with a relative time) is just a kludge, I believe.

I believe that as well.

PB> What I also would like to see is to schedule certain DLE's close to
PB> each other (e.g. because they contain parts of a database that has to
PB> stopped before dumping the first DLE and started after the last DLE --
PB> don't extend downtime by scheduling other DLE's inbetween).
PB> Maybe a directive "group" giving a name to each group.

PB> And while Santa-Claus is listening, I would also like a directive to
PB> execute some scripts at start and end of each "group" (a name of a
PB> script which must be located on that client), possibly with arguments
PB> provided on one (the first?) of the group members.

PB> host.com.tv /oradata1 {
PB> comp-user-tar
PB> order first
PB> group db1 {
PB> atstart /usr/local/bin/dbstop PRD immediate
PB> atend   /usr/local/bin/dbstart PRD
PB> }
PB> }
PB> host.com.tv /oradata2 {
PB> comp-user-tar
PB> group db1   # is a member of group named "db1"
PB> }

Good idea ...

PB> I know, Santa Claus does not exist...
PB> But Stefan saves these mails, isn't it?

Yep, I do, and I let my mailer filter these mails into virtual folders
like "AMANDA Wishes" and "todo" ... (after tagging them).

Actually the development of AMANDA just sits there and waits for the
occasional hacker. Jean-Louis doesn't have much time to do all those
things and the amanda-hackers would need someone who is able to check
their patches and give proper feedback. I would like to dig into the
code more intensely but I still ain't a coder and don't know when I
will find the time to learn C at last ;-)

So I try to at least collect ideas and provide them to those who can
make solid code out of it.
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Amanda Backup

[Jon LaBadie]

On Wed, Mar 02, 2005 at 06:38:00PM +0100, Stefan G. Weichinger wrote:
> Hi, Jon,
> 
> on Mittwoch, 02. März 2005 at 17:03 you wrote to amanda-users:
> 
> JL> Is there any way of specifying a relative value?  Say "starttime +30"
> JL> so it would begin no less than 30 min after the first dump starts.
> JL> I guess it couldn't be after amdump starts because the estimate and
> JL> planning stage varies in length.
> 
> JL> OK Jon, follow your own, oft given, advice, RTFM  
> 
> JL> Well there certainly is nothing in the man page describing relative
> JL> values, so I suspect I answered my own query.  Perhaps it would be
> JL> a good "Wish List" item.
> 
> It is relative when you read http://www.amanda.org/docs/using.html
> (still not formatted completely ...):

You mean TFM is sometimes inaccurate ;-))

> >The starttime dumptype parameter delays a backup some amount of
> >time after AMANDA is started. The value is entered as HHMM, so 230,
> >for instance, would wait 2.5 hours. This may be used to delay
> >backups of some areas until they are known to be idle.

> The manpage says:
> 
> > starttime "int"
> > Default:  none.   Backups  will not start until after this time of
> > day.  The value should be hh*100+mm, e.g. 6:30PM (18:30) would be
> > entered as 1830.
> 
> No relativity here, you're right.
> 
> > Allow certain dumptypes to be kicked off at specific times.
> > Add a new, optional, parameter to the dumptype description in
> > the config file.  The parameter is called "starttime" and takes
> > one argument which is a time of day (local timezone) formated
> > as either hhmm or hmm (no `.'s, no `:'s, just an integer).
> > define dumptype comp-user-2am {
> > comment "Non-root partitions on fast machines"
> > options compress-fast
> > priority medium
> > starttime 0200
> > }


Grossly different meanings.  Yet I can see Paul B's description of his usage
as fitting either actuality.  He indicated a "starttime 0200".  But if his
amdump was run at about midnight, 2AM would also be about 2 hours after the
start.

Definitely needs clarification.  My dusted-off, little gray cells say the
discussion when starttime was introduced covered things like laptops and
PC's that were only on during work hours for sites that did overnight
amdumps for their servers.  So I'd think the starttime argument was clocktime.

Sounds like availability of both could be useful

starttime 0430  # start at 4:30AM
starttime +200  # delay start by 2 hours.
starttime -100  # start 1 hour before amdump is started  :))

BTW how is estimating and planning done when some DLEs are delayed for a while
and may not even be on the network or booted when amdump starts?

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

Re: Amanda Backup

[Stefan G. Weichinger]

Hi, Jon,

on Mittwoch, 02. März 2005 at 19:10 you wrote to amanda-users:

JL> You mean TFM is sometimes inaccurate ;-))

You can bet on this.

JL> Grossly different meanings.  Yet I can see Paul B's description of his usage
JL> as fitting either actuality.  He indicated a "starttime 0200".  But if his
JL> amdump was run at about midnight, 2AM would also be about 2 hours after the
JL> start.

JL> Definitely needs clarification.  My dusted-off, little gray cells say the
JL> discussion when starttime was introduced covered things like laptops and
JL> PC's that were only on during work hours for sites that did overnight
JL> amdumps for their servers.  So I'd think the starttime argument was 
clocktime.

Anyone testing this?

JL> Sounds like availability of both could be useful

JL> starttime 0430  # start at 4:30AM
JL> starttime +200  # delay start by 2 hours.
JL> starttime -100  # start 1 hour before amdump is started  :))

JL> BTW how is estimating and planning done when some DLEs are delayed for a 
while
JL> and may not even be on the network or booted when amdump starts?

Ever done a grep for "starttime" in the AMANDA-sources?
I did and it didn't give me any good answers yet ...
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Amanda Backup

[Eric Siegerman]

On Wed, Mar 02, 2005 at 01:10:53PM -0500, Jon LaBadie wrote:
>   starttime -100  # start 1 hour before amdump is started  :))

You could kind-of actually do this.  It'd just mean, "delay
everything *else* by 1 hour".  Now, whether there's a reason to
implement it is another question entirely.

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
The animal that coils in a circle is the serpent; that's why so
many cults and myths of the serpent exist, because it's hard to
represent the return of the sun by the coiling of a hippopotamus.
- Umberto Eco, "Foucault's Pendulum"

Re: Amanda Backup

[Paul Bijnens]

Stefan G. Weichinger wrote:
Ever done a grep for "starttime" in the AMANDA-sources?
I did and it didn't give me any good answers yet ...
  grep STARTTIME */*.c
  grep start_t */*.c
especially conffile.c, line 2360 or about (in 2.4.4p4).
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amanda Backup

[Paul Bijnens]

Paul Bijnens wrote:
especially conffile.c, line 2360 or about (in 2.4.4p4).
Following up to myself, because I forgot the conclusion:
It is absolute time:
   2360 static int get_time()
   2361 {
   2362 time_t st = start_time.r.tv_sec;
   2363 struct tm *stm;
   2364 int hhmm;
   2365
   2366 get_conftoken(INT);
   2367 hhmm = tokenval.i;
   2368
   2369 stm = localtime(&st);
   2370 st -= stm->tm_sec + 60 * (stm->tm_min + 60 * stm->tm_hour);
   2371 st += ((hhmm/100*60) + hhmm%100)*60;
   2372
   2373 if (st-start_time.r.tv_sec<-43200)
   2374 st += 86400;
   2375
   2376 return st;
   2377 }
Line 2370 calculates midnight.
Line 2371 adds the hhmm, resulting in absolute time.
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amanda Backup

[Stefan G. Weichinger]

Hi, Paul,

on Mittwoch, 02. März 2005 at 21:35 you wrote to amanda-users:

PB> Stefan G. Weichinger wrote:

>> Ever done a grep for "starttime" in the AMANDA-sources?
>> I did and it didn't give me any good answers yet ...

PB>grep STARTTIME */*.c
PB>grep start_t */*.c

PB> especially conffile.c, line 2360 or about (in 2.4.4p4).

Errm, did a "grep starttime */*.c" ... what a shame :-)

Stefan

Re: Amanda Backup

[Stefan G. Weichinger]

Hi, Paul,

on Mittwoch, 02. März 2005 at 21:42 you wrote to amanda-users:

PB> Paul Bijnens wrote:
>> especially conffile.c, line 2360 or about (in 2.4.4p4).

PB> Following up to myself, because I forgot the conclusion:

PB> It is absolute time:

PB> 2360 static int get_time()
PB> 2361 {
PB> 2362 time_t st = start_time.r.tv_sec;
PB> 2363 struct tm *stm;
PB> 2364 int hhmm;
PB> 2365
PB> 2366 get_conftoken(INT);
PB> 2367 hhmm = tokenval.i;
PB> 2368
PB> 2369 stm = localtime(&st);
PB> 2370 st -= stm->tm_sec + 60 * (stm->tm_min + 60 * stm->tm_hour);
PB> 2371 st += ((hhmm/100*60) + hhmm%100)*60;
PB> 2372
PB> 2373 if (st-start_time.r.tv_sec<-43200)
PB> 2374 st += 86400;
PB> 2375
PB> 2376 return st;
PB> 2377 }

PB> Line 2370 calculates midnight.
PB> Line 2371 adds the hhmm, resulting in absolute time.

Looks like a relative functionality could be added "relatively" easy
;-)

I CC: this to the hackers ...
(@hackers:please refer to the users-list for the whole story ...)

Thanks for digging that up, Paul.
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Amanda Backup

[shafiqa qawasmi]

how can i fix this error with... os  sco unix & amanda the last versionUX:acomp: ERROR: "output-tape.c", line 313: cannot find include file: 
h>
 
>From: Paul Bijnens <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>CC: amanda-users@amanda.org
>Subject: Re: Amanda Backup
>Date: Wed, 02 Mar 2005 10:58:08 +0100
>
>Kaushal Shriyan wrote:
>>
>>Can I prirotise the backup in Amanda, I mean first HOST A, Then
>>HOST B
>>and next on words or can I specify in the disklist file
>
>Not completely, but you have some control.
>
>First there is the "priority" directive in the dumptype definition.
>Here "priority" is not time related (common misconception), but,
>when amanda has no tape to write, it falls back to degraded mode,
>doing incrementals to holdingdisk.  If there is not enough space,
>amanda chooses which to drop according to the priority
>("priority low" is dropped first).
>
>If you want time-based priority, you can add the "starttime"
>directive
>to some dumptypes. The starttime indicates that backups will not
>start
>until after this time of the day.  YOu can defined two dumptypes,
>one without starttime (i.e. backups will start as soon as amdump
>starts), and one with a delayed starttime (then hopefully all the
>others
>have already started). If you run amdump at e.g. 00:05 past
>midnight,
>you can define these two dumptypes:
>
>define dumptype normal {
> global
>}
>define dumptype delayed {
> normal
> starttime 200 # start at 2:00 am
>}
>
>You'll have to find out experimentally at what time it is safe to
>start with the lower priority DLE's.  You'll have to understand
>the relations between number of "inparallel" dumpers, and several
>constraints that inhibit amanda to start another dump, like spindle,
>"maxdumps" in the dumptype, bandwith and holdingdisk space.
>"amplot" is your friend here, together with an careful examination
>of the dump.X file.
>
>That said, many people (like me) would like to start the longest
>dumps first, not because they are more important, but that they are
>finished by the time people start to work again, and so that they
>can
>be put first on tape (avoiding restarting such a large dump because
>it
>bumped into end of tape -- longest are probably among the largest
>too).
>For that simple case, no need to add starttime, just change the
>default
>dumporder:
>
>inparallel 8 # or anything you  like
>dumporder ""# as many T's as you have "inparallel"
>taperalgo largestfit # why isn't this the default?
>
>
>--
>Paul Bijnens, XplanationTel  +32 16
>397.511
>Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16
>397.512
>http://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, *
>* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...  
>  *
>* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out
>  *
>***
>
>
Express yourself instantly with MSN Messenger! MSN Messenger Download today it's FREE!

Planning amanda backup

[B N Chatterjee]

Hi ,
 i have some problem in setting amanda.conf right . My reqirement 
is like below :

1) I am having 5 server data to backup ( including my amanda backup server). 
2) The Backup will run everyday .
3) I have modified disklist for the partitions for each server .
4) I require 2 DLT s [ with 20 GB compressed mode ] for each server
partition.
5) I wish that on a single tape dump image of only one server will be
there , which may span second tape [ two tapes per server as mentioned ] .
6) I am having 10 sets of DLT tapes ready per day basis . Total 70 tapes 
   are ready for a week long backup .
7) the tapes wil be recycled and overwritten on each passing week as
   usual.

Pls let me know what changes is required in amanda.conf and other relevant 
files to attain the above purpose .

Thanks a lot .

B.N.C

Amanda backup levels

[Jeroen Heijungs]

Probably very stupid questions, but can someone shed some light on very simple 
questions: what exactly are
the differences between the different levels of backup? I searched the documentation 
and arcives but so far
I have not found the exact definitions.

As I understand:
- level 0 is full-backup
- level 1 is incremental backup, based on modification time (?)
- what are the higher levels ???

And to be sure:
- at least once per dumpcycle there is a fullbackup
- the other runs are mostly level 1 (incremental), so all changes to the filesystems 
are on tape - is this
right ???

I ask now, because untill now we "only" had to backup FreeBSD servers acting as 
routers, gateways.
firewalls, mailrelayservers etc. None of them had real fast-changing user-data, so 
up-to-date restores were
not an high-priority issue and we never had to restore something (rock-solid os!).
But now we are moving to imap-mail and that means that there are lots of user-data 
which change very often
and have to restore more often (users delete mail-folders accidently), so I have to be 
sure that all changed
data is backed-up every run, users do not want mails missing.

Last question:
- are there gui-frontends for the restore, that work for the helpdesk staff (they 
cannont work with the
amrestore interface) ?

thanks in advance
Jeroen Heijungs
Het Muziektheater
Amsterdam

Re: Amanda Backup

[Paul Bijnens]

Kaushal Shriyan wrote:
In My office amanda does a full backup regularly for 3 days but why is
it not switching over to a incremental backup after the full backup is
run for first time
any help

Now we can only guess, like "you told her so", or "because she
has a mind of her own".
It would help us if post more info, like the e.g. configuration.
(At least if you're not talking about Amanda, the secretary
 in Your office)).
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amanda Backup

[Joshua Baker-LePain]

On Wed, 21 Jul 2004 at 11:39am, Kaushal Shriyan wrote

> Wanted to know about amanda tape viz to check what will be the next run
> for a particular hostname, diskname. 
> 
> How do i check that

I'm not sure exactly what you're asking, but I'm sure your answers lie in 
'man amadmin'.  It can tell what tape amanda wants next, what's on tape 
for each DLE, etc.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Amanda Backup

[Matt Hyclak]

On Wed, Jul 21, 2004 at 08:22:11AM -0400, Joshua Baker-LePain enlightened us:
> > Wanted to know about amanda tape viz to check what will be the next run
> > for a particular hostname, diskname. 
> > 
> > How do i check that
> 
> I'm not sure exactly what you're asking, but I'm sure your answers lie in 
> 'man amadmin'.  It can tell what tape amanda wants next, what's on tape 
> for each DLE, etc.

I think what he's asking for is a way to find out what level dump will be
done during the next run of amanda for a particular host/disk. 

Unfortunately the answer is you can't. amadmin can tell you what level was
done on the last run (amadmin Config info host disk), and it can tell you
when the next level 0 is due (amadmin Config due host disk). So, you can
guess based on that information what the next run might be, however amanda
is free at any time to move a level 0 forward in time if it will help
balance the amount of dumps.

Hope that explains it...

Matt

-- 
Matt Hyclak
Department of Mathematics 
Department of Social Work
Ohio University
(740) 593-1263

Re: Amanda Backup

[Paul Bijnens]

Kaushal Shriyan wrote:
I have following queries in the amanda Backup
1)
[EMAIL PROTECTED] amanda]$ amadmin DailySet1 balance
new disk indus.mumbai.redhat.com://account.mumbai.redhat.com/C ignored.
>
> Why do i get this
>
Because amanda never did a full backup of that DLE, it cannot
predict when it will be scheduled, nor how much data that will
add to the size of full backups that day.

2) I get this  whwn i run amadmin DailySet1 due
Overdue 12619 days:
indus.mumbai.redhat.com://account.mumbai.redhat.com/D
Overdue 12619 days: illusions.mumbai.redhat.com:/home/amit
Can anyone clarify this on the above point

$ perl -M'Date::Calc ":all"' \
-e 'print join("-", Add_Delta_Days(2004, 7, 26, -12619)), "\n"'
1970-1-7
I guess you got that result 6 days ago :-)
January 1, 1970 is the beginning of the epoch in Unix.
I'm not 100% sure, but I think that some older version of Amanda
says this when this is a new disk, or you did a "amadmin config force"
on that DLE to force a full dump.  What version is this?
Otherwise you somehow got a zero in the field of last-full-dump
in the info files.  Don't know how that could get there (except if
your CMOS battery is broken, and you booted that computer 6 days ago?)
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: amanda Backup

[Paul Bijnens]

Kaushal Shriyan wrote:
I am facing some issues with the backup process of the amanda
it writes data to the tape. lets say it has written to the tape when i
am restoring from the tape to the hard disk
a folder abc, now inside the abc folder there is no contents why is it
happening  but when i check the orginal folder the contents are there.
It's a little hard to follow.
Can you show the exact commands that you type?

please help as it a matter of concern for me 

Would appreciate if you can reply me fast, I have also attached my
amanda.conf file for your ready reference
please advice


--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

RE: Amanda Backup

[Gavin Henry]

Hi,

It's best to do it when no one is writing or saving documents etc.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kaushal Shriyan
Sent: 23 August 2004 13:46
To: [EMAIL PROTECTED]
Subject: Amanda Backup


Hi All

Wanted to know about the time schedule of backups. Can i take backup
during the working hours or is it compulsory to take in the night when
there is no I/O operation.

-- 
Regards,

Kaushal Shriyan

Technical Engineer
Red Hat India Pvt. Ltd.
Tel  : +91-22-22881326/27
Fax  : +91-22-22881318

Amanda backup error

[Fonken, Annita J]

> I'm getting the following error message on my backup reports from a DEC ALpha that 
>is running operating system OSF 40.d . The error message states from the backup 
>report for this unix dec alpha machine named wiley  :
> 
>  wiley /usr1 - /usr7 partitons lev 0 failed [wiley NAK: amanda not allowed access : 
>.amandahosts auth failed]
> 
> Is there a description anywhere of what this error means?
>  We have checked the client's configuration and it seems to be ok. 
> 
> We are running amanda version 2.5.0-19991009 on the backup server according to the 
>backup report. 
> The backup server is not on the same subnet as the client wiley.The backup server is 
>also a SunW , E3000 . I understand that the Dec Alpha is supposed to be running 
>amanda 2.4.1.p1 version of amanda from reading your ftp web page. Is our present 
>version 2.5.0 -19991009 on the backup server compatable with Dec Alpha running the 
>above version of the OSF operating system? Is there any patches I need for the backup 
>server's version of Amanda to correct this problem ? Can you run a different versions 
>of amanda on the server that you do on the client ? Is there a way to tell what 
>version of Amanda was installed on the DEC Alpha client ? If you can help me I would 
>sure appreciate it.
>  Please respond as soon as you can .
> 
Also is there some web page database you can lookup these errors from running backups 
with Amanda ?

Annita J. Fonken
Unix System Administrator
Phantom Works Program & Factory Support
Resource Management 
Phone 253-657-3408
Fax   253-773-7122
email address [EMAIL PROTECTED]

Re: Amanda backup

[Mangala Gunadasa]

Hi everybody,

 I am backing up 3 systems using amanda. My /etc/dumpdates on 3 systems ( total 12 
files)shows that al the files were backed up. But the amverify shows less file systems 
than what /etc/dumpdates indicate( only 4 files). 

I'd appreciate if anybody can tell what is happening.

 Thanks,
 

Re: Amanda backup

[John R. Jackson]

> I am backing up 3 systems using amanda. My /etc/dumpdates on 3 systems ( tota
>l 12 files)shows that al the files were backed up.  ...

Did the Amanda mail report show all 12 file systems being backed up?
Any problems reported?  Did all of the images make it to the tape or
did you have to amflush some?

>But the amverify shows less
> file systems than what /etc/dumpdates indicate( only 4 files). 

I'd have to see the amverify report to know exactly what you mean.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

amanda backup fails

[Gene Heskett]

On Monday 10 December 2018 18:04:47 Elias Pereira wrote:

> Hello Helge,
>
> Thanks for the answer!!!
>
> In my cups webgui does not have that tiny triangle!!! Can you show me
> with a printscreen?
>
> On Mon, Dec 10, 2018 at 3:13 PM Helge Blischke  
wrote:
> > > Am 10.12.2018 um 17:35 schrieb Elias Pereira :
> > >
> > > Hello,
> > >
> > > How do I config cups webgui to display the jobs in ascending order
> >
> > (Newest
> >
> > > to Oldest)?
> > >
> > > --
> > > Elias Pereira
> >
> > Klick on one of the tiny triangles besides the "ID“ in the title
> > line.
> >
> > Helge
> >
Normally you build amanda in the /home/amanda directory, sudo -i,
then su amanda. Then when its built, ctrl-D out of amanda and make 
install as root, then your perms are all as they should be. I have a 
configure driver file to configure and build, and It won't do a thing if 
I'm root.  Thats a bad dog, no biscuit if not the user amanda.

The script:

#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo "!! Warning !!!"
echo "Amanda needs to be configured and built by the"
echo "user amanda, but must be installed by user root."
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/usr/local/ \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote \
--with-bsdtcp-security --with-amandahosts \
--with-configdir=/usr/local/etc/amanda \
--enable-manpage-build  \
--with-readline \
--with-gnutar=/bin/tar \
--with-security-file=/etc/amanda-security.conf \
--with-amandates-file=/etc/amandates
echo "sleeping for reading configures warnings"
echo "a make as amanda will continue after 75 seconds..."
sleep 75
make




> > ___
> > cups mailing list
> > c...@cups.org
> > https://lists.cups.org/mailman/listinfo/cups



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Amanda Backup Strategy

[Ralph Bearpark]

I have a tapeless back-up config here with 2.4.3.  I have 30 virtual tapes, and so 
have amanda.conf values of "dumpcycle 30 days" and "tapecycle 30 tapes"

Now, man amanda tells me that this dumpcycle value should mean that "each disk using 
this set of options will get a full backup at least this often" i.e at least every 30 
days.

However, when I look an amoverview I see that several disks are getting a full backup 
EVERY OTHER DAY!  What's the idea of this?  I'll grant it's within the letter of the 
manual, but it's hardly space-efficient is it?

Is there any way I can force amanda to only do the full backup at most n times during 
the dumpcycle?

Also, I see that other disks are getting repeated level 1 incrementals.  I would be 
happier if it rather did level 1 then 2 then 3 etc. and no backup if no files had 
changed.  Can I specify this behaviour somehow?

I know it will make a full restore a little messier but I simply don't have unlimited 
disk space for amanda to use.

Thanks in anticipation for advice.

Regards, Ralph Bearpark.

Amanda Backup USB?

[Christ Schlacta]

I'm evaluating possible solutions for "Drop in USB backup".  as an
existing amanda user, I was interested by the possibility of having
amanda run a backup of a flash drive whenever it's connected.  I've
got a few simple requirements for this backup operation.  1) a backup
should happen whenever a "Known" usb drive is connected.  I have a
good idea how to do this with a generic UDEV rule and a script.  2) an
option to backup a drive in either "block level" (for encrypted
drives/filesystems) or "file level" mode.  amanda supports both,
though how to enable that option in configuration settings I'm a bit
unsure, but it doesn't seem insurmountable.  3) a simple web interface
(Again, I can whip something up), and 4) non-interactive operation.
with a script, most things can be done non-interactively for backups.
5) Backup mode.  when a user goes to a website and picks their drive
out of the list and specifies "Backup mode",  they should get the
version of files the specified back from the drive, optionally backing
up first.  6) when a backup or restore is done, users should get a
notification in their inbox that it's done.  this is again ahndled by
a no-longer trivial script called from udev.

5 is where I forsee the most issues.  firstly, can a restore be run
completely non-interactively like that, on an entire directory tree,
recursively?  I've never had to do ti yet, so I don't recall.  The
interface will be a smidge tricky, but doable.
Managing the the number of configuration sets needed to maintain this
system, even automatedly seems like it might be prone to errors.

What does the amanda list think, is this using a sledge hammer to push
in a thumbtack, or is amanda well suited to this task, and the issues
just need to be more fleshed out?  I ahve a few alternatives,
including using simple OS tools to backup to a directory that's in
turn backed up by amanda with other data, and looking for some
pre-existing solution, which I haven't yet found.

Re: Planning amanda backup

[John R. Jackson]

>1) I am having 5 server data to backup ( including my amanda backup server). 
>2) The Backup will run everyday .
>3) I have modified disklist for the partitions for each server .
>4) I require 2 DLT s [ with 20 GB compressed mode ] for each server
>partition.
>5) I wish that on a single tape dump image of only one server will be
>there , which may span second tape [ two tapes per server as mentioned ] .
>6) I am having 10 sets of DLT tapes ready per day basis . Total 70 tapes 
>   are ready for a week long backup .
>7) the tapes wil be recycled and overwritten on each passing week as
>   usual.

Why do you have to have requirement #5?  Segregating clients (what
Amanda calls the machines it backs up) to separate tapes is going to
make your life harder.  Although I can think of reasons to want this,
most people let Amanda mix all the clients.

If you have to have separate tapes, you're going to need to create five
separate configurations, one per machine being backed up.  And you'll
need to split the 70 tapes up into five sets of 14 and dedicate a set to
each configuration.  Then you'll have to run one configuration (amdump)
after another in your cron job.

As to item #7, the tapes will be overwritten when they are the oldest
in the list.  For instance, if you allocate two tapes per day but Amanda
only needs one, it is not going to skip over the unused second tape for
that day.  It will ask for it as the first tape of the next run.

Also, you will want to set your dumpcycle slightly smaller than one week.
If you set it to exactly match the tape cycle, it will be overwriting the
last good full dump of some of the file systems at least once a week.
If an error happens during that run, you will not have a valid set of
backups to restore from.  Tapecycle should be at least dumpcycle + 1.
In your case, dumpcycle should not be larger than six days.

>B.N.C

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: Planning amanda backup

[B N Chatterjee]

Thanks a lot for the itemwise clarification .
Could you let me know how shall i set the following parameters in each
instance of amanda.conf   considering that i shall be creating 5 sets of
amanda config ( one per server ) . 

1) inparallel 
2) dumpcycle
3) runspercycle
4) tapecycle 
5) tpchanger ( shold i hash it or keep chg-manual ) 

the dump condition will be as usual . 2 tapes allocated per server .
5 servers to backup . backup will run everyday .
Total tapes available 70 tapes .

Thanks 

B.N.C  

i guess tapecycle will be 14 , & dump cycle will be 6  per config .
am it right ? 
 




On Sun, 10 Feb 2002, John R. Jackson wrote:

> >1) I am having 5 server data to backup ( including my amanda backup server). 
> >2) The Backup will run everyday .
> >3) I have modified disklist for the partitions for each server .
> >4) I require 2 DLT s [ with 20 GB compressed mode ] for each server
> >partition.
> >5) I wish that on a single tape dump image of only one server will be
> >there , which may span second tape [ two tapes per server as mentioned ] .
> >6) I am having 10 sets of DLT tapes ready per day basis . Total 70 tapes 
> >   are ready for a week long backup .
> >7) the tapes wil be recycled and overwritten on each passing week as
> >   usual.
> 
> Why do you have to have requirement #5?  Segregating clients (what
> Amanda calls the machines it backs up) to separate tapes is going to
> make your life harder.  Although I can think of reasons to want this,
> most people let Amanda mix all the clients.
> 
> If you have to have separate tapes, you're going to need to create five
> separate configurations, one per machine being backed up.  And you'll
> need to split the 70 tapes up into five sets of 14 and dedicate a set to
> each configuration.  Then you'll have to run one configuration (amdump)
> after another in your cron job.
> 
> As to item #7, the tapes will be overwritten when they are the oldest
> in the list.  For instance, if you allocate two tapes per day but Amanda
> only needs one, it is not going to skip over the unused second tape for
> that day.  It will ask for it as the first tape of the next run.
> 
> Also, you will want to set your dumpcycle slightly smaller than one week.
> If you set it to exactly match the tape cycle, it will be overwriting the
> last good full dump of some of the file systems at least once a week.
> If an error happens during that run, you will not have a valid set of
> backups to restore from.  Tapecycle should be at least dumpcycle + 1.
> In your case, dumpcycle should not be larger than six days.
> 
> >B.N.C
> 
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
> 

Re: Planning amanda backup

[John R. Jackson]

>Could you let me know how shall i set the following parameters in each
>instance of amanda.conf   considering that i shall be creating 5 sets of
>amanda config ( one per server ) . 
>
>1) inparallel 

I'd leave this at the default.  The extra dumper processes won't hurt
anything.

If your servers (Amanda clients) can handle the load, and you have enough
holding disk space and network bandwidth, you might set maxdumps up from 1
to 2 (or more) so more than one filesystem can be dumped at the same time.

>2) dumpcycle

As you noted, with a seven day tapecycle, dumpcycle should be (at most)
six (days).

>3) runspercycle

Since your backups will run every day, leave this alone.

>4) tapecycle 

This would be 14 (7 days * 2 tapes/day).

>5) tpchanger ( shold i hash it or keep chg-manual ) 

If you want to use (up to) two tapes per day, you will need to set
runtapes to 2.  That, in turn, means you *have* to have a tape changer
defined.  If you don't have a "real" tape changer (i.e. a robot or
stacker), and you only have one tape drive, chg-manual is probably the
way to go, unless you want to write your own (it's not very hard).

If you have more than one tape drive, chg-multi would also work.
You would load both tapes for the next run and it would automatically
switch from the first to the second, if needed.

The chg-manual changer is meant to be used when amdump is run
interactively, i.e. when someone starts amdump by hand and watches for
tape mount requests on the tty.  If you're going to run it from cron or
in the background some other way, look at the comments in the chg-manual
script itself to see how to set up the notification (via E-mail, or
console log messages, etc).

>B.N.C  

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

amanda backup status - amstatus

[silpa kala]

Hi,

How to verify how much data backed up? Is there anyway
we can figure out from the amdump.1 log file.

Please clarify this doubt.

Thanks & Regards,
silpakala

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Amanda backup server restore

[Gordon J. Mills III]

I have seen some posts lately refering basically to recovering your amanda
backup server in case of failure. i.e. if you have to rebuild your backup
server and you want to restore all your amanda data, etc.

In particular "amadmin export". What I am currently doing is this:
tar -cpPzf /home/myname/cjs-amback.tar.gz /var/lib/amanda/ /etc/amandahosts
/etc/amandapass /etc/amanda/ /var/log/amanda/

Then I scp that file to other backup servers. And the other servers do the
same. 
My question is: Is it necessary to do the "amadmin export" also?

Thanks,
Gordon Mills

can amanda backup symlink?

[fedora]

Hi huys..

I have 2 situations:

1) default directory for MySQL is /var/lib/mysql. If this directory is link
to /var2/db/mysql and if I put /var/lib/mysql in disklist, can amanda do
backup? I think this should be can backup. May I know which directory is the
best to put in disklist for this case? 

2) how about this one. In /var/lib/mysql has databases but certain databases
in linking to /var3/mysql like:

lrwxrwxrwx1 root root   42 May 16  2007 AngelClub ->
/var3/mysql/AngelClub
drwx--2 mysqlmysql4096 Nov 13 11:55 BabyMobile
drwx--2 mysqlmysql4096 Nov 13 11:55 BestClub

If I put only /var/lib/mysql in disklist, can amanda backup for /var3/mysql?
Or should add both /var/lib/mysql and /var3/mysql in disklist? Please
advise.
-- 
View this message in context: 
http://www.nabble.com/can-amanda-backup-symlink--tf4848518.html#a13872345
Sent from the Amanda - Users mailing list archive at Nabble.com.

Re: Amanda backup levels

[Nicolas Ecarnot]

Jeroen Heijungs wrote:

Probably very stupid questions, but can someone shed some light on very simple 
questions: what exactly are
the differences between the different levels of backup? I searched the documentation 
and arcives but so far
I have not found the exact definitions.
Level n backup is a backup where you save what has changed since the 
last level n backup. period.

As I understand:
- level 0 is full-backup
- level 1 is incremental backup, based on modification time (?)
- what are the higher levels ???
You can do L0 backups once a month, L1 backups once a week, and L2 
backups everyday.
So, everyday, you will save what you changed since the last L2 backup, 
that is to say since the day before.

I explain that though now I hate incremental backups and pray for not 
having to do with them anymore.
They may look fun (and indeed they DO are very well managed by Amanda) 
but it may turn to nightmare when you have to restore some directories 
with changes in different level backups, and one of you tape fails...

I ask now, because untill now we "only" had to backup FreeBSD servers acting as 
routers, gateways.
firewalls, mailrelayservers etc. None of them had real fast-changing user-data, so 
up-to-date restores were
not an high-priority issue and we never had to restore something (rock-solid os!).
But now we are moving to imap-mail and that means that there are lots of user-data 
which change very often
and have to restore more often (users delete mail-folders accidently), so I have to be 
sure that all changed
data is backed-up every run, users do not want mails missing.
In my company, we use OpenBSD as an imap server, and FreeBSD as a samba 
server, and the files are changing very fast. So we do L0 backups 
everynight.
If you can afford, avoid incremental backups.

Last question:
- are there gui-frontends for the restore, that work for the helpdesk staff (they 
cannont work with the
amrestore interface) ?
No. I heard they were people working on a web frontend, but hey, when 
you restore some data, are you sure you will have a gui running ? Are 
you even sure you will have any network working ?
The command line interface is simple enough to be usable in the worst 
situation, think about that.

PS. CALLING ALL CARS : Are the guys working on the web frontend reading 
this e-mail ?

--
Nicolas Ecarnot

Re: Amanda backup levels

[Nicolas Ecarnot]

Nicolas Ecarnot wrote:

Today, I speak to myself :

PS. CALLING ALL CARS : Are the guys working on the web frontend reading 
this e-mail ?
http://subwiki.honeypot.net/cgi-bin/view/Computing/AmControl

Not tested...

--
Nicolas Ecarnot

Re: Amanda backup levels

[Jeroen Heijungs]

I asked about the differences between the levels of backup and I got (sofar)
two different answers (thanks to you both), so I still do not know for sure:

Nicolas Ecarnot wrote:
> Level n backup is a backup where you save what has changed since the
> last level n backup. period.

Gertjan van Oosten wrote:
> A level N backup includes all files modified since the last level M
> backup where M < N.  So a level 1 backup includes all files changed
> since the last level 0 backup; a level 2 backup includes all files
> changed since the last level 1 backup (or if there was no such backup,
> it includes all files changed since the last level 0 backup), etc.
> A level 0 backup includes all files, period.

That are two different ways, the first I normally call INCREMENTAL, the
second I normally call DIFFERENTIAL. I prefer the second, because mostly you
will not need every tape, but only the first (full) and the last, and not all
others in between.

Some more questions:
- in theory you can get an infinite level (no limit) backup ?
- the more low-level backups you see (0 and 1), the better Amanda can
  handle the dumpcycle and tape capacity ? Or the other way round, Amanda
  will try to make as much level 0 backups as possible but based on the
  dumpcycle and capacity she will choose to do more level 1,2,3,4 backups
  in between ?

tia
Jeroen Heijungs
Het Muziektheater
Amsterdam

Re: Amanda backup levels

[Gertjan van Oosten]

Hi Jeroen,

As quoted from Jeroen Heijungs <[EMAIL PROTECTED]>:
> what exactly are the differences between the different levels of
> backup?

A level N backup includes all files modified since the last level M
backup where M < N.  So a level 1 backup includes all files changed
since the last level 0 backup; a level 2 backup includes all files
changed since the last level 1 backup (or if there was no such backup,
it includes all files changed since the last level 0 backup), etc.
A level 0 backup includes all files, period.
See e.g. the manual page for ufsdump for some more information.

> And to be sure:
> - at least once per dumpcycle there is a fullbackup

Amanda tries to do that, yes.  You will get a warning if you are near
the end of your tape cycle and a level 0 dump of a file system hasn't
been made thus far.
["Last full dump of %s:%s on tape %s overwritten in %d run%s."]

> - the other runs are mostly level 1 (incremental),

That depends.  Amanda tries to balance things and if there's enough room
on the tape, it may decide to run a level 0 more than once in the tape
cycle.

> so all changes to the filesystems are on tape - is this right ???

In principle (unless your tape cycle is too short, or you have too much
incremental data to fit even on one tape) all changed files are
somewhere in the tape cycle.

Met vriendelijke groet,
-- 
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600

Re: Amanda backup levels

[Gertjan van Oosten]

Hi Jeroen,

As quoted from Jeroen Heijungs <[EMAIL PROTECTED]>:
> I asked about the differences between the levels of backup and I got (sofar)
> two different answers (thanks to you both), so I still do not know for sure:

My answer was paraphrased from the ufsdump documentation.

> Some more questions:
> - in theory you can get an infinite level (no limit) backup ?

In theory: yes.  In practice: ufsdump limits the levels to 0 through 9.

Kind regards,
-- 
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600

Re: Amanda backup levels

[Nicolas Ecarnot]

Jeroen Heijungs wrote:

I asked about the differences between the levels of backup and I got (sofar)
two different answers (thanks to you both), so I still do not know for sure:
Nicolas Ecarnot wrote:

Level n backup is a backup where you save what has changed since the
last level n backup. period.


Gertjan van Oosten wrote:

A level N backup includes all files modified since the last level M
backup where M < N.  So a level 1 backup includes all files changed
since the last level 0 backup; a level 2 backup includes all files
changed since the last level 1 backup (or if there was no such backup,
it includes all files changed since the last level 0 backup), etc.
A level 0 backup includes all files, period.
Indeed, the M < N statement is correct.
You can start with a L0 backup once a year, then do one L1 backup each 
month, then do a L2 backup everyday.
Everyday, what will be saved is what changed since the start of the month.
So normally, on april 1th, the L1 backup you'll do will contain what 
changed since the start of the year.



On 20040402, to restore a complete system that was set up on january 1th 
and crashed today, you'll have to provide :
- L0 2004
- L1 200404
- L2 20040402



Experts, please correct me.

(As you can see, I prefer level 0 backups ;o)

Some more questions:
- in theory you can get an infinite level (no limit) backup ?
Yes.

tia
Salut.

--
Nicolas Ecarnot

Re: Amanda backup levels

[Gertjan van Oosten]

Hi Nicolas,

As quoted from Nicolas Ecarnot <[EMAIL PROTECTED]>:
> On 20040402, to restore a complete system that was set up on january 1th 
> and crashed today, you'll have to provide :
> - L0 2004
> - L1 200404
> - L2 20040402

Correct.

Salut,
-- 
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600

Re: Amanda backup levels

[Dave Sherohman]

On Wed, Apr 21, 2004 at 10:03:24AM +0200, Nicolas Ecarnot wrote:
> Level n backup is a backup where you save what has changed since the 
> last level n backup. period.

Minor correction:  A level N backup saves all files that have changed
since the last level N-1 backup.  Level 0 gets everything, since there
are no level -1s.

The practical effect of this is that restoring will require at most one
tape more than the highest-level backup that has been run.  (e.g., If a
DLE gets up to level 3 (the highest I've seen here), restoring it will
require, at most, 4 tapes (one each of L0, L1, L2, and L3) regardless
of the dumpcycle or how many tapes of each level have been run.)

Re: Amanda backup levels

[Nicolas Ecarnot]

Dave Sherohman wrote:

Minor correction:  A level N backup saves all files that have changed
since the last level N-1 backup.  Level 0 gets everything, since there
are no level -1s.
This is not a minor correction, this is important, and I recognized my 
error in the thread above.

Thanks for the explanation.
I prefer ask and look dumb than keep quiet and stay dumb ;o)
--
Nicolas Ecarnot

Re: Amanda backup error

[John R. Jackson]

>>  wiley /usr1 - /usr7 partitons lev 0 failed [wiley NAK: amanda not allowed a
>ccess : .amandahosts auth failed]
>> 
>> Is there a description anywhere of what this error means?

Since you're running the development (2.5.0), a.k.a. bleeding edge,
version of Amanda, the docs are probably way, way, out of date.  Time to
learn how to read source code :-).

The first place I'd look, however, is /tmp/amanda/amandad*debug on
the client.  It might have more details about the failure.

Also, what do you have in .amandahosts?

>... I understand that the Dec Alpha is supposed to 
>be running amanda 2.4.1.p1 version of amanda from reading your ftp
>web page.  ...

Huh?

>Is our present version 2.5.0 -19991009 on the backup server compatable with Dec
> Alpha running the above version of the OSF operating system?  ...

As far as I know, all Amanda versions beyond 2.4.0 are compatible with
each other.  However, 2.5.0 has a totally new security framework and
there is at least the potential for problems.

>... Is there a way to tell what version of Amanda was installed on the DE
>C Alpha client ?  ...

It will be shown in the various /tmp/amanda/*debug files.  Start with
amandad*debug (as I asked above).

>Also is there some web page database you can lookup these errors from running 
>backups with Amanda ?

No.  Feel free to look up in the source code the 10,000+ potential errors
Amanda can generate, many of which are just echos of what some system
support library told it, come up with concise yet absolutely correct
descriptions for what they mean and how to fix the problem and post the
results :-).

>Annita J. Fonken

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

amanda backup setup failing

[thing]

anybody have any idea why?

I get the email below, it runs from cron as "backup"

I suspect permissions on the partitions, however I cannot find anything
in the docs or web site to give me a clue, so im almost ending up making
the user backup the same group as root to allow access, this seems
excessive. Any ideas please?

Thing


These dumps were to tape kaitlin02.
Tonight's dumps should go onto 1 tape: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
  kascha /dev/sdb2 lev 0 FAILED [kascha: [access as backup not
allowed from backup@kascha]
  kascha /dev/sdb1 lev 0 FAILED [kascha: [access as backup not
allowed from backup@kascha]
  kascha /dev/sda1 lev 0 FAILED [kascha: [access as backup not
allowed from backup@kascha]


STATISTICS:
  Total   Full  Daily
      
Dump Time (hrs:min)0:00   0:00   0:00   (0:00 start,
0:00 idle)
Output Size (meg)   0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%)   0.00.00.0
Filesystems Dumped0  0  0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --


NOTES:
  planner: Adding new disk kascha:/dev/sda1.
  planner: Adding new disk kascha:/dev/sdb1.
  planner: Adding new disk kascha:/dev/sdb2.
  driver: WARNING: got empty schedule from planner
  taper: tape kaitlin02 kb 0 fm 0 [OK]

non-amanda backup recommendations

[Matthew Boeckman]

As anathema as this question might be:

	I need to recommend a Linux backup solution (or a backup solution with 
a Linux client) that will span tapes. Are there any recommendations from 
the list on commercial options?

Thanks.
--
Matthew Boeckman			(816) 777-2160
Manager - Systems Integration		Saepio Technologies

Re: Amanda Backup Strategy

[Ralph Bearpark]

> Linebreaks, man, use some line breaks...

Sorry, dude, sorry...

> Not that I know of, but in the 2.4.4 ReleaseNotes it says 
> that it tries to 
> reduce the number of level 0s per host each night.

I guess that *might* help.  I could probably get it down to 
a full backup every week.  Would I just need 2.4.4 on the 
server?  Or the clients too?

> If you want amanda to use less disk space, crank down your 
> 'tapelength'.  
> Since you're using diskless backup, you can define whatever 
> size "tapes" 
> you want.

True, but I have 18GB over 30 tapes.  So, to be completely 
safe from Amanda filling the disk with unnecessary full 
backups, I'd have to set the tapelength to 600MB, which, 
unfortunately, wouldn't be enough for any single client full 
backup.

Is there a wishlist for 2.4.5 anywhere?

Regards, Ralph.

Re: Amanda Backup Strategy

[Joshua Baker-LePain]

Linebreaks, man, use some line breaks...

On Wed, 26 Feb 2003 at 4:10am, Ralph Bearpark wrote

> However, when I look an amoverview I see that several disks are getting 
> a full backup EVERY OTHER DAY!  What's the idea of this?  I'll grant 
> it's within the letter of the manual, but it's hardly space-efficient is 
> it?

The goal of amanda is to equalize the amount of data backed up each night 
while staying within the bounds set by dumpcycle, runspercycle, and 
tapecycle.  If this means it promotes dumps, it does it.

> Is there any way I can force amanda to only do the full backup at most 
> n times during the dumpcycle?

Not that I know of, but in the 2.4.4 ReleaseNotes it says that it tries to 
reduce the number of level 0s per host each night.

> Also, I see that other disks are getting repeated level 1 incrementals.  
> I would be happier if it rather did level 1 then 2 then 3 etc. and no 
> backup if no files had changed.  Can I specify this behaviour somehow?

You can play with bumpsize and bumpmult, but the extra hassle restoring 
really isn't worth it, IMO.

> I know it will make a full restore a little messier but I simply don't 
> have unlimited disk space for amanda to use.
> 
If you want amanda to use less disk space, crank down your 'tapelength'.  
Since you're using diskless backup, you can define whatever size "tapes" 
you want.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Amanda Backup Strategy

[Joshua Baker-LePain]

On Wed, 26 Feb 2003 at 10:33am, Ralph Bearpark wrote

> > Not that I know of, but in the 2.4.4 ReleaseNotes it says 
> > that it tries to 
> > reduce the number of level 0s per host each night.
> 
> I guess that *might* help.  I could probably get it down to 
> a full backup every week.  Would I just need 2.4.4 on the 
> server?  Or the clients too?

Just on the server -- that's the job of planner.

> > If you want amanda to use less disk space, crank down your 
> > 'tapelength'.  
> > Since you're using diskless backup, you can define whatever 
> > size "tapes" 
> > you want.
> 
> True, but I have 18GB over 30 tapes.  So, to be completely 
> safe from Amanda filling the disk with unnecessary full 
> backups, I'd have to set the tapelength to 600MB, which, 
> unfortunately, wouldn't be enough for any single client full 
> backup.

Single *client* or single *disk*?  Remember, you can always split up your 
filesystems into multiple disklist entries using tar.  Then you could 
reduce your tapelength to have *just enough* to fit everything once.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Amanda Backup Strategy

[Joshua Baker-LePain]

On Wed, 26 Feb 2003 at 11:05am, Ralph Bearpark wrote

> > Remember, you can always split up your 
> > filesystems into multiple disklist entries using tar.  Then you could 
> > reduce your tapelength to have *just enough* to fit everything once.
> 
> Hmm, dividing my clients into multiple DLEs that I hope will never exceed 
> 600MB ... that's an ugly concept.
> 
> I assume that Amanda is clever enough to not try to put, say, two 500MB 
> DLE backups on a single 600MB tape?

Yep.  Amanda gets estimates for all the DLEs at multiple incremental 
levels, and figures out the "best" thing to do within the tapelength it 
has.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

RE: Amanda Backup Strategy

[Joshua Baker-LePain]

On Wed, 26 Feb 2003 at 11:16am, Ralph Bearpark wrote

> > Yep.  Amanda gets estimates for all the DLEs at multiple incremental 
> > levels, and figures out the "best" thing to do within the 
> > tapelength it has.
> 
> Even to the extent of not doing any sort of backup at all on some or many
> of the DLEs?  If so, how on earth does it decide which?

Yep.  But, when it does that, you'll get big fat warnings such as:

FAILURE AND STRANGE DUMP SUMMARY:
  $CLIENT $DISK lev 1 FAILED [dumps way too big, must skip incremental 
dumps]

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Amanda Backup Strategy

[Ralph Bearpark]

> Remember, you can always split up your 
> filesystems into multiple disklist entries using tar.  Then you could 
> reduce your tapelength to have *just enough* to fit everything once.

Hmm, dividing my clients into multiple DLEs that I hope will never exceed 
600MB ... that's an ugly concept.

I assume that Amanda is clever enough to not try to put, say, two 500MB 
DLE backups on a single 600MB tape?

Regards, Ralph.

RE: Amanda Backup Strategy

[Ralph Bearpark]

> Yep.  Amanda gets estimates for all the DLEs at multiple incremental 
> levels, and figures out the "best" thing to do within the 
> tapelength it has.

Even to the extent of not doing any sort of backup at all on some or many
of the DLEs?  If so, how on earth does it decide which?

(If this is all documented somewhere, please tell me where and I'll stop
asking my stupid questions! :-))

Regards, Ralph.

Re: Amanda Backup Strategy

[Gene Heskett]

On Wed February 26 2003 11:16, Ralph Bearpark wrote:
>> Yep.  Amanda gets estimates for all the DLEs at multiple
>> incremental levels, and figures out the "best" thing to do
>> within the tapelength it has.
>
>Even to the extent of not doing any sort of backup at all on some
> or many of the DLEs?  If so, how on earth does it decide which?

Amanda shouldn't have to deal with that, so the normal "startup" 
procedure is to only give amanda enough acive DLE's to fill a tape 
each night until all have been done, thereby giving amanda some 
help on the initial "balance" settings.  But, if the tapetype is 
properly set, I don't *think* amanda will take a chance on hitting 
EOT as it will delay enough to assure it won't hit EOT.  I've seen 
that in my email from amanda a time or 2.

>(If this is all documented somewhere, please tell me where and
> I'll stop asking my stupid questions! :-))

The only really stupid question is the one not asked. ;-)

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

RE: Amanda Backup Strategy

[Seth, Wayne (Contractor)]

Someone recently recommended "Unix Backup & Recovery" by W. Curtis Preston
to me.  I am just now wading through the amanda section so I cannot tell you
if it's any good.  But, there certainly is a lot of material there!

-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 26, 2003 12:29 PM
To: Ralph Bearpark; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Amanda Backup Strategy


On Wed February 26 2003 11:16, Ralph Bearpark wrote:
>> Yep.  Amanda gets estimates for all the DLEs at multiple
>> incremental levels, and figures out the "best" thing to do
>> within the tapelength it has.
>
>Even to the extent of not doing any sort of backup at all on some
> or many of the DLEs?  If so, how on earth does it decide which?

Amanda shouldn't have to deal with that, so the normal "startup" 
procedure is to only give amanda enough acive DLE's to fill a tape 
each night until all have been done, thereby giving amanda some 
help on the initial "balance" settings.  But, if the tapetype is 
properly set, I don't *think* amanda will take a chance on hitting 
EOT as it will delay enough to assure it won't hit EOT.  I've seen 
that in my email from amanda a time or 2.

>(If this is all documented somewhere, please tell me where and
> I'll stop asking my stupid questions! :-))

The only really stupid question is the one not asked. ;-)

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

Re: Amanda Backup Strategy

[Gene Heskett]

On Wed February 26 2003 17:22, Seth, Wayne (Contractor) wrote:
>Someone recently recommended "Unix Backup & Recovery" by W. Curtis
> Preston to me.  I am just now wading through the amanda section
> so I cannot tell you if it's any good.  But, there certainly is a
> lot of material there!

Yes, and your quoting is broken, making it look as if I wrote both 
you message above, and my message below.  Please adjust your email 
agent.

>-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 26, 2003 12:29 PM
>To: Ralph Bearpark; [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: Amanda Backup Strategy
>
>On Wed February 26 2003 11:16, Ralph Bearpark wrote:
>>> Yep.  Amanda gets estimates for all the DLEs at multiple
>>> incremental levels, and figures out the "best" thing to do
>>> within the tapelength it has.
>>
>>Even to the extent of not doing any sort of backup at all on some
>> or many of the DLEs?  If so, how on earth does it decide which?
>
>Amanda shouldn't have to deal with that, so the normal "startup"
>procedure is to only give amanda enough acive DLE's to fill a tape
>each night until all have been done, thereby giving amanda some
>help on the initial "balance" settings.  But, if the tapetype is
>properly set, I don't *think* amanda will take a chance on hitting
>EOT as it will delay enough to assure it won't hit EOT.  I've seen
>that in my email from amanda a time or 2.
>
>>(If this is all documented somewhere, please tell me where and
>> I'll stop asking my stupid questions! :-))
>
>The only really stupid question is the one not asked. ;-)

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

Re: Amanda Backup Strategy

[Jon LaBadie]

On Wed, Feb 26, 2003 at 11:05:44AM -0500, Ralph Bearpark wrote:
> > Remember, you can always split up your 
> > filesystems into multiple disklist entries using tar.  Then you could 
> > reduce your tapelength to have *just enough* to fit everything once.
> 
> Hmm, dividing my clients into multiple DLEs that I hope will never exceed 
> 600MB ... that's an ugly concept.

I realize that 600MB is 18GB/30 days.  But you needed not set the tapelength
to 600MB.  'tapelength' is not a figure amanda tries to fill.  It is how
much it has to work with.  My tapelength is 12GB.  I average 5-6GB nightly.
But some nights it goes as low as 3GB and the occasional 10GB is seen.

Set your tapelength to some reasonable value, big enough for your large DLE's
plus some for incrementals.

As to those DLE's getting level 0's every other day;  I only recall similar
behavior under two conditions.  If the DLE is very active and level 0 or
level 1 would make little difference, or if the DLE is small and is one
that is promoted quite often to aid "future balancing" of large DLE's.
Because it is a small DLE, the impact is small also.  Is the behavior
of your frequently backed up DLE different?

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

amanda backup hanging consistently

[Orion Poplawski]

Recently the backup of a particular DLE has started hanging consistently.  I
don't see any recent changes on the server except possibly a change from
kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
problem didn't start until June 6th.

The tar command is stuck trying to write out the name of the directory to 
amgtar:

root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .

# strace -f -s 500 -p 11321
strace: Process 11321 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

# strace -f -s 500 -p 11432
strace: Process 11432 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

amgtar is stuck writing output to amandad:

# strace -s 200 -p 11427
strace: Process 11427 attached
write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
2022-05-23 17:31
./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096


amgtar debug has:

Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
/bin/tar
Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
/var/lib/amanda/gnutar-lists
Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM no
Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
bytes written: [0-9][0-9]*
Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
Directory is new$
Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
Directory has been renamed
Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
open conf file
Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
time:
Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL ^Throughput
Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
directory is on a different filesystem; not dumped
Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
ignored$
Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
shrunk by [0-9][0-9]* bytes, padding with zeros
Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
add file .*: No such file or directory$
Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
exit delayed from previous errors
Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: error
Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
"/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
/bin/tar '--version'
Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
"/usr/bin/tar /usr/bin/tar --create --verbose --verbose --block-number --file
- --directory /export/backup/rufous --no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude ." in 
pipeline

amandad debug has:

Tue Jun 14 23:47:14.049156625 2022: pid 11417: ??-amandad   : sending REP pkt:
<
CONNECT DATA 49 MESG 48 INDEX 47 STATE 46
OPTIONS features=9efefbfff3fffbf79f00;
>
Tue Jun 14 23:47:14.049312862

Tapeless Amanda Backup. Please Help?

[Shonne Beavers]

I am trying to configure Amanda for tapeless
backup. When I run, su amanda -c "amcheck DailySet1”
to test; this is what I get.

 

[root@netsaint DailySet1]# su amanda
-c "amcheck DailySet1" 

bash: /root/.bashrc: Permission denied

Amanda Tape Server Host Check

-

Holding disk /usr/amanda: 6761156
KB disk space available, that's plenty

ERROR: no-such-device: No such file or directory

   (expecting a new tape)

NOTE: skipping tape-writable test

NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not
exist

NOTE: it will be created on the next run

NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does
not exist

Server check took 0.001 seconds

 

Amanda Backup Client Hosts Check



Client check: 1 host checked in 0.053 seconds, 0 problems
found

 

(brought to you by Amanda 2.4.2p2)

 

 

Help?

Re: amanda backup status - amstatus

[Olivier Nicole]

> How to verify how much data backed up? Is there anyway
> we can figure out from the amdump.1 log file.

The report that is emailed to you will tell you how much data was
dumped (before and after compression) and how much was saved to tape.

This is in the summary part of the report.

Olivier

Re: Amanda backup server restore

[Olivier Nicole]

> In particular "amadmin export". What I am currently doing is this:
> tar -cpPzf /home/myname/cjs-amback.tar.gz /var/lib/amanda/ /etc/amandahosts
> /etc/amandapass /etc/amanda/ /var/log/amanda/

It's hard for us to say what is in /var/lib/amanda/ or /etc/amanda/ or
/var/log/amanda/

You should save the index directory that is usually in the amanda user
home directory. That you save it one way (tar and scp) or another (amadmin
export) or both, it is up to your policy.

Olivier

RE: Amanda backup server restore

[Gordon J. Mills III]

Olivier Nicole wrote:
> 
> > In particular "amadmin export". What I am currently doing is this:
> > tar -cpPzf /home/myname/cjs-amback.tar.gz /var/lib/amanda/ 
> > /etc/amandahosts /etc/amandapass /etc/amanda/ /var/log/amanda/
> 
> It's hard for us to say what is in /var/lib/amanda/ or 
> /etc/amanda/ or /var/log/amanda/
> 
> You should save the index directory that is usually in the 
> amanda user home directory. That you save it one way (tar and 
> scp) or another (amadmin
> export) or both, it is up to your policy.
> 
> Olivier

Thanks for the info Olivier. What files should I look for to identify the
index directory?

I am running the std debian package and I believe the directories listed are
the right ones. Someone please correct me if I am wrong. 

Thanks,
Gordon 

Re: Amanda backup server restore

[Jon LaBadie]

On Mon, Aug 07, 2006 at 11:18:52AM -0500, Gordon J. Mills III wrote:
> Olivier Nicole wrote:
> > 
> > > In particular "amadmin export". What I am currently doing is this:
> > > tar -cpPzf /home/myname/cjs-amback.tar.gz /var/lib/amanda/ 
> > > /etc/amandahosts /etc/amandapass /etc/amanda/ /var/log/amanda/
> > 
> > It's hard for us to say what is in /var/lib/amanda/ or 
> > /etc/amanda/ or /var/log/amanda/
> > 
> > You should save the index directory that is usually in the 
> > amanda user home directory. That you save it one way (tar and 
> > scp) or another (amadmin
> > export) or both, it is up to your policy.
> > 
> > Olivier
> 
> Thanks for the info Olivier. What files should I look for to identify the
> index directory?
> 
> I am running the std debian package and I believe the directories listed are
> the right ones. Someone please correct me if I am wrong. 
> 

amgetconf  indexdir

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

Re: can amanda backup symlink?

[Frank Smith]

fedora wrote:
> Hi huys..
> 
> I have 2 situations:
> 
> 1) default directory for MySQL is /var/lib/mysql. If this directory is link
> to /var2/db/mysql and if I put /var/lib/mysql in disklist, can amanda do
> backup? I think this should be can backup. May I know which directory is the
> best to put in disklist for this case?

Amanda will back up the link, but you probably want it to back up the data,
so you should use /var2/db/mysql as your disklist entry. Or you may want
both, so if you are rebuilding the entire server you would get the link
as well, but in that case you might want most or all of /var and not just
the database link.
> 
> 2) how about this one. In /var/lib/mysql has databases but certain databases
> in linking to /var3/mysql like:
> 
> lrwxrwxrwx1 root root   42 May 16  2007 AngelClub ->
> /var3/mysql/AngelClub
> drwx--2 mysqlmysql4096 Nov 13 11:55 BabyMobile
> drwx--2 mysqlmysql4096 Nov 13 11:55 BestClub
> 
> If I put only /var/lib/mysql in disklist, can amanda backup for /var3/mysql?
> Or should add both /var/lib/mysql and /var3/mysql in disklist? Please
> advise.

You would need both.  /var/lib/mysql would pick up the BabyMobile and
BestClub databases, but would only record the link to AngelClub and not
the database itself, so you would have to add /var3/mysql/AngelClub to
get that database.

Frank


-- 
Frank Smith  [EMAIL PROTECTED]
Sr. Systems Administrator   Voice: 512-374-4673
Hoover's Online   Fax: 512-374-4501

Re: can amanda backup symlink?

[Chris Hoogendyk]

Frank Smith wrote:

fedora wrote:
  

Hi huys..

I have 2 situations:

1) default directory for MySQL is /var/lib/mysql. If this directory is link
to /var2/db/mysql and if I put /var/lib/mysql in disklist, can amanda do
backup? I think this should be can backup. May I know which directory is the
best to put in disklist for this case?



Amanda will back up the link, but you probably want it to back up the data,
so you should use /var2/db/mysql as your disklist entry. Or you may want
both, so if you are rebuilding the entire server you would get the link
as well, but in that case you might want most or all of /var and not just
the database link.
  

2) how about this one. In /var/lib/mysql has databases but certain databases
in linking to /var3/mysql like:

lrwxrwxrwx1 root root   42 May 16  2007 AngelClub ->
/var3/mysql/AngelClub
drwx--2 mysqlmysql4096 Nov 13 11:55 BabyMobile
drwx--2 mysqlmysql4096 Nov 13 11:55 BestClub

If I put only /var/lib/mysql in disklist, can amanda backup for /var3/mysql?
Or should add both /var/lib/mysql and /var3/mysql in disklist? Please
advise.



You would need both.  /var/lib/mysql would pick up the BabyMobile and
BestClub databases, but would only record the link to AngelClub and not
the database itself, so you would have to add /var3/mysql/AngelClub to
get that database.



This requires just a bit of clarification.

Amanda calls on native tools to do the backups. On Solaris, people 
typically choose to use ufsdump. On Linux, people typically choose to 
use gnutar. So the question depends on the behavior of those tools and 
possibly the parameters Amanda calls them with, though I doubt Amanda 
would call gnutar with --dereference and --create.


ufsdump will faithfully backup a partition. That is, it backs up links 
as links and restores them as links. It backs up mount points as mount 
points and doesn't follow them into other mounted partitions. It deals 
properly with weird things such as doors. So, to paraphrase, when you 
ask ufsdump to do a partition, you get the partition, the whole 
partition, and nothing but the partition.


I'm less familiar with all the gnuances of gnutar, and some people will 
substitute star or a wrapper of their own. But gnutar will typically 
backup a symlink as a symlink, though it has parameters that can be 
tweaked to do otherwise. Gnutar also typically follows mount points into 
other mounted partitions, though I'm going to take a guess that Amanda 
passes it the parameter that tells it not to do that. It would seem 
contrary to the concept of the way DLE's are configured to have gnutar 
expanding mount points.


Aside from the above, I go along with Frank's response.

In addition, you should read the backup reports. Check the sizes of your 
partitions with `df -k` and then compare those with what the Amanda 
reports as the amount of data having been backed up. See if they make 
sense. And do trial recoveries to confirm that what you think got backed 
up really did get backed up and that you can recover it.


Also, since you are doing mySQL, be sure you are taking into account the 
peculiarities of backing up databases.



---

Chris Hoogendyk

-
  O__   Systems Administrator
 c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst 


<[EMAIL PROTECTED]>

--- 


Erdös 4

Re: can amanda backup symlink?

[Rob Dyke]

These last few weeks we've been using Zmanda to backup our mysql databases, 
replacing the filesystem backups we were doing before.

I recently needed to recover a server using amanda/zmanda. All I had to do for 
the mysql database was create a single user in a newly installed copy of mysql 
before asking Zmanda to restore all data. All data restored to dattabase while 
amanda/gnu-tar restored all the filesystem. Services restarted, backup and 
running.

Have a look at zmanda / amanda in parallel.

Rob

--
Rob Dyke

Technologist
Comwifinet Limited
Office: +44(0)8715206606
Mobile: +44(0)7730496667
http://www.comwifinet.com
mailto://[EMAIL PROTECTED]

- Original Message -
From: "Chris Hoogendyk" <[EMAIL PROTECTED]>
To: "Frank Smith" <[EMAIL PROTECTED]>
Cc: "fedora" <[EMAIL PROTECTED]>, amanda-users@amanda.org
Sent: Wednesday, November 21, 2007 2:04:12 PM (GMT) Europe/London
Subject: Re: can amanda backup symlink?



Frank Smith wrote:
> fedora wrote:
>   
>> Hi huys..
>>
>> I have 2 situations:
>>
>> 1) default directory for MySQL is /var/lib/mysql. If this directory is link
>> to /var2/db/mysql and if I put /var/lib/mysql in disklist, can amanda do
>> backup? I think this should be can backup. May I know which directory is the
>> best to put in disklist for this case?
>> 
>
> Amanda will back up the link, but you probably want it to back up the data,
> so you should use /var2/db/mysql as your disklist entry. Or you may want
> both, so if you are rebuilding the entire server you would get the link
> as well, but in that case you might want most or all of /var and not just
> the database link.
>   
>> 2) how about this one. In /var/lib/mysql has databases but certain databases
>> in linking to /var3/mysql like:
>>
>> lrwxrwxrwx1 root root   42 May 16  2007 AngelClub ->
>> /var3/mysql/AngelClub
>> drwx--2 mysqlmysql4096 Nov 13 11:55 BabyMobile
>> drwx--2 mysqlmysql4096 Nov 13 11:55 BestClub
>>
>> If I put only /var/lib/mysql in disklist, can amanda backup for /var3/mysql?
>> Or should add both /var/lib/mysql and /var3/mysql in disklist? Please
>> advise.
>> 
>
> You would need both.  /var/lib/mysql would pick up the BabyMobile and
> BestClub databases, but would only record the link to AngelClub and not
> the database itself, so you would have to add /var3/mysql/AngelClub to
> get that database.


This requires just a bit of clarification.

Amanda calls on native tools to do the backups. On Solaris, people 
typically choose to use ufsdump. On Linux, people typically choose to 
use gnutar. So the question depends on the behavior of those tools and 
possibly the parameters Amanda calls them with, though I doubt Amanda 
would call gnutar with --dereference and --create.

ufsdump will faithfully backup a partition. That is, it backs up links 
as links and restores them as links. It backs up mount points as mount 
points and doesn't follow them into other mounted partitions. It deals 
properly with weird things such as doors. So, to paraphrase, when you 
ask ufsdump to do a partition, you get the partition, the whole 
partition, and nothing but the partition.

I'm less familiar with all the gnuances of gnutar, and some people will 
substitute star or a wrapper of their own. But gnutar will typically 
backup a symlink as a symlink, though it has parameters that can be 
tweaked to do otherwise. Gnutar also typically follows mount points into 
other mounted partitions, though I'm going to take a guess that Amanda 
passes it the parameter that tells it not to do that. It would seem 
contrary to the concept of the way DLE's are configured to have gnutar 
expanding mount points.

Aside from the above, I go along with Frank's response.

In addition, you should read the backup reports. Check the sizes of your 
partitions with `df -k` and then compare those with what the Amanda 
reports as the amount of data having been backed up. See if they make 
sense. And do trial recoveries to confirm that what you think got backed 
up really did get backed up and that you can recover it.

Also, since you are doing mySQL, be sure you are taking into account the 
peculiarities of backing up databases.


---

Chris Hoogendyk

-
   O__   Systems Administrator
  c/ /'_ --- Biology & Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst 

<[EMAIL PROTECTED]>

--- 

Erdös 4

Re: can amanda backup symlink?

[Frank Smith]

Chris Hoogendyk wrote:
> 
> Frank Smith wrote:
>> fedora wrote:
>>   
>>> Hi huys..
>>>
>>> I have 2 situations:
>>>
>>> 1) default directory for MySQL is /var/lib/mysql. If this directory is link
>>> to /var2/db/mysql and if I put /var/lib/mysql in disklist, can amanda do
>>> backup? I think this should be can backup. May I know which directory is the
>>> best to put in disklist for this case?
>>> 
>> Amanda will back up the link, but you probably want it to back up the data,
>> so you should use /var2/db/mysql as your disklist entry. Or you may want
>> both, so if you are rebuilding the entire server you would get the link
>> as well, but in that case you might want most or all of /var and not just
>> the database link.
>>   
>>> 2) how about this one. In /var/lib/mysql has databases but certain databases
>>> in linking to /var3/mysql like:
>>>
>>> lrwxrwxrwx1 root root   42 May 16  2007 AngelClub ->
>>> /var3/mysql/AngelClub
>>> drwx--    2 mysqlmysql4096 Nov 13 11:55 BabyMobile
>>> drwx--2 mysqlmysql4096 Nov 13 11:55 BestClub
>>>
>>> If I put only /var/lib/mysql in disklist, can amanda backup for /var3/mysql?
>>> Or should add both /var/lib/mysql and /var3/mysql in disklist? Please
>>> advise.
>>> 
>> You would need both.  /var/lib/mysql would pick up the BabyMobile and
>> BestClub databases, but would only record the link to AngelClub and not
>> the database itself, so you would have to add /var3/mysql/AngelClub to
>> get that database.
> 
> 
> This requires just a bit of clarification.
> 
> Amanda calls on native tools to do the backups. On Solaris, people 
> typically choose to use ufsdump. On Linux, people typically choose to 
> use gnutar. So the question depends on the behavior of those tools and 
> possibly the parameters Amanda calls them with, though I doubt Amanda 
> would call gnutar with --dereference and --create.
> 
> ufsdump will faithfully backup a partition. That is, it backs up links 
> as links and restores them as links. It backs up mount points as mount 
> points and doesn't follow them into other mounted partitions. It deals 
> properly with weird things such as doors. So, to paraphrase, when you 
> ask ufsdump to do a partition, you get the partition, the whole 
> partition, and nothing but the partition.
> 
> I'm less familiar with all the gnuances of gnutar, and some people will 
> substitute star or a wrapper of their own. But gnutar will typically 
> backup a symlink as a symlink, though it has parameters that can be 
> tweaked to do otherwise. Gnutar also typically follows mount points into 
> other mounted partitions, though I'm going to take a guess that Amanda 
> passes it the parameter that tells it not to do that. It would seem 
> contrary to the concept of the way DLE's are configured to have gnutar 
> expanding mount points.

Yes, tar can follow links, but Amanda calls it with the --one-file-system
option so it won't cross filesystem boundariea.

Frank

> 
> Aside from the above, I go along with Frank's response.
> 
> In addition, you should read the backup reports. Check the sizes of your 
> partitions with `df -k` and then compare those with what the Amanda 
> reports as the amount of data having been backed up. See if they make 
> sense. And do trial recoveries to confirm that what you think got backed 
> up really did get backed up and that you can recover it.
> 
> Also, since you are doing mySQL, be sure you are taking into account the 
> peculiarities of backing up databases.
> 
> 
> ---
> 
> Chris Hoogendyk
> 
> -
>O__   Systems Administrator
>   c/ /'_ --- Biology & Geology Departments
>  (*) \(*) -- 140 Morrill Science Center
> ~~ - University of Massachusetts, Amherst 
> 
> <[EMAIL PROTECTED]>
> 
> --- 
> 
> Erdös 4
> 
> 


-- 
Frank Smith  [EMAIL PROTECTED]
Sr. Systems Administrator   Voice: 512-374-4673
Hoover's Online   Fax: 512-374-4501

Amanda Backup anomaly at 2GB

[Wood, Sid]

I have been using Amanda (version 2.4.1p1) for about three years as the tool
with which I backup my servers. Currently I backup an NCR 4400 server
(MP-RAS 3.02) to an internal DLT-7000. In the past I had experienced
infrequent errors (vxdump returned 3), but recently a puzzling anomaly has
surfaced.

Here is an extraction from the mail report:

*** THE DUMPS DID NOT FINISH PROPERLY!

*** A TAPE ERROR OCCURRED: [[closing tape: I/O error]].
*** PERFORMED ALL DUMPS TO HOLDING DISK.

THESE DUMPS WERE TO DISK. Flush them onto tape DAILY07 or a new tape.
Tonight's dumps should go onto 1 tape: DAILY08.

FAILURE AND STRANGE DUMP SUMMARY:
 /online lev 0 FAILED [out of tape]
taper: FATAL syncpipe_get: w: unexpected EOF

This has happened five times over the past two months. I have researched the
logs for some pattern, expecting that another cron might be interferring,
but that is not the case.

The only common factor I have been able to identify is that the error always
occurs when trying to write a file to the tape which would cross the 2GB
boundary. (My holding disk is 5GB and I'm using DLTIV tapes in a DLT7000
drive. A full backup takes about 18GB of tape space.) It appears as though
Amanda thinks the 35GB tape will hold only 2GB.

The manner in which Amanda sequences filesystems for backup means that it
frequently takes a different number of filesystems (disks ala. amanda) to
reach the 2GB boundary, and they are not always the same filesystems. But
the error, if it happens, always occurs if the next file would cross the
2GB boundary.

Has anyone else experienced this 2GB hiccup?
If so, what is the cause, and how was it resolved?

Any help would be greatly appreciated.
Thanks,
Sid Wood
[EMAIL PROTECTED]

AW: amanda backup setup failing

[christian . weiss]

Hi "Thing",

the Amanda-FAQ says:
---schnipp---
Q: Why does `amcheck' say `access as  not allowed...'

A: There must be something wrong with .amandahosts configuration (or
.rhosts, if you have configured --without-amandahosts).

   First, if the  is not what you expect (i.e., not what you
have specified in the --with-user flag, at configure time), check the
inetd configuration file: you must have specified the wrong username
there.

   Make sure you specify the names exactly as they appear in the error
message after the `@' sign in .amandahosts/.rhosts.  You'll need a
fully-qualified domain name or not, depending on how your client
resolves IP addresses to host names.
---schnapp---

So create the file ".amandahosts" in your Amanda-Homedirectory with the
entry "kascha backup". - If configured --without-amandahosts put the string
in ".rhosts". Then perform a "amcheck -c config".
Maybe you have to add your clients/hosts to "/etc/hosts".

Good luck,

Christian Weiss
Mobile Applications Central Services
Business Unit Communications

MATERNA Information & Communications
Voßkuhle 37, 44141 Dortmund, Germany
www.materna.de - www.annyway.com

Phone:  +49 (0) 231 / 5599-8382
PC-Fax: +49 (0) 231 / 5599-678382
eMail: [EMAIL PROTECTED]



> -Ursprüngliche Nachricht-
> Von: thing [mailto:[EMAIL PROTECTED]]
> Gesendet: Montag, 26. März 2001 11:40
> An: undisclosed-recipients
> Betreff: amanda backup setup failing
> 
> 
> anybody have any idea why?
> 
> I get the email below, it runs from cron as "backup"
> 
> I suspect permissions on the partitions, however I cannot 
> find anything
> in the docs or web site to give me a clue, so im almost 
> ending up making
> the user backup the same group as root to allow access, this seems
> excessive. Any ideas please?
> 
> Thing
> 
> 
> These dumps were to tape kaitlin02.
> Tonight's dumps should go onto 1 tape: a new tape.
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   kascha /dev/sdb2 lev 0 FAILED [kascha: [access as backup not
> allowed from backup@kascha]
>   kascha /dev/sdb1 lev 0 FAILED [kascha: [access as backup not
> allowed from backup@kascha]
>   kascha /dev/sda1 lev 0 FAILED [kascha: [access as backup not
> allowed from backup@kascha]
> 
> 
> STATISTICS:
>   Total   Full  Daily
>       
> Dump Time (hrs:min)0:00   0:00   0:00   (0:00 start,
> 0:00 idle)
> Output Size (meg)   0.00.00.0
> Original Size (meg) 0.00.00.0
> Avg Compressed Size (%) -- -- --
> Tape Used (%)   0.00.00.0
> Filesystems Dumped0  0  0
> Avg Dump Rate (k/s) -- -- --
> Avg Tp Write Rate (k/s) -- -- --
> 
> 
> NOTES:
>   planner: Adding new disk kascha:/dev/sda1.
>   planner: Adding new disk kascha:/dev/sdb1.
>   planner: Adding new disk kascha:/dev/sdb2.
>   driver: WARNING: got empty schedule from planner
>   taper: tape kaitlin02 kb 0 fm 0 [OK]
> 

RE: amanda backup setup failing

[m . krips]

hope this helps:

Have a look at the group which owns the device files in /dev/... you want
to
backup.

The backup user must belong to this group to have access to the devices.

bye Mike

Re: amanda backup setup failing

[John R. Jackson]

>/var/backups/.amandahosts has,
>
>localhost backup

Is /var/backups the home directory for "backup"?

Note the message you got:

  access as backup not allowed from backup@kascha

So this says you need this line in .amandahosts:

  kascha backup

>Thing

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: amanda backup setup failing

[thing]

"John R. Jackson" wrote:

> >/var/backups/.amandahosts has,
> >
> >localhost backup
>
> Is /var/backups the home directory for "backup"?

yes under /etc/passwords the permissions of the dir and .amandahosts are
backup:backup

>
>
> Note the message you got:
>
>   access as backup not allowed from backup@kascha
>
> So this says you need this line in .amandahosts:
>
>   kascha backup

doh..

The debian maintainer has put,

"localhost backup", changing to "kascha backup" has got through that
"stage" i have 2 other errors now

:}

will work through them and see what I can find,

thanks for your time,

Thing

Re: amanda backup setup failing

[thing]

"backup" is in /etc/group under the group disks.

disk:x:6:backup and under /dev/ sd??'s are group disk

/var/backups/.amandahosts has,

localhost backup

the holding disk is set to backup:backup

but I dont think its getting that far.

I fogot to mention this is a Debian 2.2r2 machine and im backing up the
server itself

Thing

[EMAIL PROTECTED] wrote:

> hope this helps:
>
> Have a look at the group which owns the device files in /dev/... you want
> to
> backup.
>
> The backup user must belong to this group to have access to the devices.
>
> bye Mike

Amanda Backup with HP Changer

[Martin Brown]

I am running Solaris 8, with Amanda 2.4.2p2

I have a question, when I take my drive offline "mt -f /dev/rmt/0lbn
offline" I'm unable to bring it back online, unless I physically press the
tape load on the changer.

I've tried using amtape, and mt to load a tape from the cartridge. But there
must be an easier way right? :)

Any help would be great, thanks.

Martin Brown
Technical Architect

Tantalus Communications Inc.
500-1122 Mainland Street
Vancouver, BC, Canada V6B 5L1
[EMAIL PROTECTED]

Direct  (604) 721-0351
Main(604) 609-0700
Fax (604) 609-0705
Toll Free   1-877-326-6776

http://www.tantalus.com
"The Oracle Experts."

Amanda Backup Client Host Check

[O-Zone]

Hi All,
i've just solved any problems with conf but i have a new worry...when i'm 
running amcheck it say to me:

ERROR: moon: [access as backup not alloweb from [EMAIL PROTECTED]] open 
of /home/backup/.amandahost failed

Why ?
-- 

O-Zone 2001 !
WEB @ www.zerozone.it 
Key fingerprint = BF36 D825 283A 9493 4513  E809 6F1B 9F14 DAE5 0C48
[expires: 2003-04-19]

Amanda Backup taking to long

[Kathy Ange]

I am a newbie, I have just run my fist dump on the
server only, and it is taking way to long.  So I
figure I have something configured incorrectly.  I
tried looking in FAQ but didn't see anything, so here
I am.  I know it takes to long As I ran a manual
backup (ufsdump line commands) of the same area and it
only took 12 minutes,using amanda over 90 minutes.

I am running on Solaris 8, with a Sony AIT-2 tape
drive, and the server is an E250.

Here is my amanda.conf file
org "daily" # your organization name for reports
mailto "kange amanda"   # space separated list of
operators at your site
dumpuser "amanda"   # the user to run dumps under
inparallel 4# maximum dumpers that will run in
parallel (max 63)
netusage  2000 Kbps # maximum net bandwidth for
Amanda, in KB per sec
dumpcycle 1 weeks   # the number of days in the normal
dump cycle
runspercycle 6  # the number of amdump runs in
dumpcycle days
tapecycle 10 tapes  # the number of tapes in rotation
bumpsize 50 Mb  # minimum savings (threshold) to bump
level 1 -> 2
bumpdays 2  # minimum days at each level
bumpmult 2  # threshold = bumpsize *
bumpmult^(level-1)
etimeout 300# number of seconds per filesystem for
estimates.
dtimeout 1800   # number of idle seconds before a dump
is aborted.
ctimeout 30 # maximum number of seconds that amcheck
waits
tapebufs 20
runtapes 1  # number of tapes to be used in a single
run of amdump
tapedev "/dev/rmt/1bn"  # the no-rewind tape device to
be used
tapetype Sony-AIT-2 # what kind of tape it is (see
tapetypes below)
labelstr "^Sun[0-9][0-9][0-9]*$"# label constraint
regex: all tapes must match
holdingdisk hd1 {
comment "main holding disk"
directory "/AMANDA/hold"# where the holding disk
is
use 2 Gb# how much space can we use on it
# a non-positive value means:
#use all space but that value
chunksize 1Gb   # size of chunk if you want big
dump to be
# dumped on multiple files on holding disks
#  N Kb/Mb/Gb split images in chunks of size N
# The maximum value should be
# (MAX_FILE_SIZE - 1Mb)
#  0  same as INT_MAX bytes
}

infofile "/var/adm/amanda/daily/curinfo"# database
DIRECTORY
logdir   "/var/adm/amanda/daily"# log directory
indexdir "/var/adm/amanda/daily/index"  # index
directory

define tapetype Sony-AIT-2 {
comment "SDX-500C"
length 54538 mbytes
filemark 1541 kbytes
speed 2920 kbytes   # dito
}

define dumptype global {
comment "Global definitions"
}
#  Amanda Server Dump Types ##
# this is for regular partitions on the amanda server
define dumptype Scomp {
comment "Amanda Server filesystem"
compress server best
index yes
strategy standard 
priority medium 
}

#This is for the root direct, because that is where
the holding disk is
define dumptype Scomp-nohold {
comment "Amanda Server root filesystem straight to
tape"
compress server best
index yes
strategy standard 
holdingdisk no
priority medium 
}

Here is my disklist file
# hostname  diskdevice  dumptypespindle interface
strawbwrries/export/homeScomp
strawberries/   Scomp-nohold

Any suggestion would be appreciated


=
Kathy Ange
Virginia Department of Agriculture & Consumer Services
Information Systems
(804) 786-1340 Voice Mail
(804) 786-2110 FAX

__
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com

Re: non-amanda backup recommendations

[Joseph Sirucka]

Hi Matthew

there is afbackup that will allow you to span tapes.

afbackup.sourceforge.net

As for support, its woeful, the mailing list is pretty dead and support
via the author is non-existant.

I am currently running  amanda alongside afbackup, till one day I figure
how afbackup works properly.

Unless for some miracle amanda allows tape spanning sometime soon,
amanda is good, but lacks the one need I think a majority of people
require tape spanning.

As for commercial, try netbackup, but be prepared to PAY!.

regards

Joseph

On Wed, 2002-12-18 at 02:36, Matthew Boeckman wrote:
> As anathema as this question might be:
> 
>   I need to recommend a Linux backup solution (or a backup
> solution with 
> a Linux client) that will span tapes. Are there any recommendations from
> 
> the list on commercial options?
> 
> Thanks.

Re: amanda backup hanging consistently

[Orion Poplawski]

On 6/15/22 09:38, Orion Poplawski wrote:
> Recently the backup of a particular DLE has started hanging consistently.  I
> don't see any recent changes on the server except possibly a change from
> kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
> problem didn't start until June 6th.
> 
> The tar command is stuck trying to write out the name of the directory to 
> amgtar:
> 
> root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> --verbose --verbose --block-number --file - --directory /export/backup/rufous
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
> --verbose --verbose --block-number --file - --directory /export/backup/rufous
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .
> 
> # strace -f -s 500 -p 11321
> strace: Process 11321 attached
> write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> 
> # strace -f -s 500 -p 11432
> strace: Process 11432 attached
> write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> 
> amgtar is stuck writing output to amandad:
> 
> # strace -s 200 -p 11427
> strace: Process 11427 attached
> write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
> 2022-05-23 17:31
> ./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
> orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096
> 
> 
> amgtar debug has:
> 
> Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
> euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
> Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
> Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
> Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
> euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
> Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
> /bin/tar
> Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
> /var/lib/amanda/gnutar-lists
> Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM 
> no
> Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
> Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
> Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
> Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
> Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
> Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
> Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
> Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
> bytes written: [0-9][0-9]*
> Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
> Directory is new$
> Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
> Directory has been renamed
> Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
> open conf file
> Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
> time:
> Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL 
> ^Throughput
> Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
> directory is on a different filesystem; not dumped
> Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
> ignored$
> Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
> shrunk by [0-9][0-9]* bytes, padding with zeros
> Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
> add file .*: No such file or directory$
> Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
> exit delayed from previous errors
> Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: 
> error
> Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
> "/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
> Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
> /bin/tar '--version'
> Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
> "/usr/bin/tar /usr/bin/tar --create --verbose --verbose --block-number --file
> - --directory /export/backup/rufous --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude ." in 
> pipeline
> 
> amandad debug has:

Re: amanda backup hanging consistently

[Jose M Calhariz]

Hi,


If you run tar by hand on the DLE does it finish?  After how much time?

Kind regards
Jose M Calhariz


On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:
> On 6/15/22 09:38, Orion Poplawski wrote:
> > Recently the backup of a particular DLE has started hanging consistently.  I
> > don't see any recent changes on the server except possibly a change from
> > kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
> > problem didn't start until June 6th.
> > 
> > The tar command is stuck trying to write out the name of the directory to 
> > amgtar:
> > 
> > root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory 
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> > --ignore-failed-read --totals --exclude-from
> > /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> > root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory 
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> > --ignore-failed-read --totals --exclude-from
> > /var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .
> > 
> > # strace -f -s 500 -p 11321
> > strace: Process 11321 attached
> > write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> > 
> > # strace -f -s 500 -p 11432
> > strace: Process 11432 attached
> > write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59
> > 
> > amgtar is stuck writing output to amandad:
> > 
> > # strace -s 200 -p 11427
> > strace: Process 11427 attached
> > write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
> > 2022-05-23 17:31
> > ./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
> > orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096
> > 
> > 
> > amgtar debug has:
> > 
> > Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid > > 0
> > euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
> > Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
> > Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 
> > 156
> > Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid > > 0
> > euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
> > Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
> > /bin/tar
> > Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
> > /var/lib/amanda/gnutar-lists
> > Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : 
> > ONE-FILE-SYSTEM no
> > Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
> > Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
> > Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE 
> > no
> > Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
> > Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
> > Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
> > Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
> > Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
> > bytes written: [0-9][0-9]*
> > Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
> > Directory is new$
> > Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
> > Directory has been renamed
> > Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could 
> > not
> > open conf file
> > Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL 
> > ^Elapsed time:
> > Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL 
> > ^Throughput
> > Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
> > directory is on a different filesystem; not dumped
> > Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
> > ignored$
> > Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File 
> > .*
> > shrunk by [0-9][0-9]* bytes, padding with zeros
> > Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
> > add file .*: No such file or directory$
> > Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
> > exit delayed from previous errors
> > Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: 
> > error
> > Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
> > "/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
> > Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
> > /bin/tar '--version'
> > Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar

Re: amanda backup hanging consistently

[Orion Poplawski]

On 6/17/22 04:25, Jose M Calhariz wrote:

Hi,


If you run tar by hand on the DLE does it finish?  After how much time?


Thanks for the suggestion.  That made me notice that it was bogging down 
dealing with a *very* deep directory that had been created by a buggy 
process going into infinite recursion.  Removing that appears to have 
fixed the dump.


Still seems like there is an issue with amanda not cleaning up properly 
from the timeout condition though.




On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:

On 6/15/22 09:38, Orion Poplawski wrote:

Recently the backup of a particular DLE has started hanging consistently.  I
don't see any recent changes on the server except possibly a change from
kernel 3.10.0-1160.62.1.el7 to 3.10.0-1160.66.1.el7 on Jun 2nd, but the
problem didn't start until June 6th.

The tar command is stuck trying to write out the name of the directory to 
amgtar:

root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/tar --create
--verbose --verbose --block-number --file - --directory /export/backup/rufous
--no-check-device --listed-incremental
/var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
--ignore-failed-read --totals --exclude-from
/var/log/amanda/amgtar._export_backup_rufous.20220614234714.exclude .

# strace -f -s 500 -p 11321
strace: Process 11321 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

# strace -f -s 500 -p 11432
strace: Process 11432 attached
write(2, " ./export/home/orion-admin/ansible-boulder/.git/objects/db/", 59

amgtar is stuck writing output to amandad:

# strace -s 200 -p 11427
strace: Process 11427 attached
write(4, "e_pylibssh.libs/\ndrwxr-x--- orion-admin/orion-admin 0
2022-05-23 17:31
./export/home/orion-admin/.local/lib/python3.8/site-packages/bcrypt/\ndrwxr-x---
orion-admin/orion-admin 0 2022-05-23 17:3"..., 4096


amgtar debug has:

Tue Jun 14 23:47:14.104627682 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: start at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.104731978 2022: pid 11427: ??-amgtar   : version 3.6.0
Tue Jun 14 23:47:14.104957990 2022: pid 11427: ??-amgtar   : state_stream: 156
Tue Jun 14 23:47:14.110961812 2022: pid 11427: ??-amgtar   : pid 11427 ruid 0
euid 27120 ppid 11418 version 3.6.0: rename at Tue Jun 14 23:47:14 2022
Tue Jun 14 23:47:14.110991922 2022: pid 11427: ??-amgtar   : GNUTAR-PATH 
/bin/tar
Tue Jun 14 23:47:14.111004028 2022: pid 11427: ??-amgtar   : GNUTAR-LISTDIR
/var/lib/amanda/gnutar-lists
Tue Jun 14 23:47:14.111013955 2022: pid 11427: ??-amgtar   : ONE-FILE-SYSTEM no
Tue Jun 14 23:47:14.111023583 2022: pid 11427: ??-amgtar   : SPARSE yes
Tue Jun 14 23:47:14.111033039 2022: pid 11427: ??-amgtar   : NO-UNQUOTE no
Tue Jun 14 23:47:14.111042417 2022: pid 11427: ??-amgtar   : ATIME-PRESERVE no
Tue Jun 14 23:47:14.111051865 2022: pid 11427: ??-amgtar   : ACLS no
Tue Jun 14 23:47:14.111061481 2022: pid 11427: ??-amgtar   : SELINUX no
Tue Jun 14 23:47:14.21121 2022: pid 11427: ??-amgtar   : XATTRS no
Tue Jun 14 23:47:14.30900 2022: pid 11427: ??-amgtar   : CHECK-DEVICE no
Tue Jun 14 23:47:14.40474 2022: pid 11427: ??-amgtar   : SIZE ^ *Total
bytes written: [0-9][0-9]*
Tue Jun 14 23:47:14.50269 2022: pid 11427: ??-amgtar   : IGNORE :
Directory is new$
Tue Jun 14 23:47:14.59886 2022: pid 11427: ??-amgtar   : IGNORE :
Directory has been renamed
Tue Jun 14 23:47:14.69511 2022: pid 11427: ??-amgtar   : NORMAL ^could not
open conf file
Tue Jun 14 23:47:14.79212 2022: pid 11427: ??-amgtar   : NORMAL ^Elapsed 
time:
Tue Jun 14 23:47:14.111309287 2022: pid 11427: ??-amgtar   : NORMAL ^Throughput
Tue Jun 14 23:47:14.111321160 2022: pid 11427: ??-amgtar   : NORMAL :
directory is on a different filesystem; not dumped
Tue Jun 14 23:47:14.111331690 2022: pid 11427: ??-amgtar   : NORMAL : socket
ignored$
Tue Jun 14 23:47:14.111342121 2022: pid 11427: ??-amgtar   : NORMAL : File .*
shrunk by [0-9][0-9]* bytes, padding with zeros
Tue Jun 14 23:47:14.111397543 2022: pid 11427: ??-amgtar   : NORMAL : Cannot
add file .*: No such file or directory$
Tue Jun 14 23:47:14.111407572 2022: pid 11427: ??-amgtar   : NORMAL : Error
exit delayed from previous errors
Tue Jun 14 23:47:14.111417962 2022: pid 11427: ??-amgtar   : ERROR amgtar: error
Tue Jun 14 23:47:14.114473250 2022: pid 11427: ??-amgtar   : Spawning
"/bin/tar /bin/tar -x --no-check-device -f -" in pipeline
Tue Jun 14 23:47:14.124455374 2022: pid 11431: ??-amgtar   : Executing:
/bin/tar '--version'
Tue Jun 14 23:47:14.126144343 2022: pid 11427: ??-amgtar   : Spawning
"/usr/bin/tar /usr/bin/t

Amanda Backup fails possible card errors

[Ram Smith]

Hi List,

Overview


I am running Amanda on a GNU/Linux Debian Sarge instalation. Amanda version is 
2.4.4p3-3 . The kernel is 2.6.18-4-686.

And here is some output from boot up referencing the scsi card and tape drive:

-- start
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0

aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

  Vendor: SONY  Model: SDT-11000 Rev: 0200
  Type:   Sequential-Access  ANSI SCSI revision: 02
 target0:0:0: Beginning Domain Validation
 target0:0:0: wide asynchronous
 target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
 target0:0:0: Domain Validation skipping write tests
 target0:0:0: Ending Domain Validation

-- end

The tape drive is a few years old the rest of the hardware is brand new. 

Problem
===

Whenever i run an amanda backup around 30mins into the run I get the following 
errors in the logs. I've included  a few extra unrelated lines at the beginning 
to give some context. 

>From what i can see something bad happened, an attempt was made to reset and 
>the SCSI card went offline.

So i'm finally left with the proverbial question: is it hardware or software?

I guess my question to the list is: what are these error messages saying?

Any help/pointers would be greatly appreciated. 

-- start 
lp0: using parport0 (interrupt-driven).
eth2: no IPv6 routers present
NET: Registered protocol family 5
 target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
st0: Block limits 1 - 16777215 bytes.
st 0:0:0:0: Attempting to queue an ABORT message
CDB: 0xa 0x1 0x0 0x0 0x40 0x0
scsi0: At time of recovery, card was not paused
>>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
scsi0: Dumping Card State in Data-out phase, at SEQADDR 0x1a7
Card was paused
ACCUM = 0x0, SINDEX = 0x20, DINDEX = 0xe4, ARG_2 = 0x0
HCNT = 0xe0 SCBPTR = 0x0
SCSIPHASE[0x0] SCSISIGI[0x4]:(BSYI) ERROR[0x0] 
SCSIBUSL[0xde] LASTPHASE[0x0] SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) 
SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x95]:(SINGLE_EDGE|WIDEXFER) 
SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0x20]:(DPHASE) 
SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x40]:(SHVALID) 
SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP) 
SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) 
SXFRCTL0[0x80]:(DFON) DFCNTRL[0x2c]:(DIRECTION|HDMAEN|SCSIEN) 
DFSTATUS[0x2]:(FIFOFULL) 
STACK: 0x83 0x0 0x164 0x5d
SCB count = 4
Kernel NEXTQSCB = 2
Card NEXTQSCB = 2
QINFIFO entries: 
Waiting Queue entries: 
Disconnected Queue entries: 
QOUTFIFO entries: 
Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 
22 23 24 25 26 27 28 29 3
0 31 
Sequencer SCB Info: 
  0 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x7] SCB_LUN[0x0] 
SCB_TAG[0x3] 
  1 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  2 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  3 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  4 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  5 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  6 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  7 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  8 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
  9 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 10 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 11 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 12 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 13 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 14 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 15 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 16 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 17 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 18 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) 
SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] 
 19 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWI

Re: Amanda Backup anomaly at 2GB

[Johannes Niess]

"Wood, Sid" <[EMAIL PROTECTED]> writes:

> I have been using Amanda (version 2.4.1p1) for about three years as the tool
> with which I backup my servers. Currently I backup an NCR 4400 server
> (MP-RAS 3.02) to an internal DLT-7000. In the past I had experienced
> infrequent errors (vxdump returned 3), but recently a puzzling anomaly has
> surfaced.

[...]

> The only common factor I have been able to identify is that the error always
> occurs when trying to write a file to the tape which would cross the 2GB
> boundary. (My holding disk is 5GB and I'm using DLTIV tapes in a DLT7000
> drive. A full backup takes about 18GB of tape space.) It appears as though
> Amanda thinks the 35GB tape will hold only 2GB.
> 
> The manner in which Amanda sequences filesystems for backup means that it
> frequently takes a different number of filesystems (disks ala. amanda) to
> reach the 2GB boundary, and they are not always the same filesystems. But
> the error, if it happens, always occurs if the next file would cross the
> 2GB boundary.
> 
> Has anyone else experienced this 2GB hiccup?
> If so, what is the cause, and how was it resolved?

Sid,

What's the maximum file size limit of your OS? In most cases it boils
down to set chunksize = 1.9 GB for the temporary files in the holding
disk.

Johannes Niess

Re: Amanda Backup anomaly at 2GB

[John R. Jackson]

>*** A TAPE ERROR OCCURRED: [[closing tape: I/O error]].

First, an "I/O error" means an I/O error.  The tape driver either got
a hardware error or didn't like something itself and reported that back
to Amanda.  Amanda never says this itself out of the blue.  I don't see
how 2 GB boundaries could be involved unless your tape driver is broken.

> /online lev 0 FAILED [out of tape]
>taper: FATAL syncpipe_get: w: unexpected EOF

The syncpipe_get error is probably fixed in Amanda 2.4.2.

>... It appears as though Amanda thinks the 35GB tape will hold only 2GB.

What makes you think this?

>The manner in which Amanda sequences filesystems for backup means that it
>frequently takes a different number of filesystems (disks ala. amanda) to
>reach the 2GB boundary, and they are not always the same filesystems. But
>the error, if it happens, always occurs if the next file would cross the
>2GB boundary.

Could you elaborate, i.e. with a sample sequence?

>Sid Wood

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: Amanda Backup with HP Changer

[John R. Jackson]

>I have a question, when I take my drive offline "mt -f /dev/rmt/0lbn
>offline" I'm unable to bring it back online, unless I physically press the
>tape load on the changer.

That's perfectly normal.  It (usually) takes physical movement (as in,
inserting the tape in the drive) to get the drive to go through its
load cycle.

What changer software are you using?  If you have software that lets
you move a tape from one slot to another (e.g. mtx), you could tell it
to move the tape drive to the tape drive (e.g. move slot 1 to slot 1).
On my robot that causes the gripper to grab the tape, pull it out of
the drive, then put it back in which causes the drive to reload it.

>Martin Brown

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: Amanda Backup with HP Changer

[Martin Brown]

I compiled and installed mtx, that seemed to work. Thanks John.

- Original Message -
From: "John R. Jackson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, September 10, 2001 3:45 PM
Subject: Re: Amanda Backup with HP Changer


> >I have a question, when I take my drive offline "mt -f /dev/rmt/0lbn
> >offline" I'm unable to bring it back online, unless I physically press
the
> >tape load on the changer.
>
> That's perfectly normal.  It (usually) takes physical movement (as in,
> inserting the tape in the drive) to get the drive to go through its
> load cycle.
>
> What changer software are you using?  If you have software that lets
> you move a tape from one slot to another (e.g. mtx), you could tell it
> to move the tape drive to the tape drive (e.g. move slot 1 to slot 1).
> On my robot that causes the gripper to grab the tape, pull it out of
> the drive, then put it back in which causes the drive to reload it.
>
> >Martin Brown
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>

Re: Amanda Backup Client Host Check

[Frank Smith]

--On Monday, October 14, 2002 16:57:56 +0200 O-Zone <[EMAIL PROTECTED]> wrote:

> Hi All,
> i've just solved any problems with conf but i have a new worry...when i'm
> running amcheck it say to me:
>
> ERROR: moon: [access as backup not alloweb from [EMAIL PROTECTED]] open
> of /home/backup/.amandahost failed
>
> Why ?

Because Amanda couldn't open the file /home/backup/.amandahost to see who to
allow connections from.  Make sure it exists, is mode 400 or 600, and is
owned by your backup user.

Frank

> --
>
> O-Zone 2001 !
> WEB @ www.zerozone.it
> Key fingerprint = BF36 D825 283A 9493 4513  E809 6F1B 9F14 DAE5 0C48
> [expires: 2003-04-19]



--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501

Re: Amanda Backup Client Host Check

[Gene Heskett]

On Monday 14 October 2002 10:57, O-Zone wrote:
>Hi All,
>i've just solved any problems with conf but i have a new
> worry...when i'm running amcheck it say to me:
>
>ERROR: moon: [access as backup not alloweb from
> [EMAIL PROTECTED]] open of /home/backup/.amandahost failed
>
>Why ?

Because .amandahosts doesn't exist?  And why is it looking in 
/home/backup for .amandahosts?  It should be looking for 
/home/amanda/.amandahosts.

Sounds like a configuration problem.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.18% setiathome rank, not too shabby for a WV hillbilly

Re: Amanda Backup Client Host Check

[Galen Johnson]

O-Zone wrote:

>Hi All,
>i've just solved any problems with conf but i have a new worry...when i'm 
>running amcheck it say to me:
>
>ERROR: moon: [access as backup not alloweb from [EMAIL PROTECTED]] open 
>of /home/backup/.amandahost failed
>
>Why ?
>  
>
I would guess one of 2 reasons. 1) it doesn't exist. 2) it exists but is 
not owned but your amanda user and has perms set to 600 (or even 640).

=G=

Re: Amanda Backup Client Host Check

[Anthony Valentine]

Would it look in /home/backup if Amanda were compiled with 'backup' as
the amanda user?


On Mon, 2002-10-14 at 07:16, Gene Heskett wrote:
> On Monday 14 October 2002 10:57, O-Zone wrote:
> >Hi All,
> >i've just solved any problems with conf but i have a new
> > worry...when i'm running amcheck it say to me:
> >
> >ERROR: moon: [access as backup not alloweb from
> > [EMAIL PROTECTED]] open of /home/backup/.amandahost failed
> >
> >Why ?
> 
> Because .amandahosts doesn't exist?  And why is it looking in 
> /home/backup for .amandahosts?  It should be looking for 
> /home/amanda/.amandahosts.
> 
> Sounds like a configuration problem.
> 
> -- 
> Cheers, Gene
> AMD K6-III@500mhz 320M
> Athlon1600XP@1400mhz  512M
> 99.18% setiathome rank, not too shabby for a WV hillbilly
-- 
UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things.

RE: Amanda Backup Client Host Check

[Larry Dunham]

Ozone wrote:
> >...ERROR: moon: [access as backup not alloweb from
> > [EMAIL PROTECTED]] open of /home/backup/.amandahost failed
> >
> >Why ?
>


Gene wrote:
> Because .amandahosts doesn't exist?  And why is it looking in
> /home/backup for .amandahosts?  It should be looking for
> /home/amanda/.amandahosts.
>
> Sounds like a configuration problem.
>
> --
> Cheers, Gene


One clarification:  it should only be looking for .amandahosts in
/home/amanda if the backup user  name is amanda.  If the backup user is
called backup then /home/backup would be the correct place for .amandahosts.
Am I correct?

Larry

Re: Amanda Backup Client Host Check

[Christoph Scheeder]

Hi

Larry Dunham schrieb:
> Ozone wrote:
> 
>>>...ERROR: moon: [access as backup not alloweb from
>>>[EMAIL PROTECTED]] open of /home/backup/.amandahost failed
>>>
>>>Why ?
>>
> 
> 
> Gene wrote:
> 
>>Because .amandahosts doesn't exist?  And why is it looking in
>>/home/backup for .amandahosts?  It should be looking for
>>/home/amanda/.amandahosts.
>>
>>Sounds like a configuration problem.
>>
>>--
>>Cheers, Gene
> 
> 
> 
> One clarification:  it should only be looking for .amandahosts in
> /home/amanda if the backup user  name is amanda.  If the backup user is
> called backup then /home/backup would be the correct place for .amandahosts.
> Am I correct?

not always. depends on what is the home directory of the user backup.
it is listed in /etc/passwd ( at least under linux;-)
Christoph