[Duplicity-talk] Handling of aborted sessions...

[Rob Browning]

I just tried to restore something and got:

  # duplicity --no-encryption \
    --file-to-restore foo/bar \
      file:///somedir/duplicity .
  Warning, found incomplete backup sets, probably left from aborted session

What does this mean?  If it means that duplicity can't restore because
some incremental backup failed, then is there any way duplicity could
scan for this problem and scream loudly the next time you try to make
an incremental backup after a failure.  Better yet,can we arrange it
so that duplicity just doesn't "commit" a backup until it's finished
(i.e. doesn't "mv" the backups into their final place until the whole
backup finishes), and offers to delete (or warns that you ought to
delete) corrupted backups the next time it's run?

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4