Re: [rdiff-backup-users] Restore Failure with 0.13.1

[Ben Escoto]

On Thu, 30 Oct 2003 10:20:30 -0600 "John Baker" <address@hidden> wrote:
> Thanks.  The problem was related to the famous more than one current_mirror*
> file.  I deleted the earliest one and the restore operation worked.
> However, when I backup now, I get this:
...
> Previous backup seems to have failed, regressing destination now.

If there is only one current_mirror file you shouldn't see this
message.  The only way rdiff-backup has of knowing the previous backup
failed is if there are two current_mirror files.

> 1) two current_mirror* files - again
> 
> 2) A corrupted error log - when I try to unzip I get this:
> 
> gunzip: error_log.2003-10-30T03:10:43-05:00.data.gz: unexpected end of file

The error_log and similar files are written incrementally as the
backup progresses, so if the backup aborts they will be left
truncated.

> 3) A  mirror_metadata with the correct date, but very small size - and the
> next to last one is also very small: 109 and 99 bytes, respectively.
> 
> 4) No session_statitstics file with the correct date

Session_statistics is written at the end of a successful backup.

> Do I need to delete all current_mirror* files as well as these (apparently)
> incorrect files?

The statistics and log files are never read by rdiff-backup.  If a
mirror_metadata file got corrupted somehow then you will not be able
to regress.  In that case you should delete/move the corrupted
mirror_metadata file, and get rid of everything but the last
current_mirror file.


-- 
Ben Escoto

pgpXowI76GPMK.pgp
Description: PGP signature