duplicity-team team mailing list archive

Thread
Date

Re: [Question #193846]: These backup times seem very excessive

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: edso <question193846@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 20 Apr 2012 14:00:57 -0000
Reply-to: question193846@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Question #193846 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/193846

edso proposed the following answer:
On 20.04.2012 15:20, Chris Stankaitis wrote:
> Question #193846 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/193846
> 
> Chris Stankaitis posted a new comment:
> Ok so the upgrade to 0.6.18 has helped a bit...
> 
> --------------[ Backup Statistics ]--------------
> StartTime 1334754015.69 (Wed Apr 18 09:00:15 2012)
> EndTime 1334870565.07 (Thu Apr 19 17:22:45 2012)
> ElapsedTime 116549.39 (32 hours 22 minutes 29.39 seconds)
> SourceFiles 203
> SourceFileSize 319343112521 (297 GB)
> NewFiles 6
> NewFileSize 24576 (24.0 KB)
> DeletedFiles 0
> ChangedFiles 34
> ChangedFileSize 244908956420 (228 GB)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 40
> RawDeltaSize 7674819255 (7.15 GB)
> TotalDestinationSizeChange 5589184884 (5.21 GB)
> Errors 0
> -------------------------------------------------
> 
> This still however doesn't allow me to get in a daily incremental since
> it's taking more than a day to do an incremental.  I am going to see
> what the async upload flag does to this timing.  Will report back in a
> day or however long the next inc takes.
> 

doing backups to a local file:// target and upload/sync with remote via
an extra script usually does the trick for people with poor bandwidth.

ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.