Blog 18.11.2026r.

Managed Backup for MSPs: From Insurance Policy to Frontline Service

Managed backup for MSPs after VMware: multi-tenant OpenStack protection, RPO/RTO in the SLA, EU data sovereignty and flexible licensing.

Managed backup for MSPs has evolved from a technical safeguard into a business-critical service. Clients increasingly expect more than a copy of their data: they want predictable recovery times, protection against ransomware, clear service levels and confidence that their information is secure.

For managed service providers (MSPs), this creates an opportunity to build recurring revenue while helping customers address increasingly complex data protection requirements. But delivering managed backup at scale requires the right technology, operational processes and commercial model.

Key takeaways

  • Managed backup means taking responsibility for the full backup lifecycle: configuration, monitoring, verification and recovery, all governed by clearly defined service levels.
  • Changes in the virtualization market are encouraging MSPs to explore open platforms such as OpenStack, Proxmox VE and XCP-ng, as well as multi-hypervisor strategies.
  • Ransomware protection should combine immutable backup copies with appropriate isolation mechanisms.
  • RPO, RTO and documented recovery tests help turn technical capabilities into measurable service commitments.
  • Flexible licensing and centralized management help MSPs build services that can scale across different customer environments.

Why businesses turn to managed service providers

Companies increasingly rely on external specialists to operate, maintain and secure their IT infrastructure. Several factors are driving this shift.

The growing scale of cyber threats. Ransomware, phishing and supply-chain attacks make data protection an ongoing operational responsibility. Businesses need more than scheduled backup jobs: they need monitoring, incident response procedures and reliable recovery options.

Regulatory requirements. Frameworks such as NIS2, DORA and GDPR increase the importance of documented security controls, business continuity and appropriate data handling. The specific obligations depend on the organization, its sector and its role in the relevant regulatory framework. Many smaller businesses lack the resources to interpret and implement these requirements independently.

The shortage of specialist skills. Maintaining an experienced IT team is expensive and increasingly difficult. Smaller organizations often cannot justify dedicated backup, infrastructure and security specialists.

A shift from reactive to preventive IT. The traditional approach of fixing problems after they occur is giving way to continuous monitoring, proactive maintenance and tested recovery procedures.

Managed services address these challenges by giving businesses access to specialist expertise without requiring them to build every capability in-house. Backup and disaster recovery are an important part of that model.

From an insurance policy in a drawer to a frontline service

For years, many companies treated backup like an insurance policy: something that was configured once and checked only when disaster struck.

That approach is no longer sufficient. A backup copy has limited value if it cannot be restored when the business needs it. What matters is whether the data is protected, whether recovery procedures work and how quickly critical systems can return to operation.

This changes the role of backup. It becomes an active part of business continuity, rather than a background IT task.

For smaller organizations, building and maintaining a mature data protection environment can be difficult. They may lack the infrastructure, specialist knowledge or staff needed to monitor backup operations and regularly test recovery scenarios. An MSP can provide these capabilities as a managed service.

What is managed backup?

Managed backup is a service in which a provider takes responsibility for operating and overseeing a client’s backup environment. This typically includes configuration, scheduling, monitoring, verification, retention management and recovery assistance.

Instead of purchasing backup infrastructure, managing software licenses and supervising backup jobs internally, the customer receives a service delivered under an agreed scope and service-level agreement (SLA).

The exact responsibilities depend on the contract. An MSP may manage the entire backup infrastructure, provide backup software and monitoring, operate a shared environment for multiple customers, or deliver a broader Backup as a Service (BaaS) offering.

The distinction is important: a managed backup service is not simply software access. It combines technology with operational responsibility.

What the changing virtualization market means for MSPs

The virtualization market is going through a period of change. Following Broadcom’s acquisition of VMware, changes to licensing and commercial models have encouraged many organizations to reassess their infrastructure strategies.

Some are evaluating alternatives. Others are adopting multi-hypervisor environments to reduce dependency on a single platform. Open virtualization and private cloud technologies, including OpenStack, Proxmox VE and XCP-ng, are part of this discussion.

For MSPs, supporting a wider range of platforms creates both an opportunity and an operational challenge. They need backup tools that can protect different customer environments without forcing them to maintain a separate management process for every hypervisor.

