We performed a comparison between VMware SRM (Site Recovery Manager) and Zerto based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Zerto wins out in this competition. Its consistent sub-second response for RTO and RPO makes it one of the most responsive and fastest in the marketplace today. Users are able to easily run tests and change scenarios without any effect on an organization's production.
"The most valuable feature of the solution is the integration part, along with the subsequent hardware."
"The most valuable feature is the automation, where you press a button and everything fails over seamlessly."
"I like how VMware SRM is able to automate and orchestrate disaster recovery."
"The thing I like the most about SMR is the reduced cost of management."
"The replication is a key feature."
"VMware SRM's most valuable features are its convenience and its use of stretched clusters."
"The solution is scalable."
"It eliminates the need for complex compliance requirements, making it a highly effective solution."
"When we replicated our data, I turned up the machine, and it was up in seconds. It blew my mind. I could not believe it."
"Zerto's user-friendliness is valuable."
"Its automation and the ability to replicate and keep an RTO of just seconds is valuable. It is all automatic. Everything is pretty transparent on the backend. It is just point-and-go."
"The granularity enables us to failover specific workloads instead of an all-or-nothing type of scenario, where you have to move your entire IP block and your data center, or you have to move large chunks of VMs. Those situations also make it prohibitive to test effectively."
"The most valuable feature is real-time replication, where we have the ability to recover things in near real-time."
"We can use Zerto to help protect our VMs."
"Zerto is low maintenance, so I can set it and forget it. It has a great process and an excellent solution."
"The UI is straightforward. It makes it very simple to group our resources and understand that our production workloads are covered because we can set them up as granular or as non-granular as we want."
"SRM has to be installed on two separate data centers, so both have to be coordinated very well, which becomes complicated when configuring the software for disaster recovery."
"The initial setup of VMware SRM isn't straightforward because many customizations are required since it helps in the recovery of your IT environment."
"One thing which is lacking from the SRM is reporting."
"In general, the drawbacks of VMware SRM, where improvements can be made, stem from the fact that it is an expensive and complex product."
"Lacks stability and as a result requires continuous monitoring."
"An improvement for SRM would be better interface compatibility with other products."
"VMware SRM needs to improve its pricing."
"Sometimes it can cause a bit of downtime during switchovers."
"I don't feel like we're a big enough customer to warrant being called every week or every month but it would be good to get a little bit more contact with a salesperson or engineer group."
"We have had some issues with trying to get certain parts of the backup or restore functionality to work."
"When it comes to a solution, one of the things the management wants is to standardize platforms. That's why when Rubrik came out with their solution, they wanted to look at it. For instance, if you have multiple technologies, you're going to need admins to manage all those different ones. I would like Zerto to be something that fits all our needs, including the backup that Rubrik provides, but I understand that not all solutions can be that way."
"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."
"Some of the integrations with our internal tools, in particular, company-specific ones, do not work. In cases like this, we have to ask for additional support."
"I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved."
"It needs to support more public cloud."
"Improvements in stability would be welcome; there are some software bugs that can affect RPOs. We want more of a guarantee that we won't lose any of our backups, even in the event of a disaster."
VMware SRM is ranked 6th in Disaster Recovery (DR) Software with 72 reviews while Zerto is ranked 2nd in Disaster Recovery (DR) Software with 235 reviews. VMware SRM is rated 8.0, while Zerto is rated 9.0. The top reviewer of VMware SRM writes "A scalable solution that integrates well with the VMware platform, but its platform agnostics do not support on-cloud usage". On the other hand, the top reviewer of Zerto writes "Gives us business continuity capabilities during hurricane season and in case of ransomware". VMware SRM is most compared with Veeam Backup & Replication, Dell RecoverPoint for Virtual Machines, Azure Site Recovery, VMware Cloud Disaster Recovery and Nutanix Disaster Recovery as a Service , whereas Zerto is most compared with Veeam Backup & Replication, Rubrik, Commvault Cloud, Dell RecoverPoint for Virtual Machines and VMware Cloud Disaster Recovery. See our VMware SRM vs. Zerto report.
See our list of best Disaster Recovery (DR) Software 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.