Zerto Reviews

• Journal: ZVR uses a journal of history changes. Whenever you need to failover a VM or group of VMs, you have the ability to choose a Point in Time to which those replicas should be switched. For instance, if a disaster occurs at 10:05:00, you can failover with replicas to 10:04:55.

• Consistency Groups: If you replicate groups of VMs, then during failover, all of the VMs in groups are failed over to the exact same point in time.

• Resiliency: ZVR is resilient to Zerto infrastructure component restarts and loss of connection between sites which are automatically handled. The ZVR is very lightweight it doesn't use snapshots and has close to zero impact on production VMs and many others. It lets you get your files from Windows based VMs without failing over to replica VMs.

Before ZVR, we had many limitations in case of protecting production VMs during working hours. This primarily came from frequent VM snapshots impacting users. ZVR lets us protect our VMs without any impact upon users and greatly improved our RPOs from hours to seconds.

I would like to see a couple of details regarding awareness of VM events coming outside of ZVR. This could be a user reverting VM back to an older snapshot, which can sometimes screw up the replica, but nothing major besides it is affected.

We have used this solution for over three years.

There were no issues with deployment.

There were no issues with stability.

ZVR can handle thousands of VMs, so there were issues with scalability here.

Support is very quick in their response time and most of issues are solved in a matter of hours.

We were using Veeam Replication which is based on snapshots. However, ZVR has no snaphosts, zero impact on production, and improves RPOs seamlessly.

The initial setup was very straightforward and can be done in less than one hour. You can then start replicating between two sites.

We did the implementation in-house.

Licensing is based on the number of VMs to replicate. The first thing should be to get the number of VMs to replicate based on your business needs.

Before ZVR, I evaluated Veeam Replication, vSphere Replication, and RecoverPoint for VMs.

If you need to replicate your VMs with RPOs of seconds, then Zerto is certainly the way to go.

It is easy to setup and manage.

Provides a simple interface for VM DR.

Needs compatibility with multi-tiered applications, such as Sharepoint, for testing.

One to two years.

No.

No.

Fair, depending on which location you get in contact with: They can be difficult to deal with and don't understand the product in which they are servicing.

Not applicable.

It is very straightforward. A simple wizard to install.

I didn't personally deal with the licensing structure.

You should evaluate Site Recovery Manager by VMware. It is more expensive, but works better.

Ensure you run an evaluation and test failovers to verify it will meet your individualized needs.

Hardware-Independent Simple configuration Easy installation Integrated with vCenter Server and vCloud Director Very low RPOs

Poor documentation Poor reporting engine Bugs with rollback procedures

Allows for semi-synchronic replication, even though it's hardware independent.