Each 3-2-1 condition is evaluated separately; copy count is not confused with media and location diversity. Evidence gaps are prioritised against restore age and recovery objectives.
330
Privacy & security
3-2-1 Backup Readiness Checker
Evaluates total copies, distinct media, offline/off-site copies, encryption, last successful restore date, and recovery objective separately. It accesses no backup, copies no data, and guarantees no disaster recovery.
✓ Free✓ No account✓ In-browser
QUICK ANSWER
What does this tool do?
Combine copies, media, locations, encryption, and restore testing in an evidence-focused readiness report.
APPLICATION AND DECISION GUIDE
3-2-1 Backup Readiness Checker: method and usage
Evaluates total copies, distinct media, offline/off-site copies, encryption, last successful restore date, and recovery objective separately. It accesses no backup, copies no data, and guarantees no disaster recovery.
total copies, distinct media count, offline or off-site copy, encryption, last successful restore date, and RPO and RTO targets Confirm the shape first with a small example containing no personal data.
condition-level readiness cards, missing evidence, stale-restore warnings, and the next rehearsal checklist
Practical steps
- Load the example or fill the clearly labelled fields for your scenario.
- Run the check on-device and review metrics, warnings, and recommended corrections together.
- Validate the result in the real target environment and record its assumptions.
restoring selected sample files in isolation and measuring integrity digest, readability, access permissions, and achieved RPO and RTO
Form answers do not prove that backups exist, are intact, or are restorable. Critical systems require signed evidence and regular real restore rehearsals.
Suitable use cases
- Personal archive review
- Small-team recovery readiness
- Backup-provider migration
Worked decision record
Practical scenario: Personal archive review. Combine copies, media, locations, encryption, and restore testing in an evidence-focused readiness report.
Select 3 current copies, 2 media types, off-site copy, and encryption; set the last restore to 30 days ago and RTO to 4 hours. Then reduce media to 1 and move the restore date back 120 days.
Acceptance record: restoring selected sample files in isolation and measuring integrity digest, readability, access permissions, and achieved RPO and RTO. Keep the result-card metrics and warnings together with the retained example.
Do not publish in this state: Form answers do not prove that backups exist, are intact, or are restorable. Critical systems require signed evidence and regular real restore rehearsals.
LEARN THE WORKFLOW
Guides for this tool
Local-App Resilience with Browser Storage and File Manifests
Do not treat offline data as unlimited: design quota, eviction, integrity, restore, and user-owned export together.
Read guide →Safe Release Operations: From Performance Budgets to Restore Evidence
Turn performance, dependencies, backups, and change information into one reversible release decision instead of isolated checks.
Read guide →ABOUT THIS TOOL
Frequently asked questions
What input does 3-2-1 Backup Readiness Checker accept?+
total copies, distinct media count, offline or off-site copy, encryption, last successful restore date, and RPO and RTO targets Select 3 current copies, 2 media types, off-site copy, and encryption; set the last restore to 30 days ago and RTO to 4 hours. Then reduce media to 1 and move the restore date back 120 days.
What does 3-2-1 Backup Readiness Checker return?+
condition-level readiness cards, missing evidence, stale-restore warnings, and the next rehearsal checklist Acceptance record: restoring selected sample files in isolation and measuring integrity digest, readability, access permissions, and achieved RPO and RTO. Keep the result-card metrics and warnings together with the retained example.
How should I validate 3-2-1 Backup Readiness Checker output?+
restoring selected sample files in isolation and measuring integrity digest, readability, access permissions, and achieved RPO and RTO Do not publish in this state: Form answers do not prove that backups exist, are intact, or are restorable. Critical systems require signed evidence and regular real restore rehearsals.
Does 3-2-1 Backup Readiness Checker send or store input on a server?+
Tool input is processed in the active tab. Saving to the Workstation or transferring to another tool is a separate choice. Consider browser extensions and shared devices separately; the privacy page explains advertising and network connections.