Zerto for the Win!
December 04, 2021

Zerto for the Win!

Ian Hillier | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Zerto

High-value virtual servers are replicated from our primary production data center to our secondary fail-over data center. In effect, this represents the core of our disaster recovery and business continuity plans. Other, legacy backup and restore solutions were too slow to restore, and [the] speed of restore is among the most important features for our environment.
  • Speed of recovery
  • Reduction of RPO
  • Ease of use
  • Dependence on virtual protection groups
  • Release of updates to align with VMware releases
  • Product documentation could be improved
  • More peace of mind [than] hard ROI
  • Failover testing ability is key for proving DR plans
  • Not suited for VMs with very high rate of change
Very responsive, very capable. Overall, the product is very easy to set up and configure. Problems usually encroach when lower-level components are updated for changed, for instance, vSphere. Support usually can help us work through any issues that pop up from upgrades to other software, but their own updates can lag behind a little.

Do you think Zerto delivers good value for the price?

Yes

Are you happy with Zerto's feature set?

Yes

Did Zerto live up to sales and marketing promises?

Yes

Did implementation of Zerto go as expected?

Yes

Would you buy Zerto again?

Yes

Usability was the primary reason we purchased the software in the first place. We had compared it to several other software products in the same area, and it was by far the easiest to set up and use. Long-term maintenance proved to be similar, with updates driven by updates to VMware and vSphere, rather than the product itself.
For direct failover between data centers, this product excels. Of course, connectivity between data centers is at a premium and the product doesn't fare well with excessive latency. For metro area failover, it's ideal, for a longer, continental distance, the latency would probably be too much. Also, the rate of data change is key: a very high rate of data change is challenging, even with this product.