Thank you so much for your
help -
Saga - You told me a long time ago
make sure that my tapecycle in the amanda.conf file matched the
number of tapes I was actually using - well I hesitated to make this
change for a few reasons:
1st reason - my immediate supervisor - scolded me several times
on how I couldn't get amanda to do full dumps on weekends and
incrementals during the week - onto the same tape.
then it was that I couldn't get amanda
to do incrementals less the failures we were seeing because of our
lack of holding disk size -with comparison to what we wanted to back up.
28Gb.
And finally because he is the same
supervisor who went ahead and set the tapecycle parameter to 8 in the
amanda.conf file. Who was I to question his changes?
Comments on the below email? I was told that the tapecycle parameter was
to be set to 8.
***********************************************
Date: Thu, 2 Nov 2000 18:12:46 +0000 (GMT)
From: denise's supervisor
Subject: Re: getting amanda to do incementals
On Thu, 2 Nov 2000, Denise Ives wrote:
| -yes I want to be done with getting this thing working
| properly. The dumptype I have set in our disklist file is set to
| always full. I have been told that amanda automatically does
| incremetals based on it balancing algorithyms. What I didn't realize
| and what I think is happening is i have amanda set up to do full dump
| incementals based on my dumptype setting - and that is why we are
| running out of holding space. Is that correct?
You're not doing incrementals. You have configured amanda to do a full
dump every time.
| Would this solution work?
|
| Have a single Amanda configuration with a new dumptype:
|
| define dumptype incremetals {
| global
| comment "Only do incrementals"
| compress none
| strategy nofull
After having read the amanda(8) manpage for a few minutes, it looks to
me like the right thing to do is:
mailto [EMAIL PROTECTED] # We don't need to archive this.
netusage 10000 Kbps # We've got enough bandwidth
dumpcycle 1 week
runspercycle 7
tapecycle 8 tapes # This will give us two months.
This tells amanda by default we want to run do full backups once a week
with incrementals (level 1) every day in between, and that there are 8
tapes in the rotation. This would give us two months worth of data in
regular backups which seems reasonable. Anything we want to archive
forever we can do separately or by hand.
Here's what I want:
Mon-Sat: Incremental dump to holding disk sundev1:/dump (level 1). Do
_not_ include holding disk in incrementals, as you'd be backing up data
twice.
Sun Eve/Mon AM: Full backup of everything but holding disk to tape.
Flush incrementals to tape as well.
Amanda should be able to do this almost in its default mode. You need
to configure a disklist that includes everything except the holding disk
(which is now a separate partition), and create a dumptype that tells
amanda to only flush to tape at the end of the dump cycle.
There's no reason to have to do anything here other than change the tape
once a week. None of this should have to be done manually or require any
babysitting.
Perhaps you should just ask outright on the amanda list how to do this.
I don't really have time to figure this out and we've burned a lot of
cycles on this so far.
---------- Forwarded message ----------
Date: Tue, 14 Nov 2000 18:36:49 -0500
From: John R. Jackson <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Denise Ives <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Wait - are you saying that I don't have to re-label each of my
tapes?
>Wait - are you saying that I don't have to re-label each of my tapes?
That's what I'm saying. I've been telling you all along you're working
too hard at this :-) :-).
Here's the short version:
* Set tapecycle in amanda.conf to the number of tapes you actually
have (four, right?). Don't lie to it :-).
* Run amlabel on them **once** to write the initial label, e.g. daily0,
daily1, daily2, daily3. You might want to use two digits (daily00) on
the off chance you actually get a reasonable amount of tapes someday.
If you've got good data, wait until you need the tape to run amlabel.
* Remove your tapelist file. It's probably pretty confused by now.
* Let Amanda tell you what tape it wants. For the first time
through, it will say it wants "a new tape". Give it the next tape in
the sequence (i.e. daily0 first, then daily1, and so on).
That's it. Once you get through the tapes the first time, Amanda will
just tell you explicitly what it wants.
>***Example: I have tape daily555 in the tape drive right now.
>
>When I run amadmin <conf> tape I get these results:
>
>***********************************************************
>
>amanda@sundev1 [daily] % amadmin daily tape
>The next Amanda run should go onto a new tape.
That's because you have tapecycle set larger than the number of entries
in your tapelist file. It does not actually look at the tape.
>*Example: When I run amcheck - Amanda tells me it
>will not overwrite tape daily555
That's because daily555 is listed in your tapelist file but because you
have not used "tapecycle" tapes yet, it is going to insist on a new tape.
>This is why I have been re-labeling the tapes each time. After I force the
>re-label
>of a tape amflush runs without fail. ...
That's because the tape then looks "new". But you're really confusing
Amanda about where things are.
>I never thought that made any sense - but I guess Amanda doesn't want to
>overwrite good Valid images.
It tries very, very, very hard not to do that.
>Denise E. Ives
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
