I'm running amanda 2.5.2p1 under NetBSD. since updating, I've been
getting bogus warnings from the planner about overwriting full dumps:
On Wed, Jul 29, 2009 at 04:17:44AM -0700, System Operator wrote:
NOTES:
planner: Last full dump of aragorn.poofy.goof.com:/disk/conraid on tape
DailySetA11 overwritten in 5 runs.
amadmin default find aragorn.poofy.goof.com /disk/conraid :
date host disk lv tape or file file part status
2009-07-17 aragorn.poofy.goof.com /disk/conraid 0 DailySetA16 10 -- OK
2009-07-18 aragorn.poofy.goof.com /disk/conraid 1 DailySetA1 9 -- OK
2009-07-19 aragorn.poofy.goof.com /disk/conraid 1 DailySetA3 5 -- OK
2009-07-20 aragorn.poofy.goof.com /disk/conraid 1 DailySetA4 5 -- OK
2009-07-21 aragorn.poofy.goof.com /disk/conraid 0 DailySetA5 10 -- OK
2009-07-22 aragorn.poofy.goof.com /disk/conraid 1 DailySetA6 10 -- OK
2009-07-23 aragorn.poofy.goof.com /disk/conraid 0 DailySetA7 9 -- OK
2009-07-24 aragorn.poofy.goof.com /disk/conraid 1 DailySetA8 5 -- OK
2009-07-25 aragorn.poofy.goof.com /disk/conraid 1 DailySetA9 5 -- OK
2009-07-26 aragorn.poofy.goof.com /disk/conraid 1 DailySetA10 9 -- OK
2009-07-27 aragorn.poofy.goof.com /disk/conraid 0 DailySetA11 10 -- OK
2009-07-28 aragorn.poofy.goof.com /disk/conraid 1 DailySetA12 9 -- OK
2009-07-29 aragorn.poofy.goof.com /disk/conraid 1 DailySetA13 5 -- OK
my tape numbering is not contiguous. the above is a complete list of
tapes.
from amanda.conf:
dumpcycle 5 days # the number of days in the normal dump cycle
runspercycle 5 # the number of amdump runs in dumpcycle days
tapecycle 13 tapes # the number of tapes in rotation
that's one dump per day, as shown above... how does the planner figure
I'm going to overwrite DailySetA11 in 5 runs? is there something that
needs to be kicked?
