[rdiff-backup-users] Re: Computed SHA1 digest doesn't match recorded digest

[Daniel Miller]

Incidentally, now that the particular revision has moved beyond the  
verify window on the server (30 days) it has disappeared there. It  
still appears on the remote system where I am verifying all revisions  
within the past year. Here's a little more background on my setup.  
All these steps occur each night:

server1: rdiff-backup to server1 backup volume
server1: rdiff-backup-verify 30 days of revisions on server1 backup  
volume
server2: rsync from server1 backup volume to a removable hard drive  
attached to server2
server2: rdiff-backup-verify 1 year of revisions on rsync-updated  
removable drive
server2: eject removable drive (will be replaced with a different  
drive for the next backup)

Josh, is there anything I can extract from my repo to help  
troubleshoot what might have gone wrong?

~ Daniel


On Aug 3, 2009, at 9:27 AM, Daniel Miller wrote:

> Recently I got an error message during the verify phase of my backup:
>
> Warning: Computed SHA1 digest of usr/local/pgsql829/data/base/ 
> 16417/104934
>    0520c6624e91386b43c6bdcdaddfb8df0617ec86
> doesn't match recorded digest of
>    f1629023c48ff184d702ea59d07fdd88f55fad03
> Your backup repository may be corrupted!
>
> I have continued to receive the same error on subsequent backup/ 
> verify cycles. Lucky for me this file is probably not of critical  
> importance -- it is a PostgreSQL system data file (I have a  
> separate pgdump archive that would be used to restore the database  
> if needed).
>
> However, I would like to put the repository in a state that does  
> not produce this error on verify. How to I recover from this error?  
> Is there any way to restore the integrity of my repository?
>
> System details:
> Mac OS X Server 10.5.7
> rdiff-backup 1.2.8
> Python 2.6.2
> librsync-0.9.7 (patched with librsync-largefile.patch)
> xattr-0.4
>
> ~ Daniel