Déjà Dup

Cache signatures files when using S3 (or even network filesystems)

Bug #361381 reported by Jose Carlos Garcia Sogo
2
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Wishlist
Michael Terry
Déjà Dup 10.1

Bug Description

When restoring a backup, duplicity has to access signatures files. While this is not a problem in local filesystems, it is in network filesystems or when using Amazon S3. And the problem is worse when a signatures file of several MB has to be read to restore a tiny file of 10KB.
This could be solved by locally caching these signatures files, so they can be accessed locally.

Cheers

Revision history for this message
Michael Terry (mterry) wrote :

This would be nice. I believe it's as simple as passing --archive-dir to duplicity and keeping a folder around for it. Maybe ~/.cache/deja-dup

Changed in deja-dup:
importance: Undecided → Wishlist
status: New → Confirmed
Michael Terry (mterry)
Changed in deja-dup:
assignee: nobody → Michael Terry (mterry)
milestone: none → 10.0
status: Confirmed → Fix Committed
Revision history for this message
Michael Terry (mterry) wrote :

Backing this out until duplicity has support for using --archive-dir in the middle of a backup series. I'm working on that patch.

Changed in deja-dup:
assignee: Michael Terry (mterry) → nobody
milestone: 10.0 → none
status: Fix Committed → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

OK, duplicity 0.6.00 forced my hand by requiring a cache. I worked around the bug in duplicity in Deja Dup itself (ignoring errors when running a cleanup basically) and so Deja Dup can safely add --archive-dir. 10.1 has support.

Changed in deja-dup:
milestone: none → 10.1
assignee: nobody → Michael Terry (mterry)
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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