Re: [Duplicity-talk] Understanding Duplicity run report

[edgar . soldin]

On 06.03.2015 11:23, Mikko Ohtamaa wrote:
> Hi all,
> 
> I have the following report from the duplicity from the incremental backup 
> run. Does RawDelta and TotalDestinationSize actually mean that this was the 
> delta amount required to upload and store in the backup?
> 
> Is this so? In my case something is off as, as from 70 GB set almost 69.5 GB 
> would have changed. This cannot be true, as I know that the most of the files 
> are static.
> 
> Using SFTP backend.
> 
> What could cause this behavior?
> 
> I also run the duplicity in verbose mode and it seems to be adding (A) files 
> to the backup which I know have not changed - does this happen for every 
> backed up file or only for new/delta files?
> 
> Cheers,
> Mikko
> 
> --------------[ Backup Statistics ]--------------
> StartTime 1425596471.39 (Fri Mar  6 00:01:11 2015)
> EndTime 1425609804.32 (Fri Mar  6 03:43:24 2015)
> ElapsedTime 13332.93 (3 hours 42 minutes 12.93 seconds)
> SourceFiles 924693
> SourceFileSize 75405362645 (70.2 GB)
> NewFiles 924693
> NewFileSize 75405361109 (70.2 GB)
> DeletedFiles 0
> ChangedFiles 0
> ChangedFileSize 0 (0 bytes)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 924693
> RawDeltaSize 74641311673 (69.5 GB)
> TotalDestinationSizeChange 65357662979 (60.9 GB)
> Errors 0
> -------------------------------------------------
> 
> 
> 

seems like pretty much all files were added 'NewFiles', like they never existed 
in the backup.

are you 100 percent sure you ran an incremental? is it possible that duplicity 
switched to full because the former full was incomplete or broken?

you can run 'verify ' and see what it spits out. it'll tell if files are newer 
or missing.

..ede/duply.net