|
From: | Daniel Miller |
Subject: | [rdiff-backup-users] Re: Computed SHA1 digest doesn't match recorded digest |
Date: | Thu, 13 Aug 2009 09:03:14 -0400 |
I'm still getting the error on each successive backup.Also, a possibly related question. It is my understanding (and seems to hold true after checking on my setup) that rdiff-backup does not backup a new version of a file if the file changes while rdiff-backup is backing up the file. For example, if a log file changes while rdiff-backup is backing it up rdiff-backup will discard whatever version it got and leave the archived version at the last successfully backed up state. I'm having this issue on several log files, and it happens on the same log files every night, meaning that the particular files in question have not been updated since the initial backup (months ago). Is there any way to tell rdiff-backup to keep whatever it gets, regardless of whether the files changes while being backed up?
~ 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/1049340520c6624e91386b43c6bdcdaddfb8df0617ec86 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
[Prev in Thread] | Current Thread | [Next in Thread] |