duplicity-team team mailing list archive

Thread
Date

[Question #557374]: Using Swift backend, signatures and manifests are not segmented

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: Doug <question557374@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 13 Mar 2017 22:13:40 -0000
Reply-to: question557374@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

New question #557374 on Duplicity:
https://answers.launchpad.net/duplicity/+question/557374

Ubuntu 14.04
Duplicity 0.7.11

We are using duplicity to back up a large filesystem with many many small files.  Currently the backup runs successfully but the signatures file is greater than 5G even compressed.  This means swift rejects the upload as too big and the backup fails.  When uploading the manifest or signature files, duplicity should use the swift upload -S to enable dynamic large objects support.  A manual swift upload works and a subsequent collection-status is correct.

duplicity --verbosity Notice ${OPTIONAL_OPTIONS} \
                --full-if-older-than 5D \
                --num-retries 3 \
                --asynchronous-upload \
                --no-encryption \
                --max-blocksize 20480 \
                --volsize 1024 \
                ${EXCLUDE_ARCHIVE_DIR} ${SRC} "${DEST}"

It would be nice if the volsize was used for -S parameter on upload of the manifest and signature files.

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.