Recovering from an interruption during backup
Jakob Bohm via Duplicity-talk <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Organization | WiseMo A/S |
| Message-ID | <[email protected]> |
Dear Duplicity community. As I am backing up lots of data with Duplicity, I find that the biggest backup volume takes over 3 weeks to do a full backup (starting a new chain), seemingly bottlenecked by the processing speed of AWS storage or the speed of the local router. This creates a special problem: If anything interrupts this 3 week long upload process (Such as: Router failure, AWS outage, process interrupt or local machine crash), there is no clear way to continue the backup without starting over the entire backup . It would be really nice if there was a clear way to make the backup continue where it left off, as long as at least some of the local Duplicity state directories survive the interruption. Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk