[Duplicity-tracker] [bug #25421] Make duplicity restartable after failure or interruption

[anonymous]

Follow-up Comment #3, bug #25421 (project duplicity):

Just looking at the code, and wondering is the "archive-dir" option could be
used as an automatic check-point ?

I mean, as everything is duplicated on the archive-dir, when an exception
occurs (or whatever recoverable error), couldn't duplicity restart from the
"archive-dir" content with minor modifications ?

Also, I thought about adding an option "--delayed" to create the backup set
on the client first, and then transmit it to the backend afterward.
That way, whenever the backend fails, it always possible to restart, provided
the files in the client are still there.
Each successful file deposit on the backend removes the client file, so it's
possible to track the backend progress by listing the files on the "delayed"
directory.
It double the required size on the client, but for unreliable backend, it
might still be interesting.

On the restore or incremental side, we only have to download the signature
from the backend to the client "delayed" dir, and then we can start the
restore / incremental process, without more delay (we can be asynchronous
here, no issue).



    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?25421>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/