On Thursday 03 February 2005 10:27, Rainer Hackel wrote:
>Backupdisk was just a dummy-name. The true name is an other. It's a
>smb-share with office-files on it. I'm sure the users did not touch
> them all... Perhaps any running process??? Other smb-shares from
> the same hosts don't have this problem.

That pretty well explains it then.  Samba doesn't support the ctime 
data so it looks as if its new stuff everytime.

If its not actually on a windows box, but is actually on another 
filesystem, it may be possible to install the amanda client on that 
box, which would alleviate this, and it also enhances the parallelism 
of the amanda run, potentially speeding it up noticably.

I believe too, that there is a windows rsync client, so that if a 
seperate non-samba holding area could be used for rsync to keep 
uptodate, then the holding area rsync uses could be backed up 
instead.  Be aware that rsync, in its runs, makes a backup copy of 
everything, compareing the new and old data block by block by 
checksums, and if the new data is different, subs that block, other 
wise it does a local copy of that block from the old file to the new 
one.  If there were no on the fly edits because that file wasn't 
changed, the new one is deleted on completion of the compare, so 
files that have not changed don't have their ctimes changed.  rsync 
can be a very handy tool at times.

>-----Ursprüngliche Nachricht-----
>Von: owner-amanda-users AT amanda DOT org
> [mailto:owner-amanda-users AT amanda DOT org] Im Auftrag von Jon LaBadie
>Gesendet: Donnerstag, 3. Februar 2005 16:07
>An: amanda-users AT amanda DOT org
>Betreff: Re: no different dumpsize between level 0 and 1
>
>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?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.32% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.