RTO (Recovery Time Objective) is how long you can afford to be down before it seriously hurts the business. RPO (Recovery Point Objective) is how much data you can afford to lose, measured in time. RTO drives how fast your recovery has to be; RPO drives how often you back up.
A simple example
Say your server fails at 2pm. If your last backup ran at midnight, you have lost 14 hours of work — that gap is your RPO. If it then takes six hours to restore and get everyone working again, that downtime is your RTO. Shrinking either one costs money, so the job is to set targets that match what the business actually needs.
How RTO and RPO shape the plan
- Low RPO (minutes, not hours) means frequent or continuous backups, and usually snapshots or replication rather than a nightly job
- Low RTO (up online in an hour, not a day) means a standby system to fail over to, or image-based recovery, not rebuilding from scratch
- Relaxed targets (a day of downtime and a day of data loss is survivable) mean a standard nightly backup is enough
The 3-2-1 backup rule is the baseline that makes any of these targets achievable. Whether recovery runs on-premise or in the cloud changes the cost and the speed.
Setting realistic targets
- Ask each department: how long can you work without this system, and how much re-keying is tolerable?
- Set different targets for different systems — the finance database and the print server are not equal
- Write the targets down, then test whether your current setup actually meets them
- Review after any major change to systems or headcount
Most small businesses discover their real recovery time is far longer than they assumed, because it has never been tested.
Want backup and recovery designed around real targets? See our backup and disaster recovery service or talk to our Edmonton team.
Frequently asked questions
What is the difference between RTO and RPO in one line?
RTO is maximum acceptable downtime; RPO is maximum acceptable data loss. One is about speed of recovery, the other about frequency of backup.
Can RTO and RPO be zero?
Effectively near-zero is possible with continuous replication and automatic failover, but the cost rises steeply. Most businesses set RPO in minutes to hours and RTO in hours.
Which matters more?
It depends on the system. For transactional data such as orders and payments, RPO usually dominates. For systems staff simply need available, RTO dominates.
How does Scandifix help?
We work out RTO and RPO per system with you, design backup and recovery to meet them, and test restores on a schedule so the numbers are real. See our backup and disaster recovery service.