Jon LaBadie <jon AT jgcomp DOT com> writes:

> On Thu, Feb 03, 2005 at 01:17:10PM +0100, Rainer Hackel wrote:
>> Here an abstract of tho mail reports amanda send after a backup. The first
>> time it makes dumplevel 0 of backupdisk. The second time it makes dumplevel
>> 1 of the same disk. Why differs the size that less? Looks more like if both
>> were complete backups. Someone can help?
>> 
>> -backupdisk 0 20166900 20166900 -- 104:513205.5 39:518434.9
>> 
>> -backupdisk 1 20223440 20223440 -- 93:013623.6 38:498683.2
>
>
> First question has to be, have most of the things on 'backupdisk'
> changed since the level 0?
>
> Might something be causing the ctime of each file to be altered
> so it looks like it has changed?
>
> What is on 'backupdisk'?  Is it, as the name suggests, backups?
> If so, are you backing up your backups?

Another question.  Look at the amdump log file for that date, which
should have a line which looks something like this:

planner: time 3291.422: got result for host condor disk //bunting/c$: 0 -> 
11607069K, 1 -> 1253863K, 2 -> 1253863K

The number after "0 ->" shows the suggested 0 level backup, the number
after "1 ->" shows the 1 level backup, etc.  If level 0 doubled in
size, then a large level 1 is appropriate.  Another possibility,
perhaps the ctime really has changed.  Some of the computers which I
back up have a large amount of data collection, which changes every
day.  Some of the larger data DLEs have been dropped from my backup.
I can't handle 50GB of data from one machine every night with my
current backup hardware, and it really doesn't need backup anyway.


-- 
Kevin Dalley
kevin AT kelphead DOT org