Backup Is Not Disaster Recovery

Image: RDNE Stock project via Pexels
Most organisations we speak with can confidently say they have backups. Far fewer can confidently say they could actually recover from a serious incident — and that distinction matters enormously.
Having a backup is a bit like owning a spare tyre. It’s reassuring to know it’s there. But if you’ve never checked whether it’s inflated, or practised changing a tyre in the rain, you might find yourself stranded at the worst possible moment.
When backup systems fail at the moment they’re needed most
A striking example of this played out in New Zealand in July 2026. During a real tsunami alert, the National Emergency Management Agency’s primary website went down under the surge of public traffic. What made headlines wasn’t just the outage — it was that the backup site also failed to activate, due to third-party problems. A failover system existed on paper, but when a genuine crisis arrived, it didn’t work.
This isn’t a criticism of NEMA — it’s a lesson for all of us. It illustrates something we see regularly in the private sector: organisations that have invested in backup infrastructure but haven’t validated whether that infrastructure actually performs under pressure.
What’s the difference between backup and disaster recovery?
Backup is the process of copying your data somewhere safe. Disaster recovery is the broader plan for getting your people, systems, and operations back up and running after something goes wrong. The two are related, but they are not the same thing.
A solid disaster recovery posture includes:
- Recovery Time Objective (RTO): How long can your organisation tolerate being offline? Hours? Days? Your recovery plan needs to match reality.
- Recovery Point Objective (RPO): How much data can you afford to lose? If your backups run nightly, you could lose up to 24 hours of work in a failure — is that acceptable?
- Tested restoration: Backups that have never been restored are assumptions, not guarantees. Regular restoration tests are essential.
- Failover validation: If you have a secondary system or site, you need to know it will actually activate when called upon — not discover the answer during an incident.
- Documented procedures: In a crisis, the people who know the system intuitively may not be available. Written runbooks matter.
Recovery needs to be practiced, not assumed
The NCSC’s guidance on implementing and testing backups is clear that testing is not optional — it’s the part that makes backups meaningful. An untested backup is an unverified assumption about something you may desperately need to be true.
We’d encourage any organisation to ask itself honestly: if your primary systems went offline right now, how long would recovery actually take? Have you tested it? Does your team know what to do? If those questions feel uncomfortable, they’re worth sitting with.
Business continuity planning doesn’t need to be overwhelming — it just needs to be real. If you’d like a conversation about where your organisation stands, our team is always happy to help.
Jessica Falconer
Director, Resolve Technology
When she’s not wrangling IT strategies, Jessica can be found wrangling labradoodles, teenagers, and parishioners — not necessarily in that order.
Need help with this?
Resolve Technology can help. Learn more about our SmartManage Managed IT services, or get in touch to discuss your needs.
