We performed a comparison between Druva Phoenix and Zerto based on real PeerSpot user reviews.
Find out in this report how the two Cloud Backup solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Once you set it up and you tell it exactly what needs to be backed up, you literally forget about it. It sends you emails and notifications of the current status of the jobs."
"I would definitively say that we have been able to make our people more productive by at least 30%."
"I found the cost-effectiveness of Druva Phoenix to be its most valuable feature, especially when compared to on-premises backup solutions."
"The most valuable features of Druva Phoenix are the simple portal to log in and flexibility."
"Druva Phoenix is easy to use and easy to start with."
"With Zerto, we were able to replicate our virtual servers to a remote DR site across a WAN connection."
"The ease of use is one of the best features. Previously, we were using Site Replication Manager with VMware and it was a little bit cumbersome. With Zerto, we liked the fact that it was hardware-agnostic and we were able to spin it up pretty quickly and get it working."
"Zerto offered a very good front-end GUI for orchestration. The graphic interface was very good."
"We are moving to a new data center. There are several VMs that we have to move over there that have RDM disks or SQL clusters. Those are the hardest things to move at this point in time, but now that I have the setup and it is ready to go, all we have to do is just flip the switch and get everything over where they are supposed to be. It is going to be a lifesaver for me. It will save me a whole lot of time in putting things back together."
"With Zerto, all you have to do is deploy the executable and start setting things up. So, it was very easy."
"The testing features are the most valuable features of this solution. We use the failover test feature not just for testing failovers and disaster recovery, we've also had clients use it for development purposes as well as patching purposes to test patches. We can failover the VM and then we can make any changes we want without affecting production. It's a nice sandbox for that usage."
"The near-synchronous replication is one of the primary reasons we're using Zerto because we have recovery intervals of sub-five seconds. On a scale of 10, where 10 is "very important", this feature is a 10."
"The real-time replication of data is the most valuable feature. It is a vast improvement in scheduled daily backups. Real-time data is streamed to the offsite data center, which allows us to restore our mission-critical applications up to 10 seconds from when the last changes were made in our system. If we enter a sales order or enter any kind of information in our ERP application it is replicated within 10 seconds to the offsite location."
"There is room for improvement in the reporting aspect of Druva Phoenix."
"They were able to give us a very reasonable price considering we were non-for-profit organizations, however, there is always room for improvement on that cost."
"Druva Phoenix should include a few reporting features that it doesn't provide currently."
"Druva Phoenix is optimized to work with x86 platforms, making it unsuitable for backing up non-x86 architectures like AIX. The solution is primarily designed for physical Linux and Windows systems based on the x86 architecture, as well as virtualized Windows and Linux environments. However, if you have an AIX system, it cannot be deployed in the cloud, and therefore, backing it up in the cloud is not a concern."
"Zerto's connectivity with automation platforms could be improved. For example, vCenter can use a VMware-developed tool called Site Recovery Manager. That can be integrated with automation platforms such as Terraform, Ansible, Chef, or Puppet, to perform automated, self-sufficient recoveries to essentially avoid any downtime. To my knowledge, Zerto does not have integration with those platforms."
"Their data backup and restore have some ways to go."
"The alerting doesn't quite give you the information about what exactly is going on when an issue comes up. We do get alerts inside of our vCenter, but it doesn't quite give you accurate information inside the plugin to be able to tell us what's going on without having to go into the actual Zerto application and figuring out what's causing the issue."
"The biggest pain points we have experienced are related to some of the SQL-intensive workloads just because the VPGs struggle a little bit to keep up. That might be because we are pushing too many transactions."
"Zerto should add the capability to replicate the same VM to multiple sites."
"Increased granularity in how long to keep the journal would be nice."
"The RPO for our SQL server has room for improvement."
"If the log was more detailed and more user-friendly, we wouldn't have to make the calls to the support to try and figure out where the problem lies."
Druva Phoenix is ranked 20th in Cloud Backup with 5 reviews while Zerto is ranked 3rd in Cloud Backup with 233 reviews. Druva Phoenix is rated 8.8, while Zerto is rated 9.0. The top reviewer of Druva Phoenix writes "Cost-effective and has excellent technical support". On the other hand, the top reviewer of Zerto writes "Gives us business continuity capabilities during hurricane season and in case of ransomware". Druva Phoenix is most compared with Azure Backup, Druva inSync, Veeam Backup & Replication, AWS Backup and Rubrik, whereas Zerto is most compared with Veeam Backup & Replication, VMware SRM, Rubrik, Dell RecoverPoint for Virtual Machines and Commvault Cloud. See our Druva Phoenix vs. Zerto report.
See our list of best Cloud Backup vendors, best Disaster Recovery (DR) Software vendors, and best Disaster Recovery (DR) Software vendors.
We monitor all Cloud Backup 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.