Comment 8 for bug 487720

Sorry, I must have wonked something from the error message that I typed in my description of the bug. The error message in the log should have the correct hashes. Were you looking at those?

I don't have the log from the backup that I did. I know why it failed, though.

Basically, when you're doing a backup to a remote location(ssh) and then the computer suspends, the backup will keep going just fine if you resume the machine after a short time. However, if you wait too long, I think the server will sever the connection automatically. (As a side note, annoyingly, Ubuntu does not check for a timed out connection and unmount the connection in nautilus upon resume) Upon resuming the client from suspend, deja-dup/duplicity attempts to continue the backup, and then fails because the connection has timed out. So, that's how the backup failed. When I manually ran the backup again through Deja-Dup, it found the unfinished backup, scanned through the files to the current file being backed up, and continued as normal. This is how the backup got finished.