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."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 initial setup is pretty straightforward, it's not complex."
"Technical support has been very good. They usually respond quickly to our requests."
"The initial setup is really straightforward."
"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."
"It provides our disaster recovery solution. It works fine in our tests."
"We have never had any issues with scalability."
"For regular backup and restore solutions, this product is fine."
"Zerto is intuitive. We could set everything up in the environment within a day and a half and start migrating on the third day."
"Zerto has helped reduce our organization's DR testing to seconds to minutes. We have been able to save probably close to 200 hours a year."
"The Zerto university for training staff is very useful."
"It's very stable. It doesn't require a lot of intervention."
"The DR - Disaster Recovery - is the main selling point."
"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."
"The return to operations is the most valuable feature because it decreases the amount of time it takes us to recover."
"The ease of use is one of the most valuable features when it comes to making changes and configuring. It's very easy to set up and configure. It's a great product."
"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."
"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."
"I set up a test, deleted the source, and went to fail it back, and it didn't work."
"The failback could be improved. It should be more intuitive."
"I would like to see better support for creating and working with archives."
"Sometimes a server will get a bit behind. "
"I have not seen any areas that need improvement at this time."
"I had a couple of questions after deployment, but nothing major, about a couple of ways I could tweak it."
"The only thing we've noticed that needs improvement is the backend cleanup within VMware. There are some little issues there. I would like to see tighter integration with Vmware... orphan data is an issue within VMware. It doesn't clean up properly when you're moving stuff around."
"The number-one area in which they need to improve their product is what I would call "automatic self-healing." This is related to running them at scale... We have 1,000 VRAs and if any one of their VRAs has a problem, goes offline, all of the customer protection groups and all of the customers that are tied to that VRA are not replicating at all. That means the RPO is slipping until somebody makes a manual effort to fix the issue. It has become a full-time job at my company for somebody to keep Zerto running all the time, everywhere, and to keep all the customers up and going."
"It would be advantageous if Zerto had plugins for Infoblox, Cisco, or load balancers, as this would enable us to better manage those records."
"Some of the features need improvement. One would be, as you're creating a Move group or a VPG, as they call it, it should either autosave or have the ability so that you can save it for coming back to later because if the setup times out, you lose all your work. That would be a nice improvement to have."
"I don't have any input for improvement or a critical feature request at this moment. If anything, a lower price is always better."
"They just came out with improvements for ransomware protection last week. I haven't used them yet but, overall, security and preventing ransomware is really a hot topic these days. I would like to see it detect when the ransomware occurs and provide more information on it."
"The product could benefit from improvements in automation, specifically in the area of failovers."
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.