Next week is Microsoft Ignite. I’ll be there and if you are there, come by my theater session Monday at 4:35pm at OCCC South – Expo Theater #3.
I’ll also be in the Zerto booth. We’re booth number 833. We have live demo labs and we can show you failover and failback between vSphere and Azure and Hyper-V and Azure.
Zerto has many customers already protecting virtual machines from vSphere and Hyper-V to AWS and Azure.
With the recent release, Zerto added several new features and fixes that make it worthwhile to upgrade the AWS or Azure Zerto Cloud Appliance (ZCA). See the release notes here.
The upgrade is really straightforward. Log into your ZCA, download the upgrade from MyZerto and then do the install. To demonstrate how easy it is, I created this video.
This week Zerto released version 5.5 Update 1. It has several features for different platforms, but 3 Azure related improvements.
• Azure China now supported
• Azure 4TB disk size for replicated VM
• Azure Storage Account support for pre-existing standard storage account
The last bullet is interesting. Being able to choose an existing Azure storage account is the one I will show in this video along with a full installation of the ZCA.
One of the most frequent questions we get at Zerto is “What do I need in Azure to use Zerto Virtual Replication (ZVR)?”
I find one of the easiest ways to visualize what Zerto is consuming in Azure is to pull up the Virtual Protection Groups (VPG) creation wizard in ZVR. For more on ZVR VPGs, see this great post from
I’ve got a vSphere site paired to the Zerto Cloud Appliance (ZCA) in Azure that I deployed from the Azure Marketplace. I’ve pulled up the VPG wizard and picked Azure as the target location for protection. This screenshot shows what ZVR is looking for in Azure in order to protect the VMs:
Looking at the left column we see very straightforward infrastructure requirements: VNet, Subnet, Network Security Group (NSG), Virtual Machine Series and Virtual Machine Size. Simply put, ZVR needs a network created in Azure, at least one subnet, a firewall (NSG), and you to tell it what size VM do you want to create.
For more flexibility of choice, the Virtual Machine Series and Virtual Machine Size can be different for testing and for production.