Zerto for Microsoft Hyper-V Part 1: Features, Requirements & Cross-Hypervisor Replication
By Joshua Stenhouse, Zerto Technical Marketing Manager
As part of the Zerto 4.0 release we have announced support for the Microsoft Hyper-V hypervisor. This is the first blog post in a series where I will cover supported features and topologies, requirements and installation, replicating and protecting VMs then finally cross-hypervisor replication and recovery.
All of the same great functionality we have for VMware environments has now been ported to Microsoft Hyper-V, including but not limited to:
- Storage agnostic replication and recovery on a per VM basis
- An RPO of seconds with continuous block level replication
- Journal based protection allowing recovery to previous points in time every few seconds up to 5 days in the past
- Multi-VM protection using Virtual Protection Group technology to maintain write-order fidelity across a multi-VM application for consistent recovery
- An RTO of minutes with boot ordering, re-IP addressing and custom scripting
- Recovery testing with no shutdown in production or break in replication
- Scalable Virtual Replication Appliance technology
- Application centric SLAs defining business continuity alerts and data retention
- Built-in WAN acceleration, compression and bandwidth throttling on a time schedule
- Priority and QOS on a per Virtual Protection Group basis
- Single click failback configuration
- Commit policy allowing rollback out of a failed recovery to a different point in time
Zerto support for Microsoft Hyper-V also allows for the following replication topologies:
As you can see, with Zerto you now have the exciting prospect of not only being able to replicate between Microsoft Hyper-V datacentres, but also from and to VMware vSphere, making Zerto hypervisor agnostic as well as storage agnostic. This now allows you to consider the following protection scenarios when it comes to VM replication and recovery:
- VMs from Microsoft Hyper-V into a VMware vCD cloud provider for DRAAS
- Tier 1 VMs between Microsoft Hyper-V sites
- VMs from Microsoft Hyper-V satellite offices into a VMware vSphere datacentre
- VMs from a VMware vSphere primary datacentre into a Microsoft Hyper-V recovery site to utilize Microsoft licensing
Even if you don’t have a specific need for any of the above configurations today then the most important benefit of this could just be your ability to negotiate the next time your licensing is due for renewal, as not only are you no longer tied to keeping the same storage vendor between your sites neither are you now tied into having to keep the same hypervisor vendor.
It should be noted that Zerto 4.0 will support replicating from Microsoft Hyper-V to a VMware vSphere powered Zerto Cloud, but there is no support for a Microsoft Hyper-V based Zerto cloud provider yet.
In my next blog post I will cover the installation requirements for Zerto in a Microsoft Hyper-V environment.