Reader Question on diglloydTools IntegrityChecker: “verify terabytes of content back and forth between the cloud and other local RAID drives I have”.
See also Data Integrity Over Time, and with OS Changes and Data Loss Prevented: IntegrityChecker Saves my Bacon by Detecting Corrupted Files after a Clone and Detecting Corruption / Validating Data Integrity Over Time and Across Drives and Backup/Restore.
Sobe S writes:
Here is what I am trying to do and I want to make sure your program can offer that.
I use Transmit 5 to download and upload lots of content sometimes terabytes of content back and forth between the cloud and other local RAID drives I have.
What I am looking for is a program I can run that can verify the quality of that transfer. I want to make sure my transfers have good data and be able to verify the files are not corrupt once stored somewhere. Can your program provide that?
MPG: IntegrityChecker verifies bit-for-bit data integrity anywhere—originals, copies or backups or clones—and on any operating system and file system, on read/write or read-only media. It’s a simple two-step process:
- icj update the desired folder(s) or volume(s) in order to create the hash files used for verification.
- icj verify the data (originals, backups or clones, copies, etc).
A single command can verify a specific folder or folders or an entire volume or folder hierarchy. Excepting quite slower computers, the speed of verification depends mainly how fast the data can be read.
The enabling requirements to do this are:
- The folder(s) to be verified must accessible through a file system, e.g., a mounted volume on macOS, a drive letter ("D:" or similar on Windows), a mounted file system on Linux/UNIX.
- The folders to be verified must have hash information available. That means either a per-folder hash file or a hash hierarchy file. These hash files are created in the original folders using icj update, which does the initial hashing and then creates the hash files.
Addressing the question above
The uploaded data must be accessible on a mounted file system as per requirements above.
- icj update the folder(s) involved on the local RAID volumes.
- Sync or upload the data. The syncing obviously must include the .icj and/or .icjh hash files.
- Verify the uploaded files using icj verify.
Some users feel ill-