How do you verify backup integrity and restore capabilities?

• A. Assume backups are valid if files exist.
• B. Backups must be stored offsite, but testing isn't necessary.
• C. Restore procedures should be tested only after an outage.
• D. Regularly test restore procedures, verify data integrity checksums, and document success/failure.

Answer: (D)

Regularly validating backups and restore capabilities is essential because backups can exist but still be unusable due to corruption, missing pieces, or metadata problems. The strongest approach combines end-to-end restore testing, data integrity verification, and documentation of results. By routinely rehearsing the restoration process, you confirm that you can actually recover services within the desired RTO and RPO. Using integrity checksums or hashes ensures the recovered data matches the original source, catching silent corruption that file counts alone can miss. Documenting each test—what was tested, success or failure, and any remediation steps—creates a repeatable process and traceable proof of recoverability.

Other options fall short because assuming validity from file presence ignores corruption or incomplete backups; offsite storage helps resilience but doesn’t guarantee restorable data without testing; and waiting to test until after a real outage means you’ll face unvalidated recovery during downtime.