[Duplicity-talk] feature request: resuming broken backups.

[sophana]

Adam Wendt a écrit :
> One idea would be to do a local backup and then scp the files over to
> the remote server, that way you can easily just continue with the ones
> left over if it fails. Now of course this requires you have enough
> space to store the backup on your local server initially.
Yeah having enough local space is not always possible.

It would be very nice if duplicity could resume a broken transfer by
rewriting existing partial increments.
This way you can scale to huge backups while keeping more reliability.
Duplicity would regenerate each volume one by one, rsync them to the
destination. If rsync detects that volumes are the same, there would be
no transfer (with the rsync -c option)

I think the major problem with that is in the way file names are
generated with timestamps. If duplicity could use a backup increment
counter (stored in a remote side file), that would be incremented only
when backup is successful, duplicity would simply rewrite the latest
unfinished backup.

This feature would really bring more scalability and reliability to
duplicity IMHO.