Storware Backup and Recovery supports a broad range of virtualization and private cloud platforms, including VMware, OpenStack, Proxmox VE, XCP-ng, Nutanix AHV, Oracle Linux Virtualization Manager and VergeOS. Supported platforms and versions depend on the product release and configuration; the current Storware Support Matrix provides the complete compatibility information.

Multi-tenant backup management for OpenStack

OpenStack is particularly relevant to cloud service providers and MSPs operating multi-tenant infrastructure.

Storware integrates with OpenStack through Horizon and Skyline plugins, allowing backup operations to be incorporated into familiar cloud management workflows. Role-based access control (RBAC) supports the separation of administrative responsibilities and permissions.

Providers that want to offer a branded self-service experience can also use Storware’s documented REST API to build their own customer-facing backup portal.

This gives MSPs flexibility in how they package and deliver backup services, while retaining control over the underlying infrastructure and service model.

Agentless protection in a multi-hypervisor environment

At the scale of hundreds or thousands of virtual machines, installing and maintaining a separate backup agent in every guest operating system can create significant operational overhead.

Storware Backup and Recovery uses an agentless architecture for supported virtual environments, communicating with the underlying platforms through their available APIs and backup mechanisms.

There are documented exceptions. Microsoft Hyper-V uses a lightweight host agent, while file-level protection uses the Storware OS Agent.

For MSPs, this approach can simplify deployment and ongoing operations across supported environments. Rather than managing a separate guest-level agent installation for every virtual machine, providers can use platform-level integration where available.

Data sovereignty and regulatory requirements

For MSPs serving public-sector, healthcare and financial customers, the location and jurisdiction of backup data can be important parts of the service design.

Customers may need to know where their data is stored, which providers process it, who can access it and which contractual and technical safeguards apply.

A flexible backup architecture allows an MSP to select storage destinations according to customer requirements. These may include local repositories, network storage and object storage services, including providers operating data centres in the European Union.

Storware supports a range of backup destinations, giving service providers options when designing storage architectures for different customers.

However, choosing an EU-based storage location does not by itself guarantee regulatory compliance or data sovereignty. The provider, storage location, contractual arrangements, access controls, encryption and applicable jurisdiction all need to be considered.

For a deeper discussion, see our article on Data Sovereignty and Compliant Backup.

Ransomware protection: immutability and isolation

When an MSP delivers backup as a service, it plays an important role in helping customers recover from ransomware incidents. A robust design should consider not only how backup copies are created, but also how they are protected from unauthorized access, modification or deletion.

Two useful mechanisms are immutability and isolation.

Immutable backup repositories

Storware supports immutable backup configurations using supported storage technologies, including XFS-based repositories.

Immutability helps prevent backup data from being modified or deleted during a configured retention period. This can reduce the risk that compromised credentials or malicious activity will affect existing recovery points.

The level of protection depends on the repository configuration, access controls and the security of the underlying operating system and infrastructure. Repository hosts should therefore be hardened, administrative access restricted and backup credentials separated from production environments wherever possible.

Isolation with isoLayer

Storware’s isoLayer provides an additional isolation mechanism for supported repository configurations.

The secondary storage share is mounted for the duration of backup and restore operations rather than remaining continuously accessible. This reduces the period during which the repository is exposed to the surrounding environment.

Immutability and isolation address different aspects of the threat. Combining them can strengthen a backup architecture, but neither should be treated as a substitute for network segmentation, access management, monitoring and tested recovery procedures.

Learn more in our guide to Immutable and Air-Gapped Backup.

Disaster recovery: RPO, RTO and restore testing

A backup that cannot be restored within the required timeframe may not meet the customer’s business continuity needs.

A managed backup service should therefore be designed around measurable recovery objectives.

ParameterWhat it definesWhy it matters for the MSP
RPO (Recovery Point Objective)The maximum acceptable amount of data loss, expressed as a period of timeDetermines backup frequency, retention design and storage requirements
RTO (Recovery Time Objective)The target time for restoring a service or systemInfluences recovery architecture, infrastructure capacity and staffing
SLA (Service Level Agreement)The contractual service commitments, responsibilities and reporting arrangementsDefines what the MSP promises to deliver and how performance is measured

There is no universal RPO or RTO suitable for every customer. A file server, a business-critical database and a development environment may have very different recovery requirements.

MSPs should establish these objectives with each customer and design the service accordingly. Tighter targets may require more frequent backups, additional infrastructure, reserved recovery capacity or more extensive operational coverage.

Why restore testing matters

Successful backup jobs do not automatically prove that recovery will work.

