Zerto Reviews

ZVR is very simple to setup and administer. Out of the box it just works and allows me to set my replication source and destinations and nearly forget it. Our RPOs are generally 5 seconds on a replicated base of 4Tb so we have only a very small data loss in the event of needing to recover.

Now that v4.5 has been released, I have the ability to recover individual files in the event of accidental deletion or even encryption by Ransomware. This ensures that data is easily recovered no matter when it is deleted, ensuring that files that have been created and deleted in the same day and prior to backup are recoverable easily.

And, perhaps more importantly, out of the box ZVR allows me to test the failover whenever I want to verify that my systems can come up as expected.

I have been a user of Zerto Virtual Replication for 1 year.

Technical Support at ZVR is very good. Any calls are promptly responded to and dealt with to resolution. The support personnel are very knowledgeable on the product.

Initial setup is very straight forward. You simply create a group and populate your machines into the group, select a destination and voila ZVR does the rest.

Replication of business critical VMware VMs over WAN to the remote disaster recovery datacenter.

The benefits are obvious: The simplicity of the setup and the speed of replication.

The speed of WAN replication is great. It is faster compared to RecoverPoint and 20 VMs replicating over a 20Mbps VPN, which has a RPO less than one minute. Of course, your mileage will vary.

Compared to the previous DR replication solution, Zerto has decreased both RPO and RTO significantly.

In Zerto for vSphere, it is a pain to remove the virtual appliance if for some reason you lose the host.

Make sure to understand how Zerto supports Microsoft/SQL Clusters - more of an advice to the companies thinking of implementing Zerto.

One to three years.

We primarily use Zerto Virtual Replication to protect groups of servers in our production data center, replicating them to a secondary site. We also protect essential test and dev servers.

I have also used it in a past role to carry out a datacenter migration project. 

The single pane of glass in Zerto Virtual Replication and ease of use is what makes Zerto different from other replication products that I have used in the past. You can clearly see if something is not quite right in your disaster recovery plan before you have an actual disaster.

Zerto has made Disaster Recover and Business Continuity Planning tests much easier and quicker. Even when doing 'Live' tests, we are able to confirm beforehand that everything looks OK. This means less time troubleshooting on the day of the test.

The product is improving all the time and I think the Zerto team have quite a good handle on things. I found the Local ZertoCON meetup/conference particularly useful to hear about different user cases. However, sometimes it feels like the QA is not great, as the previous two updates have been bug fixes.

One to three years.

Meets all the ticks when looking for a Disaster Recovery Product/Service. Low RPO exceptional RTS. Integrates directly with vCentre Server. Easy to use.

Needs better reporting.

Improved the DR RPO and BCP.

VMware VM replication over narrow WAN bandwidth.

It needs to support more public cloud, especially in China.

Less than one year.

No stability issues so far.

No scalability issues so far.

Excellent.

No previous solution.

Very simple.

It's a little bit expensive.

Tested several other products such as NAKIVO, Veeam, VM Replication. Zerto proved to have better replication efficiency over WAN bandwidth.

It works only for a virtual platform, it does not support bare metal. If you're looking for a comprehensive solution for both virtual and physical platforms, then Veeam is a preferable solution.

• Interoperability between Hyper-V, ESX, vCloud, and AWS.
• Very easy to use
• Reliable
• Fast
• Also the architecture (on the ISP side) is designed with isolation and multi-tenancy in mind, so it's safely deployable on an ISP environment.

It allows smooth migrations which would be a lot more difficult with other technologies.

• A "manual mode" which would allow the user to failover the VMs but keeping them powered off at destination

• More powerful scripting engine

• Ability to move protected VMs between VPGs
• More reliable ETA on VPG syncronization
• root-level user for VRA installation ( at the moment the user "root" is hardcoded )
• Bandwidth throttling schedule should include days of week

I've used it for four months.

Not at all.

There were no issues.

There were no issues.

Customer Service:

Great pre-sales experience, and good support.

Technical Support:

8/10.

It was pretty straightforward.

I love the application, and it has become essential in my work.

• 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.