Uncategorized

RTO and RPO Explained: Why Your Backup Isn’t a Backup Until You’ve Restored It

Colourful floppy disk on a yellow background, representing RTO and RPO backup recovery

Somewhere in your business, a backup report lands in an inbox every morning with a green tick on it. Nobody reads it. Nobody needs to. It says the job ran.

What it doesn’t tell you is how long it would take to get the business trading again from that copy, or how much work you would lose doing it. Those two numbers have names: RTO and RPO. This guide explains both in plain English, gives you a worksheet to set them for every system you rely on, and gives you a restore test you can run this quarter.

If you would rather someone owned this for you, recovery testing is part of how we deliver managed IT services and cyber security services for Australian businesses.

What are RTO and RPO?

RTO (recovery time objective) is how long a system can be down before it seriously hurts the business. RPO (recovery point objective) is how much data you can afford to lose, measured in time.

Put simply, RTO is the clock on the wall and RPO is the clock on the data.

Take your accounting system. If finance can work around an outage for half a day but no longer, its RTO is four hours. If re-keying an hour of invoices is annoying but survivable, and re-keying a full day is not, its RPO is one hour. That means you need a backup at least every hour, and a way to restore it in under four.

The two numbers are independent. Email might tolerate being down for a morning but not losing a single message. A file archive might be fine offline for two days but should not lose anything at all. Each system gets its own pair.

Why a successful backup job doesn’t mean you can recover

A green tick proves a copy was made. It does not prove the copy is complete, uncorrupted or restorable inside your RTO.

These are the gaps we see most often when a business actually tries to restore:

  • The files were backed up, but the application settings and configuration were not, so the data has nowhere to go.
  • The restore works, but pulling two terabytes back over the office internet connection takes three days, against an RTO of one.
  • The backups sit on the same network, under the same admin account, as everything else. Ransomware that reaches production reaches the backups too.
  • Nobody has written down the restore steps, and the one person who knows them is on leave.
  • Everyone assumed Microsoft 365 was backed up because it lives in the cloud.

Most providers report on the backup job because it is easy to report on. We would rather report on the restore, because that is the only number that matters on the day. Security first means proving recovery before you need it, not discovering the gaps in the middle of an incident.

The Australian benchmark agrees. ASD’s Essential Eight treats restore testing as part of the control, not an optional extra: at every maturity level, restoring data, applications and settings from backups is expected to be tested as part of disaster recovery exercises.

The cost of getting it wrong is not abstract. In ASD’s latest Annual Cyber Threat Report, the average self-reported cost of cybercrime per report for a small business was $56,600 in 2024-25, up 14%. A backup that restores in hours rather than days is one of the few things that directly shrinks that number.

How to set RTO and RPO for each system in your business

Setting RTO and RPO is a business decision, not an IT one. The person who owns the process should decide how much downtime and data loss it can take, and IT should then prove whether the current backup strategy can deliver it.

Work through it in four steps:

  1. List every system the business would miss within a day: finance, email, files, job or practice management, CRM, phones.
  2. For each one, ask the owner two questions. How long can we go without this? How much work could we afford to redo?
  3. Write the answers down as hours, not as “as fast as possible”. Everyone wants zero. Zero costs money.
  4. Compare the targets against what your backups actually do today: how often they run, and how long the last restore took.

Here is the worksheet we use. Copy it into a spreadsheet and fill in one row per system.

SystemBusiness ownerRTO (max downtime)RPO (max data loss)Backup frequencyLast restore testResult
Accounting systemFinance manager4 hours1 hourHourly[date]Restored in [x] hours
Email and calendars (Microsoft 365)Operations manager4 hours1 hour[check][date] 
Shared files (SharePoint or file server)Each team lead1 day4 hours[check][date] 
Job, practice or project management[owner][ ][ ][check][date] 
CRMSales lead[ ][ ][check][date] 

Any row where the last restore took longer than the RTO, or the backup runs less often than the RPO, is a gap. Each gap is either a budget conversation or a risk the owner is choosing to accept. Both are fine, as long as someone chose it on purpose.

The 3-2-1 backup rule, and why immutable backups now matter

The 3-2-1 backup rule says keep three copies of your data, on two different types of storage, with one copy offsite. It is still the right starting point, because it stops one failure (a dead server, a flooded office, a cancelled cloud account) from taking every copy with it.

