Try our new research platform with insights from 80,000+ expert users

AWS Elastic Disaster Recovery vs Druva Phoenix comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 15, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Elastic Disaster Recovery
Ranking in Cloud Backup
18th
Ranking in Disaster Recovery (DR) Software
16th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
17
Ranking in other categories
Backup and Recovery (25th)
Druva Phoenix
Ranking in Cloud Backup
32nd
Ranking in Disaster Recovery (DR) Software
18th
Average Rating
8.6
Reviews Sentiment
6.1
Number of Reviews
8
Ranking in other categories
Disaster Recovery as a Service (7th), SaaS Backup (9th)
 

Mindshare comparison

As of August 2025, in the Cloud Backup category, the mindshare of AWS Elastic Disaster Recovery is 1.3%, up from 0.6% compared to the previous year. The mindshare of Druva Phoenix is 0.8%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Backup
 

Featured Reviews

Vijay Londhe - PeerSpot reviewer
Managed services with seamless integration and good reliability
Since I have to view everything on the console, the previous application solutions like IBM and Sanavi showed the RPO and RTO status directly. In AWS Disaster Recovery Service, these details are not available, making it difficult to check my replication status. I have to calculate whether my data is replicated to the Adarabad region or not. These features, if available in AWS, would be beneficial.
Ratnodeep Roy - PeerSpot reviewer
Patch-based system, offers network flexibility but Logs are not very informative for regular users
The ransomware features are limited in Druva. There's a lot of improvement needed. It should extend to Nutanix and Hyper-V. It should extend to Azure as well. A lot of people are looking for ransomware scans, but Druva doesn't support them. Veeam barely supports them over Azure Virtual Machines. It doesn't support Linux Virtual Machines. NetApp and Commvault don't have such features. Acronis is also limited. In Azure, you have Azure Defender, but that works extensively on cloud storage, not on the servers. So, backup companies like Druva need to work a lot on ransomware protection and detection. These companies need to work a lot on ransomware detection, protection and more. Ransomware protection doesn't work in this hash-based transfer mirroring. If I only have to find this hash and feed it to the Druva end. It's sometimes not possible. It will struggle when the workloads are more than a hundred machines. It's not possible to find the hash of each file and provide it to Druva. So, this needs to be fully automated. If I were scanning with some technology, maybe signature-based scanning, behavioral-based, or keyword-based scanning. I can put this FHA, maybe SIEMs as well. But Druva is very limited. It's already in an active stage. I don't like that they don't extend all the features to all the workloads. These features are minimal compared to those of its competitors. For instance, I have one customer who was looking for Druva, but since they have Azure machines, they couldn't find a way to restore a particular file. Druva doesn't provide Azure virtual machine single file restore. It doesn't make sense to build a product and then it doesn't support it. Customers really struggle. Some customers tried Druva so that they don't have to think about setting up a separate network, but Druva is making things critical by not providing all the things at once and gradually releasing them. It's been more than six months or one year since they started their virtual machines, but there is no single file restore. Every time you have to restore the VM, and then from there, you can get the file. Why would people go with Druva if they have to manage backup machines? Nowadays, backup product companies need to be aggressive and adopt themselves in this highly changing world of AI and ML.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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 setup is pretty straightforward."
"I appreciate the automated orchestration of recovery processes in this solution, especially integration with Route 53 and automatically using Route 53 to switch to a different region directly."
"It offers seamless integration with services like ACL, EKS, and Fargate for deploying containerized applications."
"It's on the cheaper side and not too expensive for users."
"The initial setup is pretty straightforward, it's not complex."
"We have never had any issues with scalability."
"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."
"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."
"The initial setup was very straightforward."
"It's patch-based, so you don't have to bother about the backup server or the repository."
"I would definitively say that we have been able to make our people more productive by at least 30%."
"Druva Phoenix is easy to use and easy to start with."
"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."
 

Cons

"I set up a test, deleted the source, and went to fail it back, and it didn't work."
"I have not seen any areas that need improvement at this time."
"The product could be improved by incorporating more AI-driven automation for deployment and additional security features. These enhancements would make the solution even more user-friendly and secure."
"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 cost of AWS Elastic Disaster Recovery is seen as expensive."
"In its current state, ECL integrates with CloudWatch for basic logging and monitoring, yet improvements could include more detailed logs for specific actions, like when I perform actions such as push or pull."
"Since I have to view everything on the console, the previous application solutions like IBM and Sanavi showed the RPO and RTO status directly. In AWS Disaster Recovery Service, these details are not available, making it difficult to check my replication status."
"I would like to see better support for creating and working with archives."
"The ransomware features are limited in Druva. There's a lot of improvement needed. It should extend to Nutanix and Hyper-V. It should extend to Azure as well."
"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."
"The product's pricing needs to be improved."
"There is room for improvement in the reporting aspect of Druva Phoenix."
 

Pricing and Cost Advice

"Where the price adds up, there are CloudEndure licenses, then there is the AWS environment, and finally, there is the AWS storage, so cumulatively, it adds up."
"We were happy with the pricing that they gave us."
"They license us on a per machine basis. We have a set number of machines, which we have licensed.​"
"The pricing is better now that they had come out with the Tier 2 which replicates a little less often. In comparison to what I would have been spending with any other type of solution, the pricing is fair."
"I rate the price of CloudEndure Disaster Recovery a six out of ten."
"CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution."
"On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing an eight out of ten."
"I feel the product's pricing is a good value. Licensing is pretty straightforward."
"It's very costly. Normal people wouldn't understand how their credits are calculated. It's pretty complex."
"We’ve had experience with the data center for a while and we have had solutions that were able to support older versions of the operating systems that we needed. I would like for Druva to support it as well."
"I assume clients use Druva Phoenix because it is cheaper than other products."
"Druva Phoenix's pricing is based on the service provided, and it's reasonable. The cost of the service will depend on the size of your data and the number of virtual machines being backed up. However, the pricing structure is straightforward and easy to understand."
report
Use our free recommendation engine to learn which Cloud Backup solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
10%
Healthcare Company
9%
Government
9%
Computer Software Company
18%
Manufacturing Company
9%
Comms Service Provider
6%
Financial Services Firm
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about CloudEndure Disaster Recovery?
CloudEndure Disaster Recovery is a fairly stable solution.
What is your experience regarding pricing and costs for CloudEndure Disaster Recovery?
The setup is actually managed by our partner. I have taken a rate of per user. Licensing is completely managed by the partner. I am paying per user and per GB storage cost, while the infrastructure...
What needs improvement with CloudEndure Disaster Recovery?
I don't think there is any bad feature in AWS Elastic Disaster Recovery as such. It's more of when you do disaster recovery, you think of it more holistically. You want flexibility in terms of opti...
What do you like most about Druva Phoenix?
Druva Phoenix is easy to use and easy to start with.
What needs improvement with Druva Phoenix?
Druva Phoenix could be improved if they provided bare metal recovery for physical servers, which would be beneficial for server deployment.
What is your primary use case for Druva Phoenix?
The typical use case for Druva Phoenix depends on multiple workloads. If a customer wants a simple solution where we can manage the entire workload, or they want to back up with agent plus backup, ...
 

Also Known As

CloudEndure Disaster Recovery
CloudRanger
 

Overview

 

Sample Customers

Agio, Cloud Nation, Limelight Networks
TRC Companies, Family Health Network, GulfMark Offshore, Pall Corporation
Find out what your peers are saying about AWS Elastic Disaster Recovery vs. Druva Phoenix and other solutions. Updated: August 2025.
865,384 professionals have used our research since 2012.