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
19th
Ranking in Disaster Recovery (DR) Software
14th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
16
Ranking in other categories
Backup and Recovery (26th)
Druva Phoenix
Ranking in Cloud Backup
16th
Ranking in Disaster Recovery (DR) Software
11th
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Disaster Recovery as a Service (5th), SaaS Backup (7th)
 

Mindshare comparison

As of April 2025, in the Cloud Backup category, the mindshare of AWS Elastic Disaster Recovery is 1.3%, up from 0.4% compared to the previous year. The mindshare of Druva Phoenix is 0.7%, 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 initial setup is pretty straightforward, it's not complex."
"Customer service is quite helpful."
"It's on the cheaper side and not too expensive for users."
"The strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based."
"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."
"For regular backup and restore solutions, this product is fine."
"Since it is a managed service, I reduce my time to manage infrastructure and applications."
"The setup is pretty straightforward."
"The most valuable features of Druva Phoenix are the simple portal to log in and flexibility."
"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."
"It's patch-based, so you don't have to bother about the backup server or the repository."
"The initial setup was very straightforward."
"Druva Phoenix is easy to use and easy to start with."
"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."
 

Cons

"Sometimes a server will get a bit behind. ​"
"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."
"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."
"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."
"The failback could be improved. It should be more intuitive."
"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."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"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."
"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."
"The product's pricing needs to be improved."
"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."
 

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."
"They license us on a per machine basis. We have a set number of machines, which we have licensed.​"
"We were happy with the pricing that they gave us."
"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."
"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 rate the price of CloudEndure Disaster Recovery a six out of ten."
"I feel the product's pricing is a good value. Licensing is pretty straightforward."
"CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution."
"It's very costly. Normal people wouldn't understand how their credits are calculated. It's pretty complex."
"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."
"I assume clients use Druva Phoenix because it is cheaper than other products."
"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."
report
Use our free recommendation engine to learn which Cloud Backup solutions are best for your needs.
846,617 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
13%
Government
12%
Healthcare Company
10%
Computer Software Company
22%
Financial Services Firm
7%
Manufacturing Company
7%
Comms Service Provider
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?
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 pu...
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?
The product's pricing needs to be improved. Including more flexible feature sets such as options for sending secondary backups to different locations would be beneficial.
What is your primary use case for Druva Phoenix?
We utilized the product to modernize backup as a service, eliminating the need for extensive hardware and ensuring data is securely backed off-site.
 

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: April 2025.
846,617 professionals have used our research since 2012.