[Borgbackup] Archive File Integrity Check Against Local File System

[kevin.mccall at yahoo.com]

 Does this borg check switch compare all the files in the archive to the local file system? Or does this performed at the block level? 
The --verify-data option will perform a full integrity verification (as opposed to checking the CRC32 of the segment) of data, which means reading the data from the repository, decrypting and decompressing it. This is a cryptographic verification, which will detect (accidental) corruption. For encrypted repositories it is tamper-resistant as well, unless the attacker has access to the keys. It is also very slow.

    On Friday, December 9, 2022 at 04:05:55 PM EST, kevin.mccall at yahoo.com <kevin.mccall at yahoo.com> wrote:  
 
  I am new to borg, would anyone be willing to explain to me the best way to verify an archive is identical to the files in the local filesytem that were backed up? 
After reading through the documentation my understanding of command borg check is integrity checks of the repository structure and metadata at the block level. I read the command borg export-tar /path/to/repo::archive-name - | tar --compare -f - -C /path/to/compare/to  would complete an integrity check between an archive and the local filesystem.
Is this correct? How is tar comparing these files with hashes or just ctime or mtime? Is there a better way to ensure files are identical? I look forward to learning how you verify your backups. 
Thanks
Kevin

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20221209/4930e31f/attachment.html>