Zerto for Microsoft Hyper-V Part 3: Replicating and Protecting VMs in a Microsoft Hyper-V Environment
By Joshua Stenhouse, Zerto Technical Marketing Manager
All VMs that require replicating and protecting in Zerto need to be configured in a Virtual Protection Group (VPG). The VMs are then replicated and recovered on a per VPG basis. A VPG has to contain at least one VM and a VM can only exist in one VPG at a time.
VPGs are typically built on a per-application basis so that multi-VM applications can be recovered or tested together. The VPG maintains the write-order fidelity of changes across all of the VMs in the VPG, ensuring they are all recovered to the exact same point in time. This in conjunction with the Zerto journal based protection allows recovery of the entire application from any point in time, with increments every few seconds, up to 5 days in the past.
Creating a VPG in Zerto 4.0 is now a 6 step process as shown below:
Pre-seeding can be configured on a per vDisk basis which means Zerto will only synchronize the changes between the disks rather than replicating an entire copy of the disk to the target site.
Configuring the networking allows the VMNics to be connected to different vSwitches and for the IP and/or MAC address to be automatically changed as part of a move, failover or failover test operation.
Zerto 4.0 also introduces a new workflow for VPG creation that brings with it the following enhancements:
- Bulk editing of storage configurations for vDisks allowing the quick configuration of individual disks in VMs to any different target storage configuration
- Bulk editing of network configurations for VMnics allowing the quick configuration of individual VMnics in VMs to different port groups and specifying different IP addresses for reconfiguration
- Import and export of IP addresses for re-ip addressing
These 3 enhancements together make Zerto extremely easy to deploy and manage in large VM environments.
Once the VPG is in a protected state, be it after an initial-sync or pre-seeding operation, Zerto will then start protecting the VMs as shown below:
Any changes you make to the protected VMs after initial VPG configuration are replicated also, such changes include:
- Live migrations between hosts
- Storage live migrations
- Adding, removing or resizing vDisks
- Adding or removing VMnics
- Changing the VM CPU or RAM specification
As Zerto is fully virtual aware it doesn’t need constant maintenance to support the day to day changes that happen in your Microsoft Hyper-V environment.
This concludes my blog post on VPG configuration, replication and recovery in Microsoft Hyper-V environments. In my next post I will cover cross-hypervisor replication.