What is BCDR? A guide for MSPs and IT teams
What is BCDR ? Business continuity and disaster recovery for MSPs and IT teams
Best Practices
Technology
IT Operations
BACKUP
BCDR
BEST PRACTICES
+6
Kristina Shkriabina
July 27, 2026
749 views
Share
A working guide for MSPs and in-house IT teams: recovery targets by workload, the nine parts of a plan and who owns each, a 200-endpoint cost model, the exit terms to negotiate at signing, and a plan template to copy.
Updated: November 2026
BCDR stands for business continuity and disaster recovery: keeping critical operations running during a disruption, and restoring data, systems and infrastructure after one. A BCDR plan is the single document that defines both: what stays up, what comes back, how fast, and who does it. MSPs run it as a priced service line with recovery targets and a testing schedule, and in-house IT departments run it as the plan the rest of the business relies on when systems fail.
TL;DR
The short answer. BCDR is business continuity and disaster recovery, the plan and tooling that keep a business running through an outage.
Numbers. RTO, RPO and MTD set the design, and each tighter tier carries its own price.
The plan. Nine parts, starting with a business impact analysis signed off by the people who own each function.
In-house IT. The department also plans for its own tools going down: identity, remote access, the password vault and documentation.
Cost. Budget per endpoint, then negotiate the exit terms before you sign.
Testing. Schedule restores by tier and log the elapsed time against each RTO.
Business continuity vs disaster recovery: the real difference
The two words get used interchangeably and they shouldn't be. They answer different questions and they're owned by different people.
Business continuity answers "can the client keep operating?" It covers the manual workaround when the ERP is down, the phone tree, the alternate site, the decision about which five business functions matter and which twenty can wait a week. It's a business problem, and the client owns it, so ask to see it in writing before you design the recovery side.
Disaster recovery answers "can we bring the systems back?" It covers backup, replication, failover, restore validation, and the runbook your tech follows at 2am. It's a technical problem. You own it.
Inside a company with its own IT department, the same split holds: department heads own continuity for their functions, and IT owns recovery for the systems underneath them. Our continuity plan comparison shows where incident response fits between the two.
The gap between the two is where recoveries fall short. You can hit a perfect four-hour RTO on the file server and still have a client dead in the water because nobody documented that their production line depends on a Windows XP box running a proprietary controller that isn't in your backup scope. Recovering IT isn't the same as recovering the business. If you sell BCDR, you're on the hook for both conversations, even when only one of them is billable.
Business continuity vs disaster recovery: two questions, two owners - and the gap between them
This 11-minute overview from Eye on Tech covers the same ground for a general audience:
RTO, RPO, and MTD with real numbers
Three metrics carry the whole discipline. Definitions are easy. Attaching numbers to them is where the work is.
RTO (recovery time objective) is how long a system can be down before the damage is unacceptable. RPO (recovery point objective) is how much data the client can afford to lose, measured in time. MTD (maximum tolerable downtime) is the outer limit for the business function itself, and it's always larger than the RTO of any single system underneath it.
RTO, RPO, and MTD on one disruption timeline: RPO measures data lost backward, RTO measures downtime forward
Here's what those numbers look like against real workloads and what each tier costs to deliver.
| Workload | RTO | RPO | Delivery method | Rough monthly cost per client |
|---|---|---|---|---|
| Line-of-business server (accounting, ERP) | 1 hour | 15 min | Local appliance + cloud replication, instant virtualization | $300 to $500 |
| File and print server | 4 hours | 1 hour | Image backup, local restore first | $150 to $250 |
| Microsoft 365 tenant | 8 hours | 24 hours | SaaS backup, per-seat | $3 to $5 per seat |
| Domain controller | 2 hours | 4 hours | Image backup, tested bare-metal restore | $80 to $150 |
| Workstation fleet | 24 hours | 24 hours | Image backup, reimage from gold build | $2 to $6 per endpoint |
Two things fall out of that table. First, the tightest RTO tier costs roughly three times the loosest, so every hour you shave off an RTO has a price tag you can put in front of the client. Second, a 15-minute RPO and a 24-hour RPO are different products with different prices, and anyone who asks for the first while budgeting for the second needs that spelled out in the proposal or budget request before an incident tests it.
Vendors advertise around these numbers. Axcient markets x360Recover with a 15-minute RPO and an RTO under one hour, which fits a local appliance with cloud replication. A nightly cloud-only backup has an RPO of up to 24 hours by design, whatever the datasheet headline says.
What goes into a BCDR plan
A BCDR plan is one document that combines the business continuity plan and the disaster recovery plan, with a recovery target, an owner and a test date for every system in scope. One that survives contact with an auditor or an incident has nine components. Anything shorter is a backup policy wearing a costume.
Business impact analysis. Which functions matter, ranked, with an MTD attached to each. This is a client interview, not a technical exercise.
Asset and dependency inventory. Every system in scope, plus what it depends on. The dependency column is the one people skip and the one that ruins recoveries.
RTO and RPO per system, signed off by the client in writing.
Backup architecture. Where copies live, retention, immutability, air-gap status. The 3-2-1-1-0 rule is the current baseline: three copies, two media types, one offsite, one immutable, zero errors on verification. The 3-2-1-1-0 backup rule: 3 copies, 2 media types, 1 offsite, 1 immutable, 0 verification errors
Recovery runbooks. Step-by-step, per system, written so a tech who didn't build it can follow it.
Communication plan. Who calls the client, who talks to their staff, who handles insurance and legal notification. Include phone numbers that don't live in the email system you just lost.
Testing schedule with defined test types and pass criteria.
Roles and escalation, including what happens when your on-call tech is unreachable.
Review cadence. Quarterly at minimum, and after every material change to the client's environment.
Each component has an owner and a deliverable. In an MSP engagement the client signs off the business side; in an in-house IT department, department heads and leadership do.
| Component | MSP engagement | In-house IT department | What it produces |
|---|---|---|---|
| Business impact analysis | Client interview, MSP facilitates | Department heads, IT facilitates | Ranked functions with an MTD each |
| Asset and dependency inventory | MSP | IT | System list with upstream dependencies |
| RTO and RPO per system | Client signs, MSP prices | Leadership signs, IT budgets | Signed recovery targets |
| Backup architecture | MSP | IT | Copy locations, retention, immutability |
| Recovery runbooks | MSP | IT | One runbook per tier-one system |
| Communication plan | Client and MSP | Department heads and IT | Contact tree stored outside email |
| Testing schedule | MSP | IT | Test types, dates and pass criteria |
| Roles and escalation | MSP and client | IT and leadership | Named owner and deputy per role |
| Review cadence | MSP account lead | IT manager | Dated review log |
Get the business impact analysis right and the rest follows. Get it wrong and you'll build a technically excellent recovery for systems the client could have lived without for a week.
BCDR plan, BCDR policy and BCDR strategy
The three terms get used for the same document, but they describe different layers. The BCDR policy sets the rules: which systems are in scope, who owns the plan, how often it is tested and reviewed, and who can declare a disaster. The BCDR strategy is the method chosen for each tier, such as a local appliance with cloud replication for tier-one servers, image backup for file servers, and a reimage from a gold build for workstations. The BCDR plan turns both into steps, names and phone numbers. Write the policy once, revisit the strategy when the business changes, and keep the plan current enough to follow at 2am.
Business continuity plan for an IT department
An in-house IT department sits on both sides of the plan. It recovers the systems the business runs on, and it is itself a function that has to keep working while those systems are down.
NIST SP 800-34 , the US government's contingency planning guide, sets out the order of work in seven steps:
Write a contingency planning policy statement that gives the plan its authority.
Run the business impact analysis with the head of each department.
Identify preventive controls that make disruptions less likely or shorter.
Choose a recovery strategy for each system tier.
Write the contingency plan itself, with procedures for each system.
Test the plan, train the people named in it and run exercises.
Maintain the plan as systems and staff change.
The guide was written for federal systems, and the same sequence works for a company IT department. It maps onto the nine components above.
Plan for IT's own tools going down
The part that is easy to miss is IT's own working kit. Write down how the team works if each of these is unavailable:
Identity. If the identity provider or a conditional access policy locks everyone out, recovery stops. Microsoft recommends two or more cloud-only emergency access accounts for Entra ID, kept out of day-to-day use.
Remote management. Know how technicians reach machines if the RMM or remote access tool is the system that failed.
Passwords and documentation. Keep an offline, encrypted copy of recovery credentials and runbooks, since the vault and the wiki may sit inside the outage.
Communication. Keep a contact list and a fallback channel that don't depend on company email or chat.
Vendors. List support numbers, contract IDs and escalation paths for every SaaS, backup and hardware vendor. For an in-house team they replace the escalation chain an MSP would provide.
Name a deputy for every recovery role as well. In a small team, the person who built a system may be on leave the day it fails.
Managed BCDR or in-house?
Managed BCDR means an MSP runs the backup platform, watches the jobs, performs restore tests on a schedule and carries out the recovery, with the RTO and RPO written into the contract. An in-house team keeps all of that itself. A co-managed split sits between the two: IT owns the business impact analysis and the runbooks, and an MSP runs the backup stack and the testing, as our co-managed IT guide describes. However the work is divided, the plan should name who executes each step at 2am.
What BCDR costs a 200-endpoint MSP
Here is a planning model for a mid-sized practice: 200 endpoints across roughly 20 clients, 35 protected servers and 900 Microsoft 365 seats. The ranges are planning estimates for 2026; swap in your own contract prices.
| Cost line | 2026 pricing | Annual at this scale |
|---|---|---|
| Appliance hardware | From $1,095 list for a Datto SIRIS 6; free-to-use on Datto contracts since May 2025 | $0 to $24,000, depending on vendor and model |
| Cloud replication per protected server | $100 to $300 per device per month | $42,000 to $126,000 |
| Workstation image backup | $2 to $6 per endpoint per month | $4,800 to $14,400 |
| Microsoft 365 backup | $3 to $5 per seat per month | $32,400 to $54,000 |
| Restore egress (variable) | $0 (Wasabi, Backblaze) to $0.09/GB (AWS) | $0 to $4,000+ |
| Tech time on testing and remediation | 6 to 10 hours per month | $7,000 to $14,000 fully loaded |
Call it $90,000 to $230,000 a year before you've billed a client. Cloud replication for protected servers drives most of that spread, so the per-server rate is the first number to negotiate; appliance financing and egress come next.
In May 2025, Datto BCDR appliances became free-to-use across any term length under Kaseya's commercial programs , which turns what used to be a capital purchase into monthly operating cost. The monthly service price then has to cover replication, testing hours and your margin target, and a flat add-on sold three years ago and never repriced is the first line to check.
Outside those programs, Invenio IT lists SIRIS 6 appliances from $1,095, with the upfront cost discounted in some managed-service agreements.
Egress is the line that catches people. At AWS transfer rates , a 500GB restore runs about $36 after the free tier, against $0 on Wasabi or Backblaze within their egress allowances. On a 2TB restore that spread widens to $0 versus $175. Small in isolation. Not small when your worst client year involves nine restores and you quoted the contract assuming zero.
Our breakdown of MSP backup solutions goes deeper on how the per-endpoint and per-GB models compare once restore volume is factored in. For an in-house department, the same cost lines apply without the client margin: price each tier per business function, and show finance the cost of the tier next to the revenue lost per hour of downtime from the business impact analysis.
The exit cost to negotiate before you sign
What does it cost to move BCDR vendors? These are the lines to plan for.
| Exit cost component | What it involves | How to size it |
|---|---|---|
| Data reseeding | Rebuilding full chains on the new platform from scratch | As long as your retention window, if old restore points must stay reachable |
| Dual-running | Two agents, two consoles, two bills during cutover | Overlapping licenses for that same window |
| Appliance disposition | Buyback terms, or hardware you now own and can't repurpose | $0 to full residual value, contract dependent |
| Runbook rebuild | Every recovery procedure rewritten and retested | One rewrite and one timed test per protected system |
| Contract termination | Early exit penalties on multi-year terms | Up to the remaining contract value; check the termination clause |
| Client communication | Explaining why the recovery report format changed | Unbillable, and it costs trust |
Our vendor lock-in analysis puts total switching costs for a large MSP at $165,000 to $325,000. BCDR is one of the stickiest lines in that total because the data is large, the formats are proprietary, and the migration window is exactly when you're most exposed.
The practical defense is to negotiate the exit at signing. Three clauses matter: a documented export path in a restorable format, published egress pricing that can't change mid-term, and appliance buyback terms in writing. Ask for all three before you sign, whether you're an MSP or an in-house IT team buying direct from a backup vendor.
Exit terms matter for every tool under contract, which is one reason to count how many sit with one vendor. Disclosure: Flamingo, which publishes this guide, builds OpenFrame , open, AI-native infrastructure for IT and security. It covers large areas of RMM, PSA and endpoint management in one console, with AI agents inline: Fae resolves support requests and Mingo runs IT operations, which gives technicians hours back for work like restore testing. OpenFrame doesn't back up data, so BCDR stays with your backup vendor; it costs $1 per device a month including 10M AI tokens, with a 14-day free trial.
If you're mapping alternatives in the backup and continuity space itself, our Datto alternatives guide covers the current field.
Where open source and hybrid BCDR hold up
Open source components can carry serious weight in a BCDR stack. They don't carry all of it.
Where it works: Proxmox Backup Server handles VM-level backup with deduplication and verification well enough for production, and it has no per-device licensing. Restic and Borg are solid for file-level and server backup with encryption and immutable repository support. Bacula and UrBackup cover heterogeneous environments. Paired with cheap object storage that doesn't charge egress, the raw cost per protected server drops by an order of magnitude.
Where it breaks: multi-tenancy. These tools have limited multi-tenant features, so isolating 20 clients under one console with per-tenant reporting, per-tenant retention policy and role separation that survives a compliance review takes extra work. The usual workaround is a separate instance per client, and maintaining 20 of anything erases the licensing savings fast. An in-house IT department protects one organization, so this weakness matters less there.
Instant virtualization, the feature that lets you boot a failed server from the backup appliance in minutes, is also thin outside commercial products. Nor do you get the vendor-supplied recovery report that some carriers' cyber insurance requirements call for.
The pattern that holds up is hybrid: commercial BCDR on the tier-one servers where RTO is under four hours and insurance evidence matters, open source underneath it for workstation images, dev environments, and long-tail retention. It prices each tier at what it's worth.
Testing cadence
A backup that's never been restored is a hypothesis. A cadence that holds up layers nightly automated verification, a monthly single-file restore, a boot test timed against the contracted RTO (monthly for tier-one systems, quarterly for tier two), and a yearly full failover for one client or business unit end to end. The test types, pass criteria and report template are in our guide to disaster recovery testing .
Common failure modes
Six failure patterns to check for:
Backup scope drift. A new VM gets built, nobody adds it to the protection policy, and it stays unprotected for months. Reconcile your backup inventory against your RMM asset list monthly, automatically.
Untested bare-metal restore. Image backups that verify fine but won't boot because the driver set doesn't match replacement hardware. Only a real boot test finds this.
Retention that doesn't match the threat. Mandiant's M-Trends 2026 put the global median dwell time at 14 days in 2025, so half the intrusions it investigated ran at least that long. A 14-day retention window can leave no clean restore point by the time you find the intrusion.
Credentials inside the blast radius. Backup console credentials stored in the password manager that lives on the domain you just lost. Keep an offline copy.
Undocumented dependencies. Restoring the app server without the license server, the SQL instance, or the on-prem certificate authority. The dependency map is what turns a restore into a recovery.
Unpriced RTO creep. The client's business grew, their tolerance for downtime dropped, and nobody repriced the tier. You're now delivering a one-hour RTO on four-hour money.
A backup vendor going down is its own continuity event, as this thread found out:
A BCDR plan template you can copy
Drop this into a document per client and fill it in. It's deliberately short, because the plans that get maintained are the ones someone can read in five minutes at 2am. For an in-house IT department, swap the client for the business unit and list IT's own tools in Section 2.
Client: [name] | Last reviewed: [date] | Owner: [tech lead]
Section 1, Business impact. Critical functions ranked 1 to 5, MTD per function, revenue impact per hour of downtime.
Section 2, Protected systems. System name, role, dependencies, RTO, RPO, backup method, retention, last successful restore test with date and elapsed time.
Section 3, Recovery sequence. Numbered order of restoration with dependency notes, so nobody brings the app server up before the database.
Section 4, Runbooks. One per tier-one system. Link out rather than inline.
Section 5, Communication. Client primary and secondary contacts with mobile numbers, your escalation chain, insurance carrier and policy number, breach counsel if applicable, and a statement of who is authorized to declare a disaster.
Section 6, Test log. Date, test type, systems covered, result, elapsed time versus contracted RTO, remediation items and their owner.
Section 7, Exit position. Current vendor, contract end date, notice period, documented export path, egress pricing, appliance buyback terms. Fill this in at signing while you still have leverage.
Section 7 is the one that separates an MSP running a BCDR practice from one renting somebody else's. Every other section describes how you recover a client. That one describes whether you can recover yourself.
Kristina Shkriabina
Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Blog Posts
Product Releases
Podcasts
Webinars
Case Studies
Events
Onboarding Guides
Loading related content
Frequently Asked Questions
/blog/bcdr
BCDR planning
What does BCDR stand for?
BCDR stands for business continuity and disaster recovery. Business continuity covers keeping critical operations running during a disruption. Disaster recovery covers restoring data, systems, and infrastructure afterward. A BCDR plan combines both into one document with defined recovery targets and owners.
What is the difference between BCDR and backup?
Backup is one component of BCDR. Backup copies data. BCDR defines how fast systems come back, which business functions stay running meanwhile, who executes the recovery, and how often it gets tested. A backup with no tested restore is not BCDR.
What are good RTO and RPO targets for an MSP client?
A common tiering puts line-of-business servers at a one-hour RTO and 15-minute RPO, file servers at four hours and one hour, and workstations at 24 hours on both. In our cost model the tightest tier costs roughly three times the loosest, so price each tier separately and get the targets signed.
How much does BCDR cost per endpoint?
Planning ranges for 2026: workstation image backup at $2 to $6 per endpoint a month, cloud replication at $100 to $300 per protected server a month, and Microsoft 365 backup at $3 to $5 per seat a month. In our 200-endpoint model that adds up to $90,000 to $230,000 a year. Swap in your own contract prices.
How often should a BCDR plan be tested?
Sort systems by RTO first. Tier-one systems get nightly automated verification, a monthly restore and a monthly boot test timed against the RTO; tier-two systems get the boot test quarterly. Run one full failover exercise a year, and log the elapsed time of every test against its target.
What does it cost to switch BCDR vendors?
Plan for dual-running until the new platform holds a full retention window of restore points, overlapping licenses for that window, a rewrite and timed test of every runbook, and any early termination penalty in the contract. Negotiate a documented export path, fixed egress pricing and appliance buyback terms at signing.
What is a BCDR plan?
A BCDR plan is one document that combines business continuity and disaster recovery. It covers a business impact analysis, the systems in scope with their dependencies, an RTO and RPO for each, the backup architecture, recovery runbooks, a communication plan, a testing schedule, named roles with deputies, and a review date.
What is managed BCDR?
Managed BCDR is business continuity and disaster recovery run as a service by an MSP. The provider operates the backup platform, monitors the jobs, runs scheduled restore tests and carries out the recovery, with the RTO and RPO written into the contract. A co-managed version splits that work with an in-house IT team.
How does an IT department build a business continuity plan?
Start with a business impact analysis run with each department head, then follow the NIST SP 800-34 sequence: a policy statement, preventive controls, a recovery strategy per tier, the written plan, testing and training, and maintenance. Include IT's own tools in scope: identity, remote access, the password vault, documentation and the fallback communication channel.
About OpenFrame
What's included in OpenFrame? Does it integrate with my existing tools?
OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Still deciding?
Ask Mingo answers from our docs and customer stories.