Question #163116 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/163116
edso posted a new comment: > > Eventually I ran a verification to a date prior to the corrupted > manifest, the one with the missmatched hash, and voila! Verification > completed and then a restore to that date was successful. I will assume good to hear and makes perfect sense. > > Although I was lucky this time and I only lost some history (and a lot > of time), duplicity failed to 1) detect there was a problem during the > normal backup cycle and notify it there was no obvious problem during backing up, but during restoring, which is no part of backing up >and 2) provide a clear indication of > why verification was failing and which files/volumes where being > affected-event at -v9. you're right the hash mismatch should be more talkative. > > I'm now updating my backup script to run frequent verifications of my > backends. This is something I can afford because I run a local file > server. make the chains as short as you can afford and you are as safe as you can get > > Overall my gratitude goes out to Ken and Edso for helping through this > process and suggesting valuable pointers. pleasure, ede/duply.net -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
