Centralized backup across a multi-hypervisor estate
Three hypervisors — VMware ESXi, Microsoft Hyper-V, and oVirt — scattered backups and no shared data-protection strategy. The question "what happens if the entire DC goes down?" had no good answer.
Before
- 3 independent platforms: VMware ESXi, Hyper-V, oVirt
- Each hypervisor backed up differently — or not at all
- No offsite copies — 3-2-1 rule not met
- No immutability — ransomware encrypts backups too
- RTO measured in hours, no tested DR procedures
After
- 3× Veeam Backup & Replication — one instance per hypervisor
- Scale-Out Backup Repository (Performance + Capacity Tier)
- Offsite to Azure Blob — full 3-2-1 compliance
- Object Lock in Azure — ransomware-proof copies
- Instant Recovery — critical-service RTO in minutes
Project walkthrough
The client's production environment grew organically across three independent virtualization platforms: VMware ESXi for the main production systems, Hyper-V for Windows apps and Active Directory, and oVirt for development environments. Each had its own — or no — approach to backup. There was no central repository, no offsite copies, and no guarantee of data immutability.
Our certified Veeam VMCE engineer designed an architecture based on three dedicated Veeam Backup & Replication instances — one per hypervisor. Each leverages the platform's native mechanisms: HotAdd and CBT for VMware, VSS for application-consistent Hyper-V backups (critical for AD and SQL Server), and native oVirt API integration. That shortens backup windows and yields consistent, application-aware copies.
The heart of the solution is a Scale-Out Backup Repository combining two tiers: a Performance Tier (local NVMe/SSD for instant recovery) and a Capacity Tier on Azure Blob Storage (offsite, long-term retention). Data migrates between tiers automatically per retention policy — recent backups stay local, older ones move to the cloud, closing the 3-2-1 loop.
The final, critical piece is Object Lock in Azure: copies in the Cloud Tier are immutable and cannot be deleted before retention expires. Even in a full compromise of the on-premises environment — encrypted servers, deleted local copies — the cloud data stays intact. That's what separates a backup that simply exists from one that survives an attack.
Technical deep-dive on the blog →
Would your backups survive a ransomware attack?
We'll design backup and DR tailored to your infrastructure — first consultation is free.
Free consultation →