Easy resumability
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Right now, backups are all or nothing. Not usually bad when doing an incremental backup, but the first backup is a killer.
Duplicity doesn't support this yet. There was recently some talk about it on the mailing list, it's on their radar.
In the meantime, we can break backups into small parts and do them one at a time. That way, we won't miss much if there's a problem.
This is still not ideal. Giant files pose a problem. There's a danger of needing to be very clever to break it up into small parts, just to workaround a lack of resumability in duplicity itself.
Easy resumability would remove almost all of the issues with large/slow backups. I don't expect a user cares how long it takes, as long as he/she doesn't need to mind it, in the sense of babysitting it. deja-dup-monitor can take care of resuming when it can (NetworkManager back up for example).
Changed in deja-dup: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Duplicity 0.6.00 supposedly supports resuming/ checkpointing. Have to look into supporting it.