What has changed is the attacker. Ransomware crews now go looking for backups first, because a business that can restore does not pay. That is why many providers now talk about 3-2-1-1-0: one copy that is immutable or offline, and zero errors when you test a restore.

An immutable backup is a copy that cannot be changed or deleted for a set period, even by an administrator. If an attacker gets admin access, they still cannot wipe it. The Essential Eight makes a similar point by limiting which accounts can access, modify or delete backups, with tighter limits at each maturity level.

How to run a restore test this quarter

Pick one critical system from your worksheet and run this checklist. It takes a few hours, and it will tell you more than a year of green ticks.

  1. Restore to an isolated location, never over the live system.
  2. Start a timer the moment you begin.
  3. Restore the data, the application and its settings to the same point in time, so they actually work together.
  4. Have the system’s business owner check it: open files, run a report, look up a client.
  5. Record how long it took against the RTO, and how recent the data was against the RPO.
  6. Write down every step that was not documented, and who had to be asked.
  7. Fix the gaps, update the worksheet and book the next system.

Test your most critical systems at least once a quarter, and again after any major change, such as a new server, a move to the cloud or a change of backup product.

How does backup testing fit your business continuity plan?

Restore testing is the part of your business continuity plan that proves the IT promises in it are real. The plan covers people, communication and workarounds. RTO and RPO are the numbers IT commits to inside it, and the restore test is the evidence.

If you have not built that plan yet, start with our business continuity plan checklist for Australian businesses [INSERT LINK: October BCP blog URL]. If the reason you are reading this is that something has already gone wrong, read what your business must do after a data breach [INSERT LINK: September data breach blog URL].

Know your recovery time before you need it

Most businesses find out their real recovery time on the worst day of the year. You can find out on a quiet Tuesday instead.

Want a second set of eyes on your backups and recovery? Book a free 45-minute security review with Corp IT.

Frequently asked questions

What is the difference between RTO and RPO?

RTO is how long a system can be down; RPO is how much data you can afford to lose. RTO drives how fast your restore needs to be, and RPO drives how often your backups need to run.

How often should backups be tested?

Test restores of your most critical systems at least quarterly, and after any major change to your systems or backup product. ASD’s Essential Eight expects restores to be tested as part of disaster recovery exercises at every maturity level, so a backup that has never been restored should be treated as unproven.

Does Microsoft back up my Microsoft 365 data?

Microsoft keeps the service running and holds deleted items for a limited time, but that is not the same as a backup you control and can restore to any point in time. Microsoft’s own services agreement recommends that you regularly back up your content and data.

What is an immutable backup?

An immutable backup is a copy that cannot be changed or deleted for a set period, even by an administrator. It protects you when an attacker gains admin access, because the one copy you need for recovery stays untouched.

What is the 3-2-1 backup rule?

The 3-2-1 backup rule means keeping three copies of your data, on two different types of storage, with one copy offsite. It stops a single failure, such as a dead server, a flooded office or a cancelled cloud account, from taking out every copy. Many providers now extend it to 3-2-1-1-0, adding one immutable or offline copy and zero errors on a test restore.

Do I still need an immutable backup if I follow the 3-2-1 rule?

Yes, for most businesses. The 3-2-1 rule protects against hardware failure and site loss, but it doesn’t stop an attacker with admin access from deleting or encrypting every copy they can reach. An immutable backup can’t be altered or deleted for a set period, even by an administrator, so at least one clean copy survives. Immutability depends on how your backup platform is configured, so confirm it is switched on and test a restore from that copy.

What is disaster recovery testing?

Disaster recovery testing proves your systems and data can be restored within your RTO and RPO by actually doing it, rather than relying on a successful backup report. For most businesses it starts with a timed restore of one critical system to an isolated location, checked by the system’s business owner. Repeat it at least quarterly and after any major change. Wider exercises, such as walking your team through a full outage scenario, build on that foundation.

What should a backup strategy include?

A backup strategy starts with an RTO and RPO for each critical system. RTO is how long a system can be down and RPO is how much data you can afford to lose. Those targets decide how often backups run, where copies are stored and how fast they must restore. It should follow the 3-2-1 rule, include an immutable or offline copy, cover application settings and Microsoft 365 data as well as files, and name an owner for each restore. Backup and restore are two halves of one process, so a strategy that plans only the backup half is incomplete.

More Blogs

Book your free consultation today.

Lay the foundations for smarter, safer IT.

MENU