No more typing reviews! Try our Samantha, our new voice AI agent.

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
9th
Ranking in Disaster Recovery (DR) Software
9th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
25
Ranking in other categories
Backup and Recovery (9th)
Druva Phoenix
Ranking in Cloud Backup
23rd
Ranking in Disaster Recovery (DR) Software
16th
Average Rating
8.6
Reviews Sentiment
6.3
Number of Reviews
10
Ranking in other categories
Disaster Recovery as a Service (8th), SaaS Backup (13th)
 

Mindshare comparison

As of August 2026, in the Cloud Backup category, the mindshare of AWS Elastic Disaster Recovery is 1.3%, down from 1.3% compared to the previous year. The mindshare of Druva Phoenix is 1.2%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Backup Mindshare Distribution
ProductMindshare (%)
AWS Elastic Disaster Recovery1.3%
Druva Phoenix1.2%
Other97.5%
Cloud Backup
 

Featured Reviews

Kavya S - PeerSpot reviewer
Data Engineer at a outsourcing company with 201-500 employees
Continuous replication has protected critical servers and supports seamless disaster recovery drills
Some features that I personally feel can be improved are more simplified monitoring and reporting. As I previously mentioned, the console shows the replication status. If it had more detailed dashboards or built-in reports for DR readiness, it would make it easier for the teams to track everything in one place. Another improvement would be cost visibility and optimization guidance in optimizing the cost and also giving us visibility of it. Because the staging resources and replication storage are running continuously, it would be very helpful for organizations and users if AWS provided clearer cost insights, recommendations, and remediations to optimize the DR environment. It would also be useful if AWS added more automation options for application-level recovery, such as easier ways to handle IP changes, domain name system (DNS) updates, or application dependencies during failover. Additionally, we can simplify the setup and configuration process. For someone new to the service, understanding the staging settings, launch templates, and networking configurations can take some time. Setup simplicity and more detailed monitoring and alerting features would be beneficial. If we could add that, we can easily track the replication health, lag, and potential issues. Instead of relying on other additional tools for monitoring and alerting features, we can rely on AWS Elastic Disaster Recovery itself.
ZubeenAhmad - PeerSpot reviewer
Sales Support Associate at Murdoch Webster
Cloud backup has reduced storage costs and now delivers fast, reliable data recovery
My overall experience in this field is seven years. The deployment model I have chosen for Druva Phoenix is mostly cloud-based backup. Government authorities and government customers majorly opt for on-premises deployment, but we have a very limited customer segment from that area. Druva Phoenix primarily operates on a private cloud, with some customers utilizing hybrid cloud solutions. If I assess the effectiveness of backup features in Druva Phoenix, particularly in minimizing operational disruptions, I would rate it as a very strong 9 or 9.5 on a scale of 10. I am not using Druva Data Security Cloud. My overall review rating for Druva Phoenix is 9.

Quotes from Members

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

Pros

"We have never had any issues with scalability."
"What I like about ECR AWS is that it is a fully managed service, so I don't need to manage the underlying infrastructure or worry about scalability in AWS concerning building, maintenance, security, and high availability."
"AWS Elastic Disaster Recovery is a robust and reliable solution for disaster recovery needs."
"Since it is a managed service, I reduce my time to manage infrastructure and applications."
"Some of the most valuable features of this product include its ability to manage disaster recovery effectively."
"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 strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based."
"CloudEndure is easy, and block-level replication will happen."
"Druva Phoenix provides a return on investment and operational cost reductions after implementation."
"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."
"One of the best features in Druva Phoenix for me personally is that it is an air-gapped environment, where you can keep cloud backup on a separate air-gapped environment and save from any kind of ransomware attack, and it is a ransomware safer environment because a customer gets a separate environment."
"The initial setup was very straightforward."
"The solution is great for companies that need backup capabilities."
"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%."
"The most valuable features of Druva Phoenix are the simple portal to log in and flexibility."
 

Cons

"When I started working with AWS Elastic Disaster Recovery, one of the major issues I faced during my learning phase was understanding the initial setup and replication process."
"Pricing could be improved."
"An improved AWS pricing model is needed."
"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."
"I have not seen any areas that need improvement at this time."
"However, the user interface and monitoring features could be improved to make the overall experience better."
"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."
"It could be a bit more automated."
"The price is always one of those things that you always look to just improve if you're a not-for-profit organization."
"They were very much responsive a few years back, but in the last one or two years, I believe the responsiveness has gone down."
"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 could be improved if they provided bare metal recovery for physical servers, which would be beneficial for server deployment."
"Although, sometimes there is a restriction with the number of OS platforms that this solution supports."
"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."
"I rate the price of CloudEndure Disaster Recovery a six out of ten."
"We were happy with the pricing that they gave us."
"It has saved us money from having to buy hardware for disaster recovery."
"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."
"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."
"They license us on a per machine basis. We have a set number of machines, which we have licensed.​"
"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."
"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."
report
Use our free recommendation engine to learn which Cloud Backup solutions are best for your needs.
908,877 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Construction Company
10%
Outsourcing Company
7%
Comms Service Provider
6%
Financial Services Firm
11%
Construction Company
9%
Manufacturing Company
9%
Computer Software Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise12
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise3
Large Enterprise2
 

Questions from the Community

What is your experience regarding pricing and costs for CloudEndure Disaster Recovery?
The cost rating was assessed on a scale where 10 represented the most expensive.
What needs improvement with CloudEndure Disaster Recovery?
There are areas that could be improved beyond the downtime issues mentioned, and AWS Elastic Disaster Recovery could enhance several aspects of its functionality.
What needs improvement with Druva Phoenix?
While Druva Phoenix is a good solution for a cloud-to-cloud environment, such as moving from AWS to another AWS, I see complexity when a customer wants to move from a physical environment or a phys...
What is your primary use case for Druva Phoenix?
Druva Phoenix is for server backups on cloud, which is the deployment model chosen by my customers. While Druva Phoenix is a good solution for a cloud-to-cloud environment, such as moving from AWS ...
What advice do you have for others considering Druva Phoenix?
Many customers use Druva Phoenix's continuous data protection feature, but not for Phoenix. Not for Phoenix because Phoenix is server backups, and you generally do not keep continuous backup for se...
 

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 2026.
908,877 professionals have used our research since 2012.