We performed a comparison between AWS Elastic Disaster Recovery and Zerto based on real PeerSpot user reviews.
Find out in this report how the two Disaster Recovery (DR) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable aspect of CloudEndure Disaster Recovery is its instant block replication feature. This allows us to perform live block verification and eliminates the need to concern ourselves with recovery point objectives. This capability is particularly advantageous for critical workloads."
"The initial setup is really straightforward."
"It provides our disaster recovery solution. It works fine in our tests."
"We have never had any issues with scalability."
"CloudEndure Disaster Recovery is a fairly stable solution."
"For regular backup and restore solutions, this product is fine."
"We went from an organization with minimal to no disaster recovery. I was able to spin up the disaster recovery environment with AWS rather quickly and meet business requirements."
"The solution is dependent on the network bandwidth. For example, if they have a bandwidth of 10Mbps the solution will run a little heavier. If the bandwidth is good the solution runs well."
"The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so."
"The DR - Disaster Recovery - is the main selling point."
"It is incredibly granular and I really appreciate that."
"Real-time replication is a valuable feature, ensuring that changes made to the production site are immediately reflected at the recovery site."
"For us, the most valuable features are the quick upload time and how the sync works... We have VMware SRM and Veeam, and they have been pretty slow and sluggish."
"It's one of the easiest products out there, as far as managing and using it go. The UI is pretty dead simple."
"When we need to failover or move workloads, Zerto significantly decreases both the time it takes and the number of people involved. It only takes a single person to activate a failover and we can pretty much automate everything else."
"Our RPOs and RTOs are now more in line with our other critical systems."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"The failback could be improved. It should be more intuitive."
"I have not seen any areas that need improvement at this time."
"The bandwidth is a constant upload communication to the AWS DR environment, so if you do not have the proper bandwidth, it will definitely eat up your internet line."
"The UI could be a little sleeker."
"The only thing I would like to see is, they don't have a formal ticketing system. There is no way I can go back and see what questions we had six months back, what issues we had, and how they were resolved."
"Sometimes a server will get a bit behind. "
"Definitely there should be better logging. From a customer perspective I would like to see more logs on what is happening. If there is an issue, I would like to know what the problem is. Right now, we have to depend on the support of the vendor to check and let us know, because we don't have access to a lot of logging information."
"For special situations, there are options within advanced settings. You don't have to dig too far for them, but they're not quite as straightforward."
"There should be an automatic installation in a cluster. When I add a virtual client or ESX source to the cluster, it should automatically install that. There should be automatic installation. Currently, I have to do that manually."
"If there is a mass of changes to a server, Zerto will restart the replication. It would be nice to know why that happens."
"The product could benefit from improvements in automation, specifically in the area of failovers."
"It would be advantageous if Zerto had plugins for Infoblox, Cisco, or load balancers, as this would enable us to better manage those records."
"This solution could be improved if it met all the requirements that we look for including supporting multiple operating systems. We would prefer to use one solution for DR and backup."
"It needs to support more public cloud."
"The only issue I've ever had is that I wish that Zerto would work more closely with VMware. There have been a few times that Zerto has released an update but it wasn't supported with that version of VMware. I would like them to coordinate their updates with VMware's updates."
More AWS Elastic Disaster Recovery Pricing and Cost Advice →
AWS Elastic Disaster Recovery is ranked 17th in Disaster Recovery (DR) Software with 11 reviews while Zerto is ranked 2nd in Disaster Recovery (DR) Software with 236 reviews. AWS Elastic Disaster Recovery is rated 7.4, while Zerto is rated 9.0. The top reviewer of AWS Elastic Disaster Recovery writes "Free, easy to use, and offers good support". On the other hand, the top reviewer of Zerto writes "Gives us business continuity capabilities during hurricane season and in case of ransomware". AWS Elastic Disaster Recovery is most compared with Azure Site Recovery, AWS Backup, Oracle Data Guard, VMware Cloud Disaster Recovery and Veeam Backup & Replication, whereas Zerto is most compared with Veeam Backup & Replication, VMware SRM, Rubrik, Commvault Cloud and Dell RecoverPoint for Virtual Machines. See our AWS Elastic Disaster Recovery vs. Zerto report.
See our list of best Disaster Recovery (DR) Software vendors, best Backup and Recovery vendors, and best Cloud Backup vendors.
We monitor all Disaster Recovery (DR) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.