Comment 4 for bug 613244

I was flabbergast to find that *ANY* interruptions to a long running, multi-volume duplicity (v0.6.10) backup will eventually complete (with enough restart coaxing) but, they will *always* (happily) produce unusable/corrupt duplicity volumes.

I spent a lot of time *NOT* believing that Duplicity can/should only be used over uber-reliable LANs ... and never over the internet/WAN. Thank goodness I test my backups religiously. Duplicity is close to great ... but it sure isn't 1.0 yet. I don't know how regressions to Duplicity's checkpoint/restart feature pass the whole continuous integration/test nightly ... or even a one time QA-at-the-end (of dev/release cycle) test. That is worrisome. Bummer. You have been warned!