|
From: | Charles Knowlton |
Subject: | Re: [Duplicity-talk] TotalDestinationSizeChange |
Date: | Fri, 22 Jun 2007 14:42:26 -0500 |
On my backups I have the same issue: --------------[ Backup Statistics ]-------------- StartTime 1182487338.42 (Thu Jun 21 23:42:18 2007) EndTime 1182487753.65 (Thu Jun 21 23:49:13 2007) ElapsedTime 415.23 (6 minutes 55.23 seconds) SourceFiles 120083 SourceFileSize 2462544175 (2.29 GB) NewFiles 998 NewFileSize 35067617 (33.4 MB) DeletedFiles 47 ChangedFiles 2155 ChangedFileSize 76365215 (72.8 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 3200 RawDeltaSize 15041759 (14.3 MB) TotalDestinationSizeChange 39259173 (37.4 MB) Errors 0 ------------------------------------------------- Regards, Charles Knowlton On Jun 15, 2007, at 6:11 AM, Kenneth Loafman wrote:
Axel Beckert wrote:On Thu, Jun 14, 2007 at 09:42:11AM -0500, Kenneth Loafman wrote:On the incremental RDS was much *bigger* than TDSC, but TDSC is what was written to disc.[...] ChangedFiles 2 ChangedFileSize 2434927 (2.32 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2 RawDeltaSize 2297851 (2.19 MB) TotalDestinationSizeChange 562155 (549 KB)This is probably because duplicity compresses the data before encrypting and backupping it. Compressing 2.32 MB down to 549 KB is no problem for e.g. a textual or SQL diff.The first case that Fabiano reported was just the opposite: RawDeltaSize 5877233 (5.60 MB) TotalDestinationSizeChange 104697158 (99.8 MB) I don't think the two are directly related. ...Ken _______________________________________________ Duplicity-talk mailing list address@hidden http://lists.nongnu.org/mailman/listinfo/duplicity-talk
[Prev in Thread] | Current Thread | [Next in Thread] |