Zerto announces Virtual Replication 5.0 with Azure as replication target

At VMworld 2016 Zerto announced Virtual Replication 5.0. Virtual Replication is a replication and migration tool which protects and migrates workloads running on VMware vSphere, Hyper-V , Microsoft Azure and Amazon AWS.

One of the unique selling points of Zerto Virtual Replication is that it does not use snapshots. Snapshot have a couple of disadvantages. It can hurt performance and it does not allow to select any time in the past to restore. Snapshots are made in a frequency  of a couple of minutes or more. Zerto uses journaling allowing to restore to any point in the past (up to 30 days in release 5.0).

Virtual Replication 5.0 is expected to be GA in november  2016 . You can participate in beta testing by filling in the form here.

Besides protecting for fires, flooding and breakdown of storage, many customers use Zerto Virtual Replication to recover from a ransomware attack. Using the journal feature it is very easy to recover to a point in time just before the ransomware became active. Individual files can be restored!

Zerto Virtual Replication 5.0 Key Features are

  • Azure Support (ability to failover to Azure)
  • One-to-Many Replication
  • Zerto Mobile App for Monitoring
  • 30-Day Journal History

This PDF provides an overview of what is new.

A new feature which was requested by many customers is the ability to use Azure as a target. Both vSphere and Hyper-V are supported for replication to Azure. The image below shows the architecture. In the Azure cloud a Zerto cloud Appliance is installed. This is a D3 sized virtual machine which receives the synchronized data from the source. Zerto VR does not use replica instances. Instead all replica data is stored in an Azure storage account. When a failover test or actual failover is initiated, instances will be created by Zerto VR. This method saves on costs for running replica instances in Azure doing nothing but getting the data sync.

The data connection between source datacenter and Azure needs to be a 5Mbps or better connection.

A failback from Azure to the original location is not yet available. In 2017 this feature will become available as well as an Azure to Azure recovery scenario.

There will be a IBM public cloud to IBM public cloud recovery feature available in Q4 2016. This feature is offered as a IBM managed solution using Zerto VR under the hood.

Details on the new Azure support  in this PDF.



The journal history has been extended from 14 days to 30 days.

Vladan Seget of ESX virtualization has more details here. 

Add a Comment

Your email address will not be published. Required fields are marked *

Current ye@r *