Estimate level 0, but ran level 4
Hello, I am having some strange behavoir with amanda. This morning I came in and my level 0 had failed due to the fact that the disk has more data then my tape device is capable of backup up. Thats cool. I tweaked the exclude file to backup only what will fit. I ran amcheck - all good. So here is where it gets weird. I ran amdump and started a new backup. I was watching /tmp/amanda/sendsize.debug to make sure everything is ok. I got the follown output from the estimate: sendsize: getting size via gnutar for sda5 level 0 Total bytes written: 5240483840 (4.9GB, 9.1MB/s) Which is great, expect when it went to actually create the tarball to send it did a level 4 incremental backups: sendsize: getting size via gnutar for sda5 level 4 Total bytes written: 891750400 (850MB, 1.1MB/s) Why did it estimate a full, but actually run a inc? How does one force a full backup with amanda. Andrew Hall
Re: Estimate level 0, but ran level 4
On Apr 6, 2001, [EMAIL PROTECTED] wrote:
Why did it estimate a full, but actually run a inc?
It estimated *both* a full and an inc, and decided to run an inc
because either a full wasn't due or it wouldn't fit.
How does one force a full backup with amanda.
amadmin conf force
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Estimate level 0, but ran level 4
On 6 Apr 2001, Alexandre Oliva wrote: On Apr 6, 2001, [EMAIL PROTECTED] wrote: Why did it estimate a full, but actually run a inc? It estimated *both* a full and an inc, and decided to run an inc because either a full wasn't due or it wouldn't fit. OK. Here is the weird thing. An estimate for the lvl4 was never ran. Just the estimate for the full (4.9G), which will fit on my tape, then the tar for the inc? Is this an error I should be concerned about, or just weird behavior. Andrew
