>
> IIUC, you want a way to check the integrity of the pool files on the
> server side.
>
Yes
> BackupPC 3 used to have such a function, by re-checksumming and
> verifying some percentage of the pool during a nightly (can't remember
> the details, and I don't have the v3 docs available).
>
Found it here:
https://backuppc.github.io/backuppc/BackupPC-3.3.2.html#Rsync-checksum-caching
The wording further confirms that V4 won't checksum the files once they're
added to the pool, contrary to what I believed.
> If you want to do this for yourself, it's pretty easy with a cronjob.
> Just compare, for all files in $topDir/pool/*/*/, their md5sum with the
> filename. Same = good, not the same = bad.
> If your pool is compressed, pipe the compressed files in
> $topDir/cpool/*/*/ through pigz [1] (which, as opposed to gzip, can
> handle the headerless gz format used there), as in the following piece
> of bash:
>
> digest=$(pigz -dc $file | md5sum -b | cut -d' ' -f1)
>
> Now, check if $digest == $file, and you have a sanity check. (It's
> slightly more annoying to find out where $file was referenced in case it
> is corrupted; but it's possible, and I recommend not to worry about that
> until it happens.)
>
Perfect, thanks! I can then use --checksum to verify the client, and a
script to checksum the server off-line from time to time. The best of both
worlds :)
Regards,
Guillermo
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
