>I am using tar. Where is this info about each file backed up saved, in
>the amanda db file?
Amanda has nothing to do with it (well, very little). This is purely
up to the backup program.
For dump, it's stored in /etc/dumpdates. For tar, Amanda tells it to keep
"listed-incremental" files in the "listed incremental" directory, which
is defined at the time you run ./configure using --with-gnutar-listdir.
You can see what this is set to with:
amadmin xx version | grep listed_incr_dir
Amanda does very little with these files except some basic maintenance
(removing old ones, creating an empty one for a full dump, etc).
>[the level 0] completly fails.
What incremental level did Amanda do the next day? Did it go back to 1,
or did it repeat whatever it had been doing before the full?
If it went back to 1 when it had been doing something higher, that might
be a bug.
>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? ...
That's correct. Amanda only guarantees it will be at most 7 days between
full dumps of any given file system. It does not guarantee what day in
the cycle, or that it won't get a full dump more often.
>Am I
>correct, and if so how do I force amanda to do a full on the same day
>every week?
Why would you want to do that?
This confuses a lot of people about Amanda. It doesn't matter what day
things happen. Really. I'm not kidding. Trust me. :-)
We (and I include myself, before my Amanda days) are often so used to the
"it's Friday, we should do this" lock-step kind of thinking that it's
hard to let go of. Once you do and let Amanda control things, you'll
wonder why you used to work so hard to fit stuff into a rigid schedule.
>Andrew
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
