On Tuesday 25 October 2005 04:08, Paul Bijnens wrote:
>Cameron Matheson wrote:
>> Hi,
>>
>> I just got my tape library back online, and I thought backups should
>> be good to go now, but it seems that maybe all those days that i
>> missed out on backups have confused amanda or something. No backups
>> occured over the weekend (I had changed my crontab to make it run 7
>> days a week), but I didn't get any emails from amanda over the
>> weekend. I tried running 'amadmin DailySet1 balance', and it reports
>> the following:
>>
>> due-date #fs orig KB out KB balance
>> ----------------------------------------------
>> 10/24 Mon 0 0 0 ---
>> 10/25 Tue 0 0 0 ---
>> 10/26 Wed 0 0 0 ---
>> 10/27 Thu 0 0 0 ---
>> 10/28 Fri 20 182596290 182596290 +362.5%
>> 10/29 Sat 6 62085930 62085930 +57.3%
>> 10/30 Sun 4 31671340 31671340 -19.8%
>> ----------------------------------------------
>> TOTAL 30 276353560 276353560 39479080
>> (estimated 7 runs per dumpcycle)
>
>"amadmin xx balance" takes the last dumpcycle, and projects that in the
>future, in the assumption that the dumpcycle will repeat itself again:
>at least, that is what amanda expects to do in the next cycle.
>Note the date column is labeled "due-date".
>
>When amanda runs, it first assumes a full dump of only those that
>are "due". If planner notes that the total of full dumps is a on
>the small side, it looks for "hills" in the future in the dumpcycle,
>and will promote some dumps from those hills for the current run.
>
>The above shows that, if the current dumpcycle is the same as the last
>one, there will be no full dump on the first 4 days, because in the last
>dumpcycle, there was neither a dump in the four last days either,
>be it because it was weekend or because you tapedrive broke, amanda
>doesn't mind: amanda uses the real world facts, and not the theory
>of planning.
>
>The planner will start with 0 due dumps, and will note there is room
>for some more full dums, it looks "ahead" and notices that 10/28 is
>expected to be very busy day, and starts moving full dumps from that
>days to this run, up to about 276353560/7 = 39479080 (total full dumps
>divided by runspercycle).
>
>After another full cycle, the dumps will already be spread better.
>Amanda continuously shuffles the full dumps, aiming at 0% in the
>last column.
Many thanks Paul. A very good explanation indeed. I guess I should 'read
the code' more often. But I'd always wondered how this actually worked and
now I should know. If my wet ram doesn't forget that is. :-)
>> How come there is nothing scheduled for Monday-Friday? My crontab is
>> set back to running amanda Monday-Saturday (does this utitity even
>> read the crontab? I'm not sure how it works). Anyway, I flushed the
>> old backups (from last week) to tape w/ no difficulty, so I think it
>> should be able to dump stuff to tape... I'll run amdump manualy
>> tonight if i can't figure this out, but it would be nice to figure
>> this thing out.
>>
>> Thanks!
>> Cameron Matheson
--
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.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
|
