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

AWS Backup vs AWS Elastic Disaster Recovery comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 3, 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 Backup
Ranking in Cloud Backup
11th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
28
Ranking in other categories
SaaS Backup (4th)
AWS Elastic Disaster Recovery
Ranking in Cloud Backup
12th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
22
Ranking in other categories
Backup and Recovery (20th), Disaster Recovery (DR) Software (11th)
 

Mindshare comparison

As of March 2026, in the Cloud Backup category, the mindshare of AWS Backup is 2.7%, down from 3.5% compared to the previous year. The mindshare of AWS Elastic Disaster Recovery is 1.3%, up from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Backup Mindshare Distribution
ProductMindshare (%)
AWS Backup2.7%
AWS Elastic Disaster Recovery1.3%
Other96.0%
Cloud Backup
 

Featured Reviews

RiteshPurbey - PeerSpot reviewer
Senior Analyst at ESRI INDIA
Manages virtual machine backups smoothly and simplifies restoration across environments
It is quite easy to manage AWS Backup's centralized console for multiple environments. The product's interface is intuitive. AWS Backup has a much higher price if you compare it with the snapshots. I have to pay for the whole environment by AWS. We have a backup solution with only virtual machines. The rest of it, we have a restore point.
KS
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.

Quotes from Members

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

Pros

"The most valuable feature is its ease of use."
"When I was using an on-premises backup, there was an external hard drive or something like that, and I had a backup server, but I had a few problems related to transfer when I had to restore something that I have deleted, as I had to wait for after-office hours to do something like that, but now I just have to send a mail and within one hour I have my restored file."
"We primarily use the solution as a backup for snapshots so that the data will not get corrupt or lost, and it secures our data for us."
"The solution's most valuable features are its backup capability and tight integration with other AWS services."
"The most valuable feature is the daily incremental site backup."
"The most valuable features of AWS Backup are point-in-time recovery and support resources."
"It provides an easy data migration process from on-premise to cloud."
"RDS backup is one of the most crucial components of any client's cloud environment, so we generally use that. Additionally, we store EBS snapshots in S3."
"The initial setup is pretty straightforward, it's not complex."
"Overall, the best combination of AWS Elastic Disaster Recovery is its near real-time replication and quick recovery testing, and this makes the service very useful in real-world scenarios."
"We went from an organization with minimal to no disaster recovery, and I was able to spin up the disaster recovery environment with AWS rather quickly and meet business requirements."
"The strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based."
"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."
"AWS Elastic Disaster Recovery is a robust and reliable solution for disaster recovery needs."
"AWS Elastic Disaster Recovery is a reliable and cost-effective solution for business continuity."
"Scalability is pretty good; it's seamless and can do it automatically."
 

Cons

"There could be a centralized dashboard with a reporting feature notifying us of daily backup status."
"Only the price could be improved."
"AWS Backup could benefit from including more services."
"It requires a lot of time to connect the snapshot, identify the files, and restore a single file manually."
"For additional functionalities, it should be more intelligent, like more AI-capabilities."
"One of the limitations of AWS Backup is that it only does file-based copying."
"The support people face some challenges in coming on for remote sessions. They always prefer giving some logs."
"The notifications on the backup and on the mobile app could be more useful."
"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."
"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."
"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."
"It could be a bit more automated."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"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 UI could be a little sleeker."
"While the service is very effective, it could improve in areas such as more granular cost visibility during staging and test launches."
 

Pricing and Cost Advice

"Our customers pay a monthly AWS fee that includes the AWS Backup service."
"The solution's price is reasonable."
"AWS is more expensive than some competitors like Azure."
"The clients pay for the whole AWS bundle. It is an affordable solution."
"The pricing is decent."
"We don't use a lot of space, only approximately 900 GB, so the price is reasonable. For standing, it's okay. We normally do a payment to SSML, and they are the ones who pay over there. It is around $100 monthly."
"It's a myth that Cloud is cheap. Cloud is cheap initially, but the cost over time can be equal to your own infrastructure if you consume a lot."
"There is a lot of flexibility with the services and pricing. The price is reasonable when compared to other products. This is very good for us."
"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.​"
"I feel the product's pricing is a good value. Licensing is pretty straightforward."
"I rate the price of CloudEndure Disaster Recovery a six out of ten."
"We were happy with the pricing that they gave us."
"CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution."
"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."
report
Use our free recommendation engine to learn which Cloud Backup solutions are best for your needs.
884,933 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Financial Services Firm
10%
Manufacturing Company
8%
University
6%
Financial Services Firm
10%
Computer Software Company
8%
Government
8%
Healthcare Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise6
Large Enterprise15
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise5
Large Enterprise11
 

Questions from the Community

What do you like most about AWS Backup?
The solution's most valuable features are its backup capability and tight integration with other AWS services.
What is your experience regarding pricing and costs for AWS Backup?
AWS Backup operates on a pay-as-you-go model without requiring a license.
What needs improvement with AWS Backup?
I would need to get feedback from my colleague to see what additional features I would like to see in AWS Backup in the next release to make it closer to ten.
What is your experience regarding pricing and costs for CloudEndure Disaster Recovery?
The pricing has been fine, and regarding the setup cost as well, it is quite fine. There is definitely a scope of improvement, and for year-end licensing, they should definitely improve the cost.
What needs improvement with CloudEndure Disaster Recovery?
After implementing AWS Elastic Disaster Recovery, we significantly improved our disaster recovery metrics. Our RPO improved from approximately three to four hours to less than one minute. While the...
What is your primary use case for CloudEndure Disaster Recovery?
Our main use case for AWS Elastic Disaster Recovery was to ensure that if our primary on-premises data center failed, we could quickly launch EC2 instances in AWS to resume production. The main use...
 

Also Known As

No data available
CloudEndure Disaster Recovery
 

Overview

 

Sample Customers

TransferWise
Agio, Cloud Nation, Limelight Networks
Find out what your peers are saying about AWS Backup vs. AWS Elastic Disaster Recovery and other solutions. Updated: March 2026.
884,933 professionals have used our research since 2012.