Updated November 2026: rewritten and expanded with a side-by-side comparison, RTO and RPO explained, real-world scenarios (including ransomware and Microsoft 365), and a step-by-step guide to building and testing a BCDR plan.
The short answer: business continuity (BC) is how your organisation keeps operating during a disruption: people, premises, suppliers, communications and IT. Disaster recovery (DR) is the IT part of that picture: how you restore systems, applications and data after an incident. Business continuity keeps the business running; disaster recovery gets the technology back. Together they form BCDR (business continuity and disaster recovery).
The two terms are often used as if they mean the same thing, and in a small business the same person may well own both. But they answer different questions. Business continuity asks, “How do we keep serving customers while something is wrong?” Disaster recovery asks, “How do we get our systems and data back, and how quickly?”
This guide explains the difference, shows how the two fit together in practice, and walks through how to build and test a BCDR plan that works when you need it.
What is business continuity?
Business continuity is the planning and preparation that lets an organisation keep delivering its most important services when normal operations are disrupted. It is deliberately broad. A business continuity plan (BCP) covers:
- People: who does what during an incident, who deputises if key staff are unavailable, and how staff can work if they cannot get to the office.
- Premises: where you work if your office is unusable because of fire, flood, power loss or a building problem.
- Processes: which activities must continue, which can pause, and any manual workarounds while systems are down.
- Suppliers: what happens if a key supplier, contractor or service provider cannot deliver.
- Communications: how you tell staff, customers, suppliers and, where relevant, regulators or insurers what is happening.
- Technology: what IT the business needs, and how quickly. This is where disaster recovery plugs in.
The disruption does not have to be a dramatic disaster. A cyber attack, a long power cut, a failed internet connection, theft, human error or the sudden departure of a key employee can all stop a business from operating normally. The recent shift to remote and hybrid working showed how quickly continuity plans are tested: organisations that already had secure remote access, accessible data and clear communication channels adapted faster than those improvising under pressure.
For more on the strategy side, see the importance of having a business continuity strategy.
What is disaster recovery?
Disaster recovery is the set of tools, processes and people that restore IT systems, applications and data after an incident. A disaster recovery plan (DRP) is narrower and more technical than a continuity plan. It typically covers:
- What gets recovered: servers, virtual machines, file shares, line-of-business applications, Microsoft 365 data and so on.
- In what order: the systems the business needs first, and the dependencies between them (for example, identity and networking before the applications that rely on them).
- From where: which backups or replicas you restore from, whether local, offsite or in the cloud.
- How fast, and to what point: your recovery time objective (RTO) and recovery point objective (RPO), explained below.
- Who does it: named people or a named provider, with the access and instructions they need.
Disaster recovery depends on good backups, but backup and DR are not the same thing. Backup gives you copies of your data. DR is the ability to turn those copies back into working systems within a time the business can live with. That might mean restoring onto replacement hardware, booting a server from a local backup appliance, or failing over to a recovery environment offsite. When that capability is delivered by a provider, it is known as Disaster Recovery as a Service; see what DRaaS is and why it matters.
Business continuity vs disaster recovery: the key differences
| Business continuity | Disaster recovery | |
|---|---|---|
| Core question | How do we keep operating during a disruption? | How do we restore IT systems and data after an incident? |
| Scope | Whole organisation: people, premises, processes, suppliers, communications and IT | IT: servers, applications, data, networks and cloud services |
| Goal | Keep critical services running at an acceptable level | Return systems and data to a working state within agreed targets |
| Typical owner | Senior management or a nominated continuity lead | IT manager, internal IT team or managed service provider (MSP) |
| Timeframe | Before, during and after an incident | Mainly after an incident, until systems are back |
| Key measures | Maximum tolerable downtime for each business activity; minimum service levels | RTO, RPO, restore success and test results |
| Examples | Staff working from home, a temporary office, manual order-taking, a customer communication plan | Restoring a server from backup, failing over to an offsite copy, recovering deleted Microsoft 365 mailboxes |
A simple way to remember it: business continuity is proactive and business-wide; disaster recovery is reactive and IT-focused. DR is one of the most important parts of a continuity plan, but a continuity plan without DR has nothing to restore from, and a DR plan without continuity planning restores systems with no agreed priorities.
How business continuity and disaster recovery fit together as BCDR
BCDR is the combined approach: the business decides what matters and how much disruption it can tolerate, and the IT side makes sure systems and data can be recovered within those limits.
In practice, the continuity plan sets the targets and the DR plan delivers them. If the business says, “We can’t take orders for more than half a day,” that becomes a recovery time target for the order system, the database behind it and the network it relies on. If the business says, “Losing a full day of transactions would be serious,” that becomes a recovery point target, which in turn sets how often those systems need to be backed up.
Older articles (including the original version of this one) sometimes call the combined document a contingency plan. Whatever you call it, smaller organisations often keep business continuity and disaster recovery in one document. That works well, provided the IT recovery steps, owners and test dates are clearly spelled out rather than buried in general text.
RTO and RPO explained
Two measures sit at the heart of any BCDR plan.
Recovery time objective (RTO)
RTO is the maximum time a system can be unavailable before the impact becomes unacceptable. If your accounts system has an RTO of eight hours, the plan and the technology behind it must be able to bring it back within eight hours of the decision to recover.
Recovery point objective (RPO)
RPO is the maximum amount of data, measured in time, that you can afford to lose. If your file server has an RPO of one hour, you need restore points at least every hour, so that at worst you lose an hour’s work.
Why they matter
RTO and RPO turn vague goals (“get back up quickly”) into targets you can design for and test against. Shorter RTOs and RPOs generally mean more frequent backups, faster recovery options such as local appliances or offsite failover, and more cost. Not every system needs the same targets. A sensible plan sets tighter targets for the few systems the business cannot run without, and accepts longer ones for everything else.
Real-world scenarios: continuity and recovery side by side
The difference is clearest when you look at what each plan does in a real incident.
Ransomware attack
- Business continuity: activate the incident response plan, tell staff not to use affected systems, switch to manual processes for critical work, and manage communication with customers and, where required, the Information Commissioner’s Office (ICO) and your insurer.
- Disaster recovery: isolate affected systems, identify a clean restore point from before the infection, and restore in priority order. This only works if the attacker could not reach your backups. Copies held somewhere the compromised network and admin accounts cannot touch are what make recovery possible. See how our backup and offsite DR service keeps offsite copies separate.
Server or hardware failure
- Business continuity: staff know which work can continue on other systems and who to call, and customers see minimal disruption.
- Disaster recovery: restore the server to new hardware or a virtual machine, or run it temporarily from a backup appliance while the hardware is repaired or replaced. Our onsite business continuity and disaster recovery service is designed for exactly this situation.
Loss of the office (fire, flood or power)
- Business continuity: staff work from home or a temporary location, phones are redirected, and suppliers and customers are told how to reach you.
- Disaster recovery: systems that lived in the office are recovered from offsite copies, so data is not lost with the building.
Microsoft 365 outage or data loss
- Business continuity: agree how staff communicate if email or Teams is unavailable, and how urgent customer contact is handled.
- Disaster recovery: recover deleted or corrupted mailboxes, OneDrive files and SharePoint sites from an independent backup. Microsoft keeps the service running, but protecting your data against deletion, corruption or malicious change is your responsibility. See Microsoft 365 and SaaS backup.
How to build a BCDR plan: step by step
You do not need a large team or a thick binder to build a useful plan. These steps work for most small and medium-sized organisations.
- List your critical activities. What must the business keep doing to serve customers, get paid and meet legal obligations? Rank them.
- Run a simple business impact analysis. For each critical activity, ask what happens after an hour, a day and a week without it. This gives you your tolerable downtime and data-loss limits.
- Map activities to systems and data. Note which servers, applications, files and cloud services each activity depends on, including the less obvious dependencies such as internet connectivity, identity and line-of-business databases.
- Set RTO and RPO for each system. Use the impact analysis to agree realistic targets, and be honest about which systems really need the fastest recovery.
- Choose backup and recovery methods that meet those targets. Typically this means a combination of onsite backup for fast local restores, offsite copies for site loss and ransomware, file-level backup, and Microsoft 365 backup. Our backup solutions compared guide covers the trade-offs between onsite, cloud and hybrid approaches.
- Protect the backups themselves. Keep at least one copy separated from your main network and admin credentials, so a single compromise cannot destroy every copy.
- Monitor every backup. A backup that silently fails is worse than useless, because it creates false confidence. Someone needs to check every job and act on failures; see why backup monitoring matters.
- Write the plan down and assign owners. Include contact details, decision-makers, step-by-step recovery instructions, supplier details and a communication plan. Keep a copy that is accessible when your systems are not.
- Test, review and update. More on this below.
Testing your BCDR plan
An untested plan is an assumption. Testing tells you whether your backups restore, whether your RTOs are realistic, and whether people know what to do.
Useful types of test include:
- Restore tests: regularly restore files, folders, mailboxes and whole systems from backup, and check they work.
- Recovery time checks: time a full system recovery and compare it with the RTO you agreed.
- Tabletop exercises: walk key staff through a scenario such as ransomware or loss of the office, and see where the plan is unclear.
- Contact and access checks: confirm phone numbers, supplier contacts and emergency admin access are still correct.
Review the plan on a fixed schedule, and also after any significant change: a new system, a new office, a change of IT provider, or a near-miss incident. Each test should produce a short list of fixes, and those fixes should be tracked to completion.
BCDR consulting: where a specialist partner helps
Many SMEs and MSPs understand the theory but struggle to find the time or in-house expertise to put it into practice. A BCDR consultant or specialist partner can help with:
- Assessment: reviewing what you back up today, where the gaps are, and whether your current setup could meet the recovery targets the business needs.
- Design: choosing the right combination of onsite backup, offsite DR, file backup and Microsoft 365 backup, and making sure offsite copies are kept out of an attacker’s reach.
- Implementation: deploying and configuring the backup and recovery platform.
- Ongoing management: monitoring backups, dealing with failures, and running restore tests so recovery is proven rather than assumed.
- Documentation and reporting: keeping recovery steps current and giving you clear visibility of backup status.
That is the work BCDR Solutions does. Our managed service covers onsite backup and business continuity, backup and offsite DR, file and folder backup and Microsoft 365 backup. We monitor the backup notifications we manage 24/7, give you a customisable client dashboard so you can see backup status for yourself, and include restore testing as part of the service. Offsite snapshots are held in a separate, isolated account, so an attacker who gets into your network cannot delete them.
- For SMEs: see BCDR solutions for SMEs.
- For MSPs: we offer white-label BCDR and DRaaS, so you can deliver business continuity and disaster recovery to your clients under your own brand. See BCDR solutions for MSPs and our guide to packaging DRaaS and BCDR as an MSP service line.
If you would like a second opinion on your current plan, book a free consultation, email james@bcdr.co.uk or call 01386 898324. You can also find out more about us on the BCDR Solutions home page.
Frequently asked questions
What is the main difference between business continuity and disaster recovery?
Business continuity is about keeping the whole organisation operating during a disruption, covering people, premises, processes, suppliers and IT. Disaster recovery is the IT-focused part: restoring systems, applications and data after an incident.
Is disaster recovery part of business continuity?
Yes. Disaster recovery is usually treated as a component of business continuity. The continuity plan decides what matters most and how long the business can cope without it; the disaster recovery plan makes sure IT can be restored within those limits.
What does BCDR stand for?
BCDR stands for business continuity and disaster recovery. It describes the combined approach of planning how the business keeps running and how its IT systems and data are recovered after an incident.
Do I need both a business continuity plan and a disaster recovery plan?
You need both covered, but they do not have to be separate documents. Many smaller organisations keep one combined BCDR plan, as long as the IT recovery steps, recovery targets, owners and test dates are clearly set out.
Where does backup fit into BCDR?
Backup provides the restore points that disaster recovery depends on. Without reliable, monitored and tested backups, including at least one copy kept away from your main network, neither plan will work when it is needed.
How often should a BCDR plan be tested?
Test it on a regular schedule and after any major change to your systems, premises or suppliers. Restore tests should be routine rather than a once-a-year event, because they are the only real proof that recovery will work.

