On Mon, 30 Apr 2001, John R. Jackson wrote:
> >1) When I run an amflush I notice that the dump are put on tape starting
> >with the smallest and working its way up to the largest last. Why is
> >this?
>
> I suspect the theory is to get as many images safely out to tape as
> quickly as possible.
>
> Would you prefer it was done some other way? Why?
>
This is fine by me, I was just curious.
> >2) When an incremental runs does it do the incremental based on what was
> >on the drive at the completion of the last full, or last incremental if
> >one has run after the full?
>
> That depends on the dump program, not Amanda.
>
> In general, dump programs back up everything that has changed since
> the most recent backup at a lower level. For instance, a level 2 will
> back up everything since the most recent level 1 (a level 3 would also
> back up everything since a level 1 if there had not been any level 2's
> in between).
I am using tar. Where is this info about each file backed up saved, in
the amanda db file?
>
> >3) If a full backup fails, why does amanda continue with an incremental
> >the next day?
>
> What do you mean by "fails"? Did the dump succeed but just not get to
> tape? Or did it totally fall apart?
>
It completly fails.
> Full dumps can shift around in the Amanda cycle. Amanda might decide
> to promote (move earlier in the cycle) a full dump one day but make a
> different decision another day, based on what else was going on.
>
OK. So what I hear is that amanda is not guaranteed to do a level 0 on
the same day in each dumpcycle. So if I have
dumpcycle 7 days
then I might get a lvl 0 on Monday on week, and Wed on the next? Am I
correct, and if so how do I force amanda to do a full on the same day
every week?
Thanks.
Andrew
