on Tue, 19 Sep 2006 16:13:16 +0200
Paul Bijnens <paul.bijnens AT xplanation DOT com> wrote:
>
> On 2006-09-19 12:34, Charles Stroom wrote:
> > Hi list,
> >
> > when I do "amadmin daily balance", the result is:
> >
> > due-date #fs orig KB out KB balance
> > ----------------------------------------------
> > 9/19 Tue 1 5704660 5704660 +29.6%
> > 9/20 Wed 1 4237300 4237300 -3.7%
> > 9/21 Thu 1 6144730 6144730 +39.6%
> > 9/22 Fri 0 0 0 ---
> > 9/23 Sat 1 1967870 1967870 -55.3%
> > 9/24 Sun 11 4085180 4085180 -7.2%
> > 9/25 Mon 1 8675160 8675160 +97.1%
> > ----------------------------------------------
> > TOTAL 16 30814900 30814900 4402128
> > (estimated 7 runs per dumpcycle)
> >
> > Why would it not plan any backup for 9/22?
>
> Amanda cannot predict the future. But she expects
> that you will schedule runs just like the last
> dumpcycle.
>
> In the above output, that means that you did not
> run any amdump on the 4th day of the dumpcycle,
> and expects that the next cycle will be the same.
>
Dumps are done daily in principle, but actually, 3 days ago,
many DLEs failed to backup with the
FAILED [too many dumper retry: "[request failed: timeout waiting for ACK]"]
message. So, that may be the reason, although it would be a bit
odd that because of a failure to do a backup, no backup is scheduled
in 7 days.
Every now and then (say, 1 in 5), amanda fails to perform backups
with above messages and then the next daily backup works ok.
This was the case with the previous 2.5.1b1-2 and is the same
with my current 2.5.1-1 Suse 10.0 version. Such is life I assume.
There are other reports with a similar failures, so maybe it will
be resolved in a future release.
Thanks for feedback.
Charles Stroom
email: charles at stremen dot xs4all dot nl
|