Regular restore tests help verify that data can be recovered and that documented procedures are practical. They also give the MSP evidence to assess whether agreed recovery objectives are achievable.

A useful recovery test should record what was restored, which procedures were followed, how long the process took and whether the result met the expected criteria.

For an MSP, this information is valuable in two ways: it helps improve service quality and gives customers tangible evidence of the work being performed.

Turning managed backup into recurring revenue

Managed backup can become a predictable service line when the MSP combines a scalable technical platform with a clear commercial model.

A typical service can be built around several elements:

  1. Shared backup infrastructure. The MSP operates a centrally managed environment that can protect multiple customer environments.
  2. Customer-specific policies. Each customer receives backup schedules, retention settings, access permissions and recovery procedures suited to their requirements.
  3. Flexible service tiers. The MSP can differentiate offerings by retention, monitoring, recovery assistance, storage destination and agreed service levels.
  4. Transparent billing. Pricing can be based on a suitable metric, such as protected virtual machines, hosts or front-end capacity, depending on the licensing model and service design.
  5. Additional services. Disaster recovery planning, recovery testing and support can complement the core backup offering.

The result is a service that can grow with the MSP’s customer base without requiring every customer to have a completely separate management platform.

Flexible licensing as an MSP advantage

The licensing model has a direct impact on the economics of managed backup. MSPs need to understand how software costs change as customer environments grow and how those costs translate into their own service pricing.

Storware offers several licensing models for supported environments, including per-host, per-VM and front-end capacity-based licensing. Additional licensing arrangements apply to specific workloads and integrations, such as OS Agent protection and external backup provider integrations.

The appropriate model depends on the protected environment, workload type and service architecture. MSPs should select the option that best matches their customers’ infrastructure and commercial requirements.

This flexibility can help providers design different service packages and align software costs with the way they charge customers. For current licensing details and eligibility, see the Storware licensing page.

Six pillars of an effective managed backup service

A scalable managed backup offering should be built around six principles:

  1. Broad workload coverage. Support the virtualization platforms, applications and infrastructure types that customers actually use.
  2. A resilient storage architecture. Apply the 3-2-1 backup principle: maintain three copies of data, on two different types of media, with one copy off-site. Where appropriate, extend the design with an additional immutable or isolated copy and regular recovery verification.
  3. Ransomware protection. Combine immutability, isolation, access controls and secure infrastructure management.
  4. Centralized monitoring and administration. Manage multiple customers and environments through consistent operational workflows, with appropriate separation of access and responsibilities.
  5. Regular recovery testing. Verify that backups can be restored and document the results.
  6. Defined disaster recovery objectives. Agree on RPO, RTO and service responsibilities with each customer, then design and price the service accordingly.

These principles help MSPs move beyond simply storing backup copies and build a service that supports customer business continuity.

Frequently asked questions

What is managed backup for MSPs?

What is the difference between managed backup and Backup as a Service (BaaS)?

Which RPO and RTO should an MSP offer?

How do immutable and isolated backups help protect against ransomware?

Can an MSP protect OpenStack environments with Storware?

Does managed backup automatically make a customer compliant with NIS2, DORA or GDPR?

Build your managed backup service with Storware

Storware Backup and Recovery helps service providers protect supported virtualization and private cloud environments through centralized management, multi-platform integration and flexible licensing options.

Building a BaaS or DRaaS service line? Explore Storware for MSPs and see how Storware can support your managed backup offering.

Sources 

  • Rimini Street / Unisphere Research survey, 2026, reported by Computing 

Blog

You might also like...

Data Sovereignty vs Data Residency: What Changes for Backup Blog

Data Sovereignty vs Data Residency: What Changes for Backup

Data residency is where data sits; sovereignty is whose law applies. What that means for backup copies under GDPR, NIS2, DORA and the Data Act.

Read more
Building a Minimum Viable Company for Cyber Recovery Blog

Building a Minimum Viable Company for Cyber Recovery

Backup alone won't save you after a cyberattack. Learn how a Minimum Viable Company plan sets recovery priorities, tiered RTO/RPO and tested runbooks.

Read more
OpenStack DR Runbook: A Free Template Blog

OpenStack DR Runbook: A Free Template

A ready-to-adapt OpenStack disaster recovery runbook: roles, declaration criteria, workload tiers, and a phase-by-phase recovery procedure.

Read more

Ready to protect your data?