Backup restart/resume marks files deleted

[krbvroc1]

Duplicity 0.6.17
Python 2.4.3
Centos 5.6
Target is custom backend

Summary: When a RESTART occurs, all files prior to the restart will be marked deleted and re-backed up in subsequent backups

To reproduce:

1) Kick off a full backup. Wait until several volumes have been uploaded and then hit Ctrl-C during the upload of a volume. You will probably have to hit Ctrl-C five times to abort each of the five retry attempts. The goal is to exit back to the shell.

2) Run the same backup command and let it complete. Duplicity will print something like
"RESTART: Volumes 2 to 3 failed to upload before termination.
         Restarting backup at volume 2."

At this point you are supposed to have a completed full backup set.

3) Run the same backup command and let it complete. This will be your first incremental. All files located in volumes prior to the RESTART will be marked as deleted.

4) Run the same backup command and let it complete. This will be your second incremental. All files marked deleted will be backed up again and marked deleted again.

[krbvroc1 (kbass)]

Attached is -v9 logs of each of the steps to reproduce the bug.

[Robert (rycee)]

Just to add that I ran into this exact issue (on my first ever backup using duplicity, no less!) using Tahoe-LAFS as backend. I'm using a stock Fedora 16 install with duplicity 0.6.17 and Python 2.7.2.