RPO / RTO & Backup Frequency Checker

Understanding the RPO, RTO and backup frequency checker — concept and principle

Recovery point objective (RPO) and recovery time objective (RTO) are the two numbers at the heart of every backup and disaster recovery plan. RPO is how much data, measured in time, the business can afford to lose. RTO is how long the service may be down before it must be running again. This checker compares your backup interval and restore time with those targets.

A failure just before the next backup loses 240 minutes of data (RPO missed), while the 90-minute restore meets the RTO.

How it is calculated

Worst-case data loss = backup interval. If a failure happens just before the next backup, everything since the last backup is lost.
RPO met if backup interval ≤ required RPO. If not, the tool tells you to back up at least every RPO minutes.
RTO met if restore time ≤ required RTO.

All values are in minutes.

The principle

Backups taken at fixed intervals leave a gap between snapshots. A failure can strike anywhere inside that gap; on average you lose half an interval, but planning must cover the worst case, which is the full interval. So the backup interval must not exceed the RPO. RTO is about time, not data: from the moment of failure until users are served again. The restore itself is only one part of it; detecting the problem, deciding to fail over, and checking the restored system also take time.

Worked example

Inputs: required RPO 60 min, backup interval 240 min, restore time 90 min, required RTO 120 min.
Worst-case data loss = 240 minutes (four hours of changes).
240 > 60, so RPO is not met — back up every 60 min or less.
90 ≤ 120, so RTO is met, with 30 minutes of margin.

Each point is the calculator re-run with only “Backup interval (minutes)” changed; the gold point is the default example. Change the inputs above and this chart follows your numbers.

Backup interval (minutes)	Worst-case data loss (min)
60	60
120	120
180	180
240	240
300	300
360	360
480	480

How to read the result

RPO near zero calls for continuous replication or transaction log shipping rather than periodic backups. RPO of a day can be met with nightly backups. For RTO, measure the restore time in a real test, including data transfer, database recovery and application checks, and keep a margin for problems. Different systems deserve different targets: a payment system and an internal wiki should not share the same RPO.

Common mistakes

Counting only the time to copy files back, not detection and validation, when estimating RTO.
Assuming a backup succeeded without monitoring or test restores.
Forgetting that a replica copies deletions and corruption instantly; replication is not a backup.

Keep in mind: This check assumes backups complete instantly and always succeed. In practice the backup's own duration, failures and ransomware that encrypts backups can extend real data loss beyond the interval. Test restores regularly.

Frequently asked questions

What is the difference between RPO and RTO?

RPO looks backward and limits data loss; RTO looks forward and limits downtime.

How often should backups run?

At least as often as the RPO; many teams back up more frequently to leave margin for a failed job.

What is the 3-2-1 backup rule?

Keep three copies of data on two different media, with one copy off-site; many now add an offline or immutable copy.

Sources: NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems · ISO 22301, Security and resilience: Business continuity management systems

Checked 8 Nov 2026. Standard formulas and RFC/IEEE definitions, computed locally in your browser — nothing you type is sent anywhere.

Your numbers