In Reply to: Backup Integrity posted by PAR on January 17, 2016 at 09:07:12:
The most reliable way is to do a complete file compare of the original and the backup. My normal practice is to compare file directory trees to make sure that each sub directory has the same list of file names, file modification dates and file sizes. This will catch most user errors, but there is still a possibility of undetected data corruption while in storage or (more likely) while being read or written. When I moved to an entire new set of backup disks for my NAS I performed the ultimate level of security, namely in addition to the directory scanning I did a complete file comparison on each file in the library. This took a long time, not something I would do every day or even every month.
I use software that automates this process and provides a list of files that are inconsistent (at whatever level of paranoia chosen.) I have this software configured so that it does not overwrite a file in case the newer one disagrees. This way, I can resolve any differences manually, but these have only happened as a result of reorganizations of my library.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
This post is made possible by the generous support of people like you and our sponsors:
Follow Ups
- RE: Backup Integrity - Tony Lauck 01/17/1610:51:23 01/17/16 (10)
- Ah - fmak 02:10:25 01/18/16 (9)
- RE: Ah - PAR 02:21:13 01/18/16 (8)
- RE: Ah - fmak 03:47:07 01/18/16 (7)
- RE: Ah - PAR 08:24:36 01/18/16 (6)
- RE: Ah - Tony Lauck 13:24:55 01/18/16 (0)
- RE: Ah - J.Mac 12:55:03 01/18/16 (4)
- Integrity? - fmak 04:31:04 01/20/16 (2)
- RE: Integrity? - Tony Lauck 11:39:56 01/20/16 (0)
- I don't see your point - J.Mac 10:57:54 01/20/16 (0)
- RE: Ah - AbeCollins 13:13:18 01/18/16 (0)