Comment 37 for bug 487720

Hi,

I have encountered the same issue - If a backup was interrupted, a file is being left over in the loval cache preventing a restore until the cashe is flushed ot the file is manually deleted. A detail which is a bit more critical about this issue is that the file that was being backupped at the time of the interruption seems to be hashed in the signature file and will not be backupped in any of the following inc-runs. I was able to test is by creating a large file (couple of hundred MBs) being backupped. After an initial full backup I modified the file and ran an incremental backup pulling out the network during the backup. Re-starting the incremental backup showed that nothing had to be uploaded - the modified file was therefore never fully uploaded to the server.

This might create a hole in your backup...