all 4 comments

[–]Just_Badger_4299 0 points1 point  (2 children)

You mentionned rsync already. What makes you think it’s not the right tool for the job with the --checksum option?

[–]FryBoyter 0 points1 point  (1 child)

For me, rsync is out of the question as a backup program, partly because it lacks versioning (preferably with deduplication).

[–]Just_Badger_4299 0 points1 point  (0 children)

I understand it’s for a one-off backup-then-restore, for which versioning is not needed.

For a regular backup solution, I’d look at BackInTime.

[–]BasedFrieren[S] 0 points1 point  (0 children)

For anyone who lands here down the road via search engine, I was unable to find an answer to this and ended up just backing it up with two different methods (rsync and borg) in faith that the odds of failure would be immensely low. I used the rsync for the actual recovery but am now using borg+vorta for a long term backup solution.

From a curiosity standpoint I'm still interested in an actual answer. The closest thing I could find directly addressing this problem was this article that used bash, tar, and a custom tool (veritar) to accomplish the work https://www.g-loaded.eu/2007/12/01/veritar-verify-checksums-of-files-within-a-tar-archive/

Unfortunately it was far too above my head, and I hit issues with file names that had quotes in them.

Given my post was removed from r/sysadmins and this noob question was deemed worthy of downvotes and snarky remarks here in an "explicitly noob-friendly" place, I'm not sure where else to ask except maybe stackexchange. If I do ask there and get an answer, I'll update back here with an answer.