Backup Validation Checklist

A free, printable checklist to prove your backups are complete, intact and recoverable — not just “green”.

Free, no signup.

A backup job that reports “success” is not the same thing as a backup you can rely on. A green status only confirms the job ran — it says nothing about whether the data is intact, complete, or actually restorable. Files can be silently corrupted, partially written, or changed without the job ever flagging a problem. The only way to know your backups will save you is to validate their integrity and test that they restore. Work through the checklist below for each backup set, tick every box, and keep the evidence.

1. Scope & schedule

☐ Critical data identified (what must be recoverable).
☐ Backup and retention schedule defined.
☐ An off-site or immutable copy exists.

2. Integrity validation

☐ Hash (SHA-256) the source set.
☐ Hash the backup / restored set.
☐ Compare the hashes for a MATCH.
☐ Investigate any mismatch before relying on the backup.

3. Restore testing

☐ Perform a test restore on a clean target.
☐ Confirm files open and counts match.
☐ Record the date and who ran it.

4. Evidence & certification

☐ Capture the validation results.
☐ Issue a Backup Integrity Certificate.
☐ Retain the certificate and logs for audit / insurer.

5. Cadence

☐ Validate on a regular schedule.
☐ Re-test after major changes.

How e-Dex helps

e-Dex is a free, offline Windows tool with a dedicated Backup Validation tab built for exactly this checklist. Point it at your source data and your backup, and it hashes both sides and tells you plainly whether they MATCH or MISMATCH — turning “the job said it worked” into provable, byte-for-byte integrity. When the sets match, e-Dex issues a signed Backup Integrity Certificate you can keep as one-page evidence for an audit or insurer. Everything runs fully offline on your own machine, so your data never leaves your control. Download e-Dex free and start validating your backups today.

Frequently Asked Questions

What is a backup validation checklist?
A backup validation checklist is a repeatable set of checks that proves your backups are complete, intact and recoverable rather than merely reported as successful. It covers scope and schedule, integrity validation by hashing and comparing, a test restore on a clean target, and capturing evidence such as a Backup Integrity Certificate for audit or insurer.

Why is a successful backup job not proof of recoverability?
A backup job can report success while the underlying files are corrupt, partially written, silently changed, or impossible to restore. A green status only confirms the job ran, not that the data is intact or usable. The only proof is validating integrity by hashing and comparing the data, and then actually restoring it on a clean target to confirm the files open and counts match.

How do you validate backup integrity with a hash?
Compute a SHA-256 hash of the source data set, compute the same hash on the backup or restored copy, and compare the two values. If they match, the copy is bit-for-bit identical to the source. If they differ, even by a single byte, the hashes will not match and you should investigate before relying on that backup.

How often should backups be validated?
Validate backups on a regular schedule aligned to how critical the data is — many teams validate and test-restore monthly or quarterly — and always re-test after a major change such as a system upgrade, migration or change to the backup configuration. Each validation should be recorded with the date and who ran it so you have an audit trail.

Backup Validation Checklist