I know that checksum caching was primarily introduced to speed up the
comparison with existing compressed pool files.

However, it seems like we get for free a built in file md4 checksum
that can be used to verify data integrity.

Is there any user-configurable way to turn on checksum caching the
first time a file is transferred rather than having to wait until it
may or not be present in another backup?

This way if you ever have questions about data integrity, you can
always go back even years later to verify the files...

Also if I am understanding it correctly the "tax" is about 1% for
large files (20 bytes per 2048 block).


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/