🧭 RPO / RTO 🗓 Retention 🧪 Tested Recovery 📋 Checklist 🧭 RPO / RTO 🗓 Retention 🧪 Tested Recovery 📋 Checklist
Disaster Recovery

Backup Is the Foundation of Your Recovery Plan
RPO · RTO · Retention · Tested Recovery

A disaster recovery plan is the act of deciding in advance how much data you can lose and how quickly you must be back. Those two numbers — RPO and RTO — come directly from your backup design. Below is how to set them and where backup sits in the plan.

No credit card required · 14-day free trial

Core Concepts

What Are RPO and RTO?

Without these two numbers you cannot choose a backup frequency sensibly.

RPO — acceptable data loss

"At most how many hours of data can I lose?" This sets your backup frequency directly. Hourly backups mean a one-hour RPO.

RTO — time to recover

"How quickly must the system be back?" This drives your restore speed and readiness.

🗓

Retention

How far back must you be able to go? How late you might notice a problem decides this.

🧪

Test cadence

How often is the plan rehearsed? An untested plan is a wish, not a plan.

Applying It

Backup Frequency by RPO Target

This mapping is a practical starting point for most businesses.

📄

Brochure site

Content rarely changes; weekly or daily is enough and RPO can be a few days.

📰

Blog / news

Daily is reasonable — you lose at most one day of content.

🛒

Ecommerce

Daily gets expensive fast. Hourly brings RPO down to one hour.

🏪

High-volume store

More frequent than hourly may be warranted, driven by order volume.

🗄

Split by component

Files change rarely, databases constantly. Separate frequencies protect more and cost less.

Make it cheaper with incremental

Incremental makes frequent backups economical. Details.

Checklist

Is This Written Down?

In a crisis you need a document to read, not a memory to recall.

1️⃣

Critical systems

Which systems come back first? Is the order written down?

2️⃣

RPO / RTO targets

Is an acceptable loss and recovery time defined per system?

3️⃣

Backup location

Where are the backups? Who can access them? Where is the encryption key?

4️⃣

Restore steps

Are the steps documented, or in one person's head?

5️⃣

Communication

Who tells whom, and when? Who owns client notification?

6️⃣

Test schedule

When was the plan last rehearsed? Were the results recorded?

Backup is the foundation of the plan — but it is not the plan

Recovery is impossible without a backup, yet having one is not sufficient on its own. Most of the time lost in a crisis goes not to "was there a backup?" but to "who restores it, from where, and how?"

So prepare three things alongside your backups: written restore steps, pre-defined authorised people, and your encryption key stored independently of the server. If the key existed only on the server you lost, your encrypted backup is lost with it.

FAQ

Disaster Recovery Plan — Frequently Asked Questions

RPO (Recovery Point Objective) is the maximum data loss you can accept — the answer to "at most how many hours of data can I lose?" — and it directly determines your backup frequency. RTO (Recovery Time Objective) is how quickly the system must be back up. A site backed up hourly has a one-hour RPO; one backed up daily has a 24-hour RPO.
Work backwards from your RPO target. If you cannot accept losing a day of orders, daily backups are insufficient. A practical mapping: weekly or daily for brochure sites, daily for blogs and news sites, hourly for ecommerce, and more often than hourly for high-volume stores. Because files change rarely and databases constantly, giving the database a higher frequency both protects more and costs less.
The deciding question is how late you might notice a problem. Silent corruption and undetected intrusions can surface weeks later, and if your retention is short every backup you hold already contains the problem. If you process personal data you should also set a limit: data protection law generally requires not keeping data longer than the processing purpose requires.
At minimum: which systems are critical and in what order they are recovered, RPO and RTO targets per system, where backups live and who can access them, written restore steps, who is notified and when, and how often the plan is tested. An untested plan is a wish rather than a plan.
No. Business continuity is the broader framework covering how the business keeps operating during an incident, while disaster recovery focuses on how technical systems are brought back. Backup is the foundation of disaster recovery but is not a plan by itself.

Build a Plan That Matches Your RPO Target

Per-component frequency, retention counts and verification in one panel. 14 days free.

Create Free Account

Backup verification →