duplicity creates huge backup archives

Bug #873164 reported by Anders Aagaard
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

Runnning this command:
# duplicity --no-encryption --volsize 25 --full-if-older-than 1M --s3-european-buckets --s3-use-new-style /path/ s3+http://path

# ls -lh ./.cache/duplicity/cb16c6c2ab88f146c07ca64f59318183/
total 73G
-rw------- 1 root root 2.1M 2011-10-11 21:52 duplicity-full.20110919T174252Z.manifest.part
-rw------- 1 root root 31G 2011-10-11 22:46 duplicity-full-signatures.20110919T174252Z.sigtar.gz
-rw------- 1 root root 43G 2011-10-11 21:52 duplicity-full-signatures.20110919T174252Z.sigtar.part

Most of my duplicity backups work fine, but in this directory it's not splitting the archives properly.

duplicity 0.6.14 ubuntu 10.10, python 2.6.6

Revision history for this message
Anders Aagaard (aagaande) wrote :
Revision history for this message
Anders Aagaard (aagaande) wrote :
Revision history for this message
Anders Aagaard (aagaande) wrote :

Note that the log referes to "windowsdomainserver", that's a clients server we take backup from. The system is linux. I use lftp and mirror all files to the linux server, then use duplicity to S3 for history and mirroring.

Revision history for this message
Martin R. Siegert (martin-siegert) wrote :

Dear Anders,

You go not observe too-big backup-archives (duplicity-*.vol*.difftar.gz) but too-large signatures (*.sigtar.*) , as it is outlined already since 2009 in https://bugs.launchpad.net/duplicity/+bug/385495 (and still not fixed yet, because of desired backwards-compatibility and number-of-open-files).

Regards,
Martin

Revision history for this message
Anders Aagaard (aagaande) wrote :

I'll subscribe to that bug then, thank you very much :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.