RE: [rdiff-backup-users] CRC checksum and other "minor" errors

[Olav Langeland]

> -----Original Message-----
> From: Paul Smith [mailto:address@hidden 
> Sent: 1. februar 2005 17:27
> To: address@hidden
> Subject: [rdiff-backup-users] CRC checksum and other "minor" errors
> 
> I'm frustrated with the fact that rdiff-backup will halt when 
> it hits a 
> CRC checksum error, most often due to a source file changing 
> during its 
> backup. This is not uncommon with certain large files on our system. 
> Since I'm backing up large volumes, I'd rather the backup 
> continue past 
> this and other "minor" errors (i.e., errors related to a single file) 
> so that as much of the volume is backed-up as possible. As it is now, 
> the whole thing aborts, even if it's only a fraction of the way 
> through. I'm not sure what the "right" solution is here. Maybe each 
> file that fails is pushed into a stack that is reported at 
> the end, and 
> I can decide how to handle them later. Maybe a flag can be set to 
> ignore checksum errors specifically. At a minimum, I'd like a 
> command-line option to not halt on (at least) checksum errors.
> 
> -Paul

Hi,

this is the same problem I discovered and is for me the only
show-stopper regarding rdiff-backup. We have several logfiles where
daily rotating is not ideal and rdiff-backup ofcourse skips these. Since
changes in the logfile makes the MD5 checksum invalid, I can see why it
skips by default. But it would be nice, really nice, if it had a switch
for ignoring it and backup the file regardless of filechange.

-olav