[posted and Cc'ed]

On Fri, Feb 21, 2003 at 02:13:26PM -0800, John Oliver wrote:
> > see "GENERATING SCHEDULE" in logdir/amdump.1.
> 
> DUMP backup fffffeff9f00 /dev/hda1 20030221 0 1 2003:2:19:10:38:53 10995392 
> 6305

So 10.9GB on a level 1, right?  And amanda apparently thought that
would *barely* fit, but it didn't.  Make sense?

> > Confirm you've got 'record yes', and that it worked.
> 
> I'm not following.  "Record yes"?  Is that an option somewhere?

Go to your amanda config directory.  Edit amanda.conf.  Search for the
dumptype entry this DLE uses.  Confirm that this dumptype entry says
'record yes' somewhere within it.  Depending on if this dumptype
declares program "DUMP" or "GNUTAR", look at /etc/dumpdates or
/etc/amandates on host backup, confirm the entries for /dev/hda1 are
what you expect.

> > 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),

> > Confirm your dumptype compress is set where you expect for
> > backup:/dev/hda1.
> 
> Again, I'm not sure what you mean by this.  I see:
> 
> [root@backup DailySet1]# grep backup /etc/amanda/DailySet1/disklist
> backup /dev/hda1 comp-root-tar
> 
> Is that what you mean?

Ummm, it's the first step on the path of getting to what I mean.

"comp-root-tar" is just a dumptype entry in your amanda.conf, so you
need to understand what every parameter in that dumptype entry means.

-- 
Jay Lessert                               jay_lessert AT accelerant DOT net
Accelerant Networks Inc.                       (voice)1.503.439.3461
Beaverton OR, USA                                (fax)1.503.466.9472