Backup Validation

The Silent-Corruption Problem

Most backup tools report success the moment they finish writing files. That status tells you the job completed — it does not tell you the copy is good. Bit rot on a drive, an interrupted transfer, a flaky USB enclosure, a truncated cloud sync or a quietly failing disk can all leave you with a backup that looks complete but is subtly broken. The worst time to discover this is during a real restore, when the original is already gone. "The backup ran" is a log entry; "the backup is a perfect copy" is a fact you have to prove. That proof is exactly what Backup Validation gives you.

Hash-Compare Backup vs Source

e-Dex compares a backup against its source the only way that is mathematically defensible: by cryptographic hash. It computes a fingerprint for every file on both sides and compares them, then prints an overall PASS or FAIL verdict. Underneath the verdict, every file lands in one of four buckets: matched (present on both sides, identical hash), changed (present on both sides but the hashes differ — corruption or modification), missing (in the source but absent from the backup) and extra (in the backup but not in the source). A backup passes only when nothing is changed and nothing is missing, so a single altered byte anywhere flips the result to FAIL and shows you precisely which file to investigate.

Validate at Scale

Backups are rarely a single file. e-Dex walks entire folder trees and whole drives, hashing thousands of files and reconciling them against the source in one pass. Because the comparison is content-based rather than date- or size-based, it catches the corruption that timestamp checks miss — two files can share a name, size and modified date and still differ byte-for-byte. Whether you are validating a nightly file-server backup, a migrated archive or a freshly restored dataset, the four-bucket breakdown stays readable: one verdict at the top, and an exact list of what changed, what went missing and what appeared that should not have.

Get a Backup Integrity Certificate

When the comparison is done, e-Dex issues a Backup Integrity Certificate — a clean, shareable record of the PASS/FAIL verdict and the matched, changed, missing and extra counts, with the source and backup locations and the hashes that back the result. It turns a moment-in-time check into durable evidence you can file, attach to a change ticket, or hand to an auditor who asks "how do you know the backup was good?" Like the rest of e-Dex, the certificate is produced locally and aligns with the same integrity model as our Backup Integrity Certificate for compliance guidance.

For IT, DR and Compliance Teams

IT and infrastructure teams use Backup Validation to confirm a copy is sound before they trust it or rotate media. Disaster-recovery teams validate restored datasets against a known-good source so a restore can be signed off with evidence rather than hope. Compliance and audit teams use the certificate to demonstrate that protected data is intact and unaltered. One important boundary: Backup Validation is an integrity attestation, not a recoverability test. It proves the files are bit-for-bit identical to the source; it does not boot a system or confirm an application can mount the data. Pair it with your restore-rehearsal process to cover both halves of "is this backup safe?"

Frequently Asked Questions

How do I verify backup integrity by hash?
Point e-Dex at your original Source folder and your Backup or Restored folder. e-Dex computes a cryptographic hash for every file on both sides and compares them. It returns an overall PASS or FAIL verdict and breaks the result down into matched, changed, missing and extra files, so you can see exactly where a backup differs from its source — all without an internet connection.

Does Backup Validation test whether my backup can be restored?
No. Backup Validation is an integrity attestation, not a recoverability test. It proves that the files in your backup are bit-for-bit identical to the source at the time of comparison. It does not boot a system, replay transaction logs, or confirm that an application can mount the data. Use it alongside a recoverability or restore-rehearsal process, not as a replacement for one.

What do matched, changed, missing and extra mean?
Matched files are present in both source and backup with identical hashes. Changed files exist on both sides but their hashes differ, indicating corruption or modification. Missing files are in the source but absent from the backup. Extra files are in the backup but not in the source. A backup passes only when there are no changed and no missing files.

Does e-Dex need an internet connection to validate a backup?
No. e-Dex runs fully offline on your own Windows machine. Hashing both folders, comparing them and issuing the Backup Integrity Certificate all happen locally, so your data never leaves your computer. This makes it suitable for air-gapped, regulated or sensitive environments.

Prove Your Backup, in Minutes

Stop trusting a green "success" log and start proving it. e-Dex hash-compares your backup against its source, hands you a plain PASS/FAIL verdict with matched, changed, missing and extra files, and issues a Backup Integrity Certificate you can keep — all offline, free, on a single Windows machine. Download e-Dex free and validate your first backup today.