Disaster recovery (DR) planning is how you make sure mission-critical servers and data come back quickly after a failure, theft, fire, ransomware attack or extended power outage. A good plan is not a thick document nobody reads. It is a clear set of targets, systems and steps that you have actually tested.
The key terms
| Term | Meaning | Example |
|---|---|---|
| RTO (recovery time objective) | How long a system can be down | Accounting system back within 4 hours |
| RPO (recovery point objective) | How much recent data you can afford to lose | No more than 1 hour of transactions |
| Backup | A copy of data you can restore | Nightly backup to a backup server |
| Replication | Continuously copying systems or data to another location | VMs replicated to a standby host |
| Failover | Switching to a standby system | Starting replicas at a second site |

Step 1: Identify critical systems
List every system, then rank them by business impact. Typical tier 1 systems are finance and ERP, email, customer-facing applications and file shares that staff need daily. Set an RTO and RPO for each tier.
| Tier | Typical RTO | Typical RPO | Approach |
|---|---|---|---|
| Tier 1 (critical) | Minutes to hours | Minutes | Replication to a standby server or second site |
| Tier 2 (important) | Hours to a day | Hours | Frequent backups and a ready restore target |
| Tier 3 (non-critical) | Days | A day | Nightly backups |
Step 2: Choose your recovery methods
- Backups following the 3-2-1 rule: three copies, on two types of storage, with one off site.
- Immutable or offline backups so ransomware cannot encrypt or delete them.
- VM replication to a standby host for systems with short RTOs. See setting up virtualisation.
- A recovery site: a second office, a data centre or cloud recovery service.
- Power protection with UPS and generator or inverter capacity for load shedding.
Step 3: Document the plan
- Contact list: who declares a disaster, who does what, and supplier contacts.
- System inventory with RTO, RPO and recovery method for each.
- Step-by-step recovery procedures, written so someone else can follow them.
- Locations of backups, passwords and licence keys, stored securely off site.
- Communication plan for staff, customers and, where personal information is affected, the Information Regulator.
Step 4: Test and maintain
Test at least once or twice a year: restore complete servers, not just files, and time how long it takes against your RTO. Update the plan after every test and every major change. Pair this with high availability design to reduce how often you need it.
Frequently asked questions
What is a disaster recovery plan?
A documented, tested set of targets, systems and procedures for restoring critical IT services after a major failure or incident.
What is the difference between RTO and RPO?
RTO is how quickly a system must be restored. RPO is how much recent data you can afford to lose.
How often should disaster recovery be tested?
At least once or twice a year, and after significant changes to your systems.
What is the 3-2-1 backup rule?
Keep three copies of your data, on two different types of storage, with one copy off site.
Building a standby or backup server? Browse our storage servers or talk to our team.


