Re: [Duplicity-talk] What is Duplicity doing during incremental backup?

[edgar . soldin]

On 22.02.2012 10:37, Nicholas Sherlock wrote:
> Okay, at 400 minutes it was still doing the same thing, so I killed
> that task and restarted. Now it quickly completes:
> 
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Tue Feb 21 13:03:05 2012
> python: ERROR: (rs_job_complete) loadsig job failed: out of memory
> Error librsync error 102 while in delta rs_signature_t builder getting
> delta for lib/mysql/ibdata1
> --------------[ Backup Statistics ]--------------
> StartTime 1329902068.63 (Wed Feb 22 09:14:28 2012)
> EndTime 1329902563.24 (Wed Feb 22 09:22:43 2012)
> ElapsedTime 494.61 (8 minutes 14.61 seconds)
> SourceFiles 796
> SourceFileSize 412831898 (394 MB)
> NewFiles 0
> NewFileSize 0 (0 bytes)
> DeletedFiles 0
> ChangedFiles 30
> ChangedFileSize 143144207 (137 MB)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 30
> RawDeltaSize 134604624 (128 MB)
> TotalDestinationSizeChange 51429054 (49.0 MB)
> Errors 1
> -------------------------------------------------
> 
> However, it seems to have run out of memory during the job. How can I
> estimate how much memory and temporary disk space will be needed for a
> given backup process? There seems to be no information available about
> resource requirements for Duplicity which is rather problematic for
> large backups.
> 

That's probably the memleak bug still. Should be fixed in the next release 
0.6.18.
Read https://bugs.launchpad.net/duplicity/+bug/908228

You can try patching duplicity yourself with branch attached to the bug ticket.
or
Use unaffected 0.6.15 ..

ede/duply.net