Josh Nisly wrote: > I don't know about the first problem (I though rdiff-backup on linux > handles it.)
Not sure about linux; I've only tried on a PC -- I guess it would be possible to test on linux by using touch to reset the date fields on a fail, if it can reset the relevant ones. Which date field does rasync-backup check? > The second problem is because one of the underlying libraries has a > bug dealing with large (>4GB) files. There is a patch available that > is typically applied on linux, but when I wrote the build script, I > simply failed to include it. I'll try to change this soon. That'd be great. > Philip Warner wrote: >> >> 1. If date and size do not change, then rdiff-backup assumes the file is >> unchanged. There seems to be no way to force it to check a file (I >> vaguely recall rsync *does* have a parameter to say 'force file data >> check'. >> >> 2. Large file support does not seem to be there. The file I am using is >> 12GB in size and rdiff-backup dies (eventually) with an illegal seek. >> _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
