Test backup recovery quarterly
Test one backup quarterly by performing a simulated full restore to verify recoverability before you need it, timing the process and documenting any gaps.
When This Fires
- Quarterly, as a scheduled maintenance activity
- After any changes to backup configuration (new tool, new location, new scope)
- When you realize you haven't verified backup recoverability in 6+ months
- Complements 3-2-1 backup rule (3-2-1 backup rule) with the verification that the backup infrastructure actually works
Common Failure Mode
Backup-without-verify: running automated backups daily for years without ever testing whether the data can actually be restored. The backup process runs, the status says "complete," and you assume you're protected. Meanwhile, the backup has been silently failing to capture a critical directory, or the cloud restore process requires a password you've since forgotten.
The Protocol
(1) Quarterly, select one of your backup copies (rotate between copies across quarters). (2) Perform a simulated full restore to a temporary location (not overwriting your current data). (3) Time the process from initiation to completion — this is your recovery time. (4) Verify the restored data: open representative files from each critical data category. Check formatting, metadata, and file integrity. (5) Document: What worked (successfully restored data types), What failed (missing files, corruption, process errors), Time taken (your actual recovery time), Gaps (data that should be backed up but wasn't). (6) Fix any identified gaps before the next quarter.