On Fri, Feb 21, 2003 at 02:42:31PM -0800, Jay Lessert wrote:
> > > See also "got result" in amdump.1, it'll tell you if there's any
> > > difference between a level0 and level1 estimate.
> > 
> > planner: time 10.451: got result for host backup disk /dev/hda1: 0 ->
> > 21156480K, 1 -> 19996640K, 2 -> 19996600K
> 
> So it says that all but 1GB of your / has been touched in some way
> since the last level 0.  Assuming this surprises you, then you start
> checking the output of 'find / -mtime' and 'find / -ctime'.  You know
> what the last level 0 date was (because you checked
> dumpdates/amandates),

For the archives...

The sudden jump in the size of this backup was caused when I moved the
holdingdisk.  It didn't occur to me that I was moving it on to the
filesystem I was backing up... :-)  I just added /hold to the exclude
file.  So, backups will shrink dramatically tonight...

I'm still interested in finding out what the flaw in my understanding of
how amanda handles compression is, though.  I'm sure it's something
really obvious that I'm an idiot for not seeing, but I still think my
tapes should be able to hold more than 20GB when compression is being
used.

-- 
John Oliver, CCNA                            http://www.john-oliver.net/
Linux/UNIX/network consulting         http://www.john-oliver.net/resume/
***               sendmail, Apache, ftp, DNS, spam filtering         ***
****                Colocation, T1s, web/email/ftp hosting          ****