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

[anonymous]

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

What about triggering a checkpoint on any exception except KeyboardInterrupt
?

That way, whenever duplicity is about to fail, it saves it state to a file
(not necessary distant file, should be local to handle network error
correctly), and'll be able to restart from that state "file", provided the
network is now up and working.

I don't know if duplicity can auto-serialize itself, or if we need to write
code for this. 

The only issue I could imagine would be modified file in the current archive,
but either the archive is compressed & cyphered, and in that case, it would be
better to try an incremental backup after the state restore, either it isn't
compressed & cyphered, and in that case, we should recreate the archive
including the modified files.

Cyril

    _______________________________________________________

Reply to this item at:

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

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