Backup and recovery planner
Check each important system’s backups against how much data you can afford to lose (RPO) and how long you can be down (RTO), plus 3-2-1 and offline copies. Nothing you enter is saved.
- ⚠ Backups every 4 h can lose up to 4 h of data — more than the 1 h you can afford. Back up more often.
- ⚠ A full restore takes 48 h but you can only be down 4 h — a gap to fix.
- ✓ Meets the 3-2-1 rule of thumb.
- ⚠ No offline or immutable copy — ransomware targets backups it can reach.
- ✓ Backups every 24 h meet the 24 h RPO.
- ✓ A full restore (6 h) fits the 168 h RTO.
- ⚠ 3-2-1 rule of thumb: keep 3 copies (original + 2 backups); use 2 different media types; store 1 copy offsite.
- ⚠ No offline or immutable copy — ransomware targets backups it can reach.
5 gaps to fix.
How it works
- RPO check: backups must run at least as often as your recovery point objective. RTO check: your last timed full restore must fit your recovery time objective.
- 3-2-1 rule of thumb (three copies, two media types, one offsite) and at least one offline or immutable copy, as CISA’s ransomware guidance recommends.
How to read it
The example rows reproduce our guide’s scenario: accounting data with a 4-hour RTO but a 48-hour restore is a gap to fix. If you’ve never timed a full restore, that’s the first thing to do — scheduling backups isn’t enough.
The full explanation is in our guide: Backups and Disaster Recovery: RPO, RTO and Restores That Work.