Table of contents
- Key Takeway
- Intro
- Recovery time objectives: The question that shapes everything
- Cloud backup for MSPs: When it works and when it fails
- On-premise backup appliances: Fast recovery vs. capital costs
- Hybrid backup: Combining local speed with cloud protection
- Comparing MSP backup architectures
- Microsoft 365 backup: The protection gap MSPs should sell into
- How to evaluate backup vendors for MSP use
- Which backup architecture fits which client type
- Why backup should integrate with your RMM and PSA
- Test your restores
- Frequently Asked Questions
Key Takeway
Most MSPs undercharge for backup because they don’t track storage costs against what they’re billing. Cloud-only backup works until you need to restore 2TB over a 50Mbps connection. Appliances give you fast recovery but tie up capital and limit your service area. The real question isn’t which architecture is “best” but which one matches each client’s actual recovery time requirements and budget.
Intro
Picking the right backup solutions for your MSP comes down to three things: how fast clients need to recover, how much you’re willing to manage, and whether the economics actually work at scale.
Backup is the service MSPs love to sell and hate to support. The margins look good on paper until a restore fails at 2am and you’re explaining to a client why their QuickBooks database is gone. Or until you realize the “unlimited cloud storage” you’re reselling actually costs you more than you’re charging once a client crosses 500GB.
The vendor landscape doesn’t help. Datto got acquired and pricing went up. Veeam works but the licensing model punishes growth. Axcient has loyal fans but the interface takes getting used to. And the flood of cloud-only backup startups all promise the same thing: set it and forget it, until you actually need to recover something large.
This guide skips the feature comparison matrices and focuses on what actually matters when you’re picking a backup solution: recovery speed, operational overhead, and whether the economics work at scale.
Recovery time objectives: The question that shapes everything
Before you compare vendors, ask your clients one question: How long can you be down?
Most will say “not long” without understanding what that means. Push harder. If your server dies at 9am on a Monday, can your staff work from laptops for four hours while we restore? Eight hours? A full day?
That answer determines everything. A client who can tolerate a day of downtime doesn’t need a $3,000 appliance on-site. A client who loses $10,000 per hour of downtime absolutely does.
The problem is that most MSPs skip this conversation because it’s uncomfortable. It forces clients to think about scenarios they’d rather ignore. But without it, you’re guessing at what level of protection to sell, and guessing usually means either over-engineering (killing your margins) or under-engineering (killing the client relationship when something goes wrong).
Cloud backup for MSPs: When it works and when it fails
Cloud backup makes sense for distributed workforces, laptop-heavy environments, and clients whose data fits in a reasonable footprint. The operational model is simple. No hardware to maintain, no truck rolls for capacity upgrades, no single point of failure sitting in a closet that also houses the water heater.
The math works like this: your backup software captures changes, encrypts them, and ships them to a data center. Recovery means pulling that data back down over the same internet connection.
Here’s where it falls apart. A 500GB restore over a 100Mbps connection takes about 12 hours under ideal conditions. Real-world conditions aren’t ideal. You’re competing with the client’s other traffic, dealing with ISP throttling, and hoping nothing interrupts the transfer. I’ve seen restores take three days for a server that would have been back online in 90 minutes from a local appliance.
Cloud-only works when:
- The client’s total protected data stays under 200-300GB
- They have fiber or business-class internet with real upload speeds
- Their recovery time tolerance is measured in days, not hours
- They’re not running on-premise line-of-business applications that need to come back fast
Cloud-only fails when:
- You’re protecting servers with databases that grow unpredictably
- The client’s internet goes down when the building loses power (which is often when disasters happen)
- Teams expect “we’ll restore from backup” to mean “we’ll be back up this afternoon.”
On-premise backup appliances: Fast recovery vs. capital costs
On-premise appliances store backups locally and replicate to the cloud on a schedule. When something breaks, you restore from the box in the closet instead of pulling terabytes over the WAN.
Recovery times drop dramatically. A bare-metal restore that takes 12 hours from cloud takes 45 minutes from local storage. For clients who can’t afford extended downtime, that difference justifies the hardware cost.
The tradeoffs are real, though.
Capital gets tied up in boxes. A decent BDR appliance runs $2,000-5,000 depending on storage capacity, and you’re either fronting that cost or passing it to clients who don’t love writing checks for hardware they’ll never see work (until the day it saves them).
Storage capacity hits walls. Unlike the cloud, you can’t just provision more space when a client’s data grows. You’re either replacing the appliance or adding another one, both of which mean cost and truck rolls.
Your service area shrinks. Appliances need physical access for maintenance, drive replacements, and those moments when the thing just stops working, and you need hands on it. If you’re managing clients across multiple cities, appliances make your life harder.
And there’s the single point of failure problem. If the building floods, the appliance floods with it. Cloud replication mitigates this, but only if your replication schedule is aggressive enough that you’re not losing a day’s worth of changes.
Hybrid backup: Combining local speed with cloud protection
Hybrid backup means local appliance plus cloud replication. Fast recovery from local storage, disaster protection from offsite copies. Sounds like the obvious choice until you start managing it.
You’re now running two backup targets. Two sets of alerts. Two potential failure modes. The local appliance can fail, the cloud sync can fail, and the handoff between them can fail. I’ve seen environments where local backups ran fine for months while cloud replication silently broke, leaving the client with zero offsite protection.
Hybrid also means hybrid costs. Hardware investment plus ongoing storage subscription. Some vendors bundle this cleanly; others nickel-and-dime you for every feature.
That said, a hybrid is often the right answer for mid-market clients. These are businesses with enough data and enough downtime cost that they need local recovery speed, but they’re also sophisticated enough to understand why offsite copies matter. The operational complexity is manageable if you have good monitoring and you’re actually watching the alerts.
Comparing MSP backup architectures
| Factor | Cloud-only | On-premise appliance | Hybrid |
| Upfront cost | Low (subscription) | High ($2,000-5,000+) | Medium to high |
| Ongoing cost | Scales with storage | Minimal after purchase | Both subscription + hardware |
| Recovery speed (500GB) | 12+ hours typical | Under 2 hours | Under 2 hours locally |
| Disaster protection | Strong (offsite by default) | Weak without replication | Strong |
| Best fit | Remote workforce, <300GB data | Fast RTO requirements | Mid-market with on-prem servers |
| Operational complexity | Low | Medium | Higher |
| Scales with growth | Yes | Limited by hardware | Yes for cloud tier |
Microsoft 365 backup: The protection gap MSPs should sell into
Ask your clients who backs up their email. Most will say Microsoft.
They’re wrong, and that misconception is costing you money.
Microsoft’s shared responsibility model means they protect the infrastructure, not your data. Retention windows are short: 30 to 93 days depending on the service. Ransomware that encrypts OneDrive files? Those encrypted versions sync to the cloud, and your clean copies age out. Malicious deletion by a disgruntled employee? You’ve got a few weeks to notice before it’s gone permanently.
M365 backup is one of the easiest upsells in the MSP business. Clients already understand email is critical. They just don’t realize Microsoft isn’t protecting it the way they assumed. The conversation practically sells itself once you explain the gap.
The operational side is straightforward, too. Cloud-based M365 backup doesn’t require appliances or complex configuration. You’re protecting Exchange, OneDrive, SharePoint, and Teams data to a separate cloud repository with its own retention policies. Restores are granular, meaning you can recover a single email or folder without rolling back an entire mailbox. Syncro’s M365 management capabilities go beyond backup to include security baselines and compliance monitoring across tenants.
If you’re not offering M365 backup, you’re leaving recurring revenue on the table and your clients are exposed to risks they don’t know they have.
How to evaluate backup vendors for MSP use
Skip the feature comparison charts. Every vendor claims automated backup, encryption, granular restore, and proactive monitoring. Those are baseline expectations, not differentiators.
Focus on these instead:
- Multi-tenant management that doesn’t waste your time. You’re managing backup across dozens of clients. If you’re logging into separate portals or clicking through endless menus to check status, you’re burning technician hours on administrative overhead. Look for a single dashboard that shows backup health across all clients with alerts that surface problems without you hunting for them.
- Billing integration that captures revenue automatically. Backup pricing usually scales with users or storage. Tracking that manually against what you’re invoicing is tedious and error-prone. Platforms that tie into your PSA and billing workflow eliminate reconciliation work and make sure you’re actually charging for what you’re protecting.
- Restore options for different scenarios. End-user recovers their own deleted file. The technician restores a folder from last week. Full bare-metal recovery after a server dies. Each scenario needs a different workflow, and clunky tooling makes restores take longer than they should.
- Honest documentation about what’s not supported. Every backup solution has gaps. Some don’t handle certain database types well. Some struggle with open files. Some have bandwidth limitations that affect large environments. Vendors that bury these limitations in fine print will burn you eventually. Vendors that document them clearly let you plan around them.
Which backup architecture fits which client type
Small clients with tight budgets and modest data volumes do fine with cloud-only backup. Their recovery time tolerance is probably higher than they realize, and the operational simplicity keeps your costs down.
Mid-market clients with on-premise servers and real downtime costs usually need hybrid. They’ve got enough at stake that local recovery speed matters, and they’re paying you enough that the added complexity is worth managing.
Enterprise and regulated clients might need dedicated appliances, custom retention policies, and compliance documentation you can hand to their auditors. These engagements justify higher margins because the requirements are genuinely more involved.
The mistake is treating every client the same. Selling enterprise-grade protection to a 10-person company wastes their money and your margin. Selling cloud-only backup to a manufacturing client with a 2TB ERP database sets everyone up for a bad day.
Why backup should integrate with your RMM and PSA
Managing backup as a standalone tool creates friction you’ll feel every month. Separate console means separate login, separate alert monitoring, separate reconciliation against what you’re billing.
Platforms that unify RMM, PSA, and backup in a single interface eliminate that overhead. Your technicians see backup status alongside other endpoint health data. Billing adjusts automatically when clients add or remove users. Alerts flow into the same ticketing system as everything else.
Syncro’s approach bakes Cloud Backup for M365 and Entra ID directly into the platform you’re already using for endpoint management. No separate vendor relationship, no bolted-on integration that breaks when someone changes an API.
That tight integration matters more than most feature comparisons. The best backup solution is one your team actually monitors and your billing actually captures.
Test your restores
What separates MSPs who have backup figured out from those who don’t is regular restore testing.
Pick a client. Pick a server. Restore it to a test environment and time how long it takes. Compare that to what you promised in your SLA. If there’s a gap, you’ve got a problem to solve before it matters.
Most MSPs skip this because it’s time-consuming and nothing feels broken. Then a real disaster happens, and they discover their backup solution doesn’t perform the way the sales rep claimed.
Test your restores. Document the results. Adjust your pricing and promises based on what you can actually deliver.
Want to see how backup fits into an integrated MSP platform? Try Syncro free and run a real backup-and-restore cycle before you commit.
Frequently Asked Questions
There’s no single best architecture for every MSP. Cloud-only works well for clients with limited data and flexible recovery windows. On-premise appliances are the right call when clients have fast recovery time requirements and the budget to support hardware. Hybrid backup gives you both local speed and offsite protection, but adds operational complexity. The right choice comes down to each client’s RTO, data volume, and what the economics actually support at your scale.
Most MSPs undercharge for backup because they don’t track storage costs against billing. Start by calculating your true cost per GB across your backup platform, including storage, licensing, and technician time for monitoring and restores. Then build a margin on top of that. Per-user or per-device flat-rate pricing tends to be easiest to sell and easiest to manage, but make sure your flat rate still works when a client’s storage grows.
Cloud-only backup sends data directly to a remote storage destination. Backup and disaster recovery (BDR) typically refers to a hybrid appliance model: the device stores local backups for fast restores and replicates those backups to the cloud for disaster protection. BDR solutions generally offer faster recovery times but require hardware investment and more hands-on management.
No. Microsoft’s shared responsibility model means they protect infrastructure availability, not your clients’ data. Native retention windows for Exchange, OneDrive, SharePoint, and Teams are limited to 30 to 93 days depending on the service. If a client’s files get encrypted by ransomware or permanently deleted before that window closes, the data is gone. A third-party M365 backup solution is the only way to ensure independent, recoverable copies with extended retention.
The most efficient approach is a backup platform that provides a multi-tenant dashboard showing backup health, job status, and alerts across all clients in a single view. Logging into separate consoles per client is a time sink for technicians. Platforms that integrate backup with your RMM and PSA go further by routing backup alerts into the same ticketing system as the rest of your monitoring, so nothing falls through the cracks.
Prioritize multi-tenant management, billing integration, and granular restore options over feature lists. Every vendor claims automated backup and encryption. What differentiates them is whether the tooling fits into your existing workflow, whether billing ties cleanly into your PSA, and whether the vendor documents its limitations honestly instead of hiding them in fine print.
At minimum, once per quarter per client tier. High-priority clients with fast RTO requirements should be tested more frequently. The test should simulate a real restore scenario, not just verify that backup jobs are completing. Time the restore and compare it against your SLA. If there’s a gap, you have a problem to solve before an actual disaster forces the issue.
Share










