Generating Checksum of .tar.gz Backup in a Performant Matter #2
Description
CRC32 is 1.5x faster than MD5 according to some anecdotal testing of personal backups.
Should I generate a checksum of the .tar.gz only, or per file while backing up? Both?
What's the best method of implementing this? tar comes with no method of generating a checksum. Maybe tee the output of the compression in-progress into CRC? Large backups will slow Aegis to a halt for checksum generation.
Oh, and checksum generation should be a configurable value during setup.