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

AWS Elastic Disaster Recovery vs Dell RecoverPoint for Virtual Machines 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 Disaster Recovery (DR) Software
9th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
25
Ranking in other categories
Backup and Recovery (11th), Cloud Backup (11th)
Dell RecoverPoint for Virtu...
Ranking in Disaster Recovery (DR) Software
7th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Disaster Recovery (DR) Software category, the mindshare of AWS Elastic Disaster Recovery is 2.5%, up from 1.4% compared to the previous year. The mindshare of Dell RecoverPoint for Virtual Machines is 5.0%, up from 3.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Disaster Recovery (DR) Software Mindshare Distribution
ProductMindshare (%)
Dell RecoverPoint for Virtual Machines5.0%
AWS Elastic Disaster Recovery2.5%
Other92.5%
Disaster Recovery (DR) Software
 

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.
ClaudioSalgado - PeerSpot reviewer
IT Architect Consultant at RTFM
Offers replication flexibility across multiple environments, including local centers and secondary sites
It offers key features like any point-in-time recovery without needing scheduled snapshots. It allows for automated VM protection during processes like failover and testing, and it offers replication flexibility across multiple environments, including local centers and secondary sites. It also provides IP address management when network configurations differ across sites.

Quotes from Members

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

Pros

"It's on the cheaper side and not too expensive for users."
"Since it is a managed service, I reduce my time to manage infrastructure and applications."
"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."
"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."
"There has definitely been a lot of improvements in recovery time with very less downtime because we already understand how to recover using the clear process that AWS Elastic Disaster Recovery provides."
"Customer service is quite helpful."
"The most valuable aspect of CloudEndure Disaster Recovery is its instant block replication feature. This allows us to perform live block verification and eliminates the need to concern ourselves with recovery point objectives. This capability is particularly advantageous for critical workloads."
"AWS Elastic Disaster Recovery has positively impacted my organization by securing and stabilizing our platform."
"The most valuable feature is the ability to change IP addresses when failing a server over."
"The product's initial setup phase was quite easy to install."
"Continuous replication with lower RTO and RPO is the most innovative feature, and its tight integration with VMware for VMware VMs is also valuable."
"The most valuable feature is that it is journal-based and you don't have to replicate a lot of data."
"I use RecoverPoint for VM for my production-critical system because it gives you general electives for the journals and the point-in-time recovery."
"It is a very simple tool to use and offers flexibility in using the tool for recovery and transitioning from one state to another."
"Dell RecoverPoint for Virtual Machines offers key features like any point-in-time recovery without needing scheduled snapshots."
"Point-in-time recovery and ease of deployment are valuable."
 

Cons

"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."
"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 cost of AWS Elastic Disaster Recovery is seen as expensive."
"AWS Elastic Disaster Recovery is stable, but it can be improved."
"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."
"An improved AWS pricing model is needed."
"The failback could be improved. It should be more intuitive."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"The solution currently supports only VMware. There is increasing demand for compatibility with other hypervisors, such as Hyper V and KVM Proxmox. Additionally, licensing has become less flexible and more expensive."
"Their L1 support is not so good as of now. They have recently outsourced to a company, and they are not doing good."
"The configuration process seems a bit challenging, and the installation takes a bit longer than expected."
"The solution could improve by being more easier to use. However, once you have used it for a while it becomes easier. Additionally, there could be better support and compatibility with management by having a command-line interface. This would be beneficial for the customers."
"Maybe integration with Kubernetes for OpenShift would be helpful."
"Although we can change the IP address, it would be good to have some other sort of orchestration to make life easier to manage when we failover."
"The solution currently supports only VMware."
"There is a problem with the solution's architecture. First of all, it requires double the resources on the virtual environment to set up one environment."
 

Pricing and Cost Advice

"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."
"It has saved us money from having to buy hardware for disaster recovery."
"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."
"We were happy with the pricing that they gave us."
"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."
"This is an expensive product."
"There is a license required for this solution and the pricing depends on how many virtual machines you have."
"The tool is expensive. If one means cheaply priced and ten means expensive, I rate the tool's price as a seven."
"This is not a very cheap solution and compared to others, it is expensive."
"Pricing-wise, it is pretty much fair for any customer who only has a VMware environment. Licensing is based on the number of VMs that you want to protect at any given point in time. Licensing is not based on size."
"It was a part of a backup solution. So, it was free for us."
report
Use our free recommendation engine to learn which Disaster Recovery (DR) Software solutions are best for your needs.
902,270 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Construction Company
8%
Computer Software Company
7%
Comms Service Provider
7%
Computer Software Company
12%
Financial Services Firm
12%
Manufacturing Company
7%
Construction Company
6%
 

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 Business5
Midsize Enterprise4
Large Enterprise6
 

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 Dell EMC RecoverPoint for Virtual Machines?
Although we can change the IP address, it would be good to have some other sort of orchestration to make life easier to manage when we failover.
What is your primary use case for Dell EMC RecoverPoint for Virtual Machines?
I was actually just having a quick look to compare some solutions, but we are going to stick with what we currently have, which is Dell RecoverPoint for Virtual Machines ( /products/dell-recoverpoi...
 

Also Known As

CloudEndure Disaster Recovery
No data available
 

Overview

 

Sample Customers

Agio, Cloud Nation, Limelight Networks
Rushmore Electric Power Cooperative, PCS Publishing, Noble Foods
Find out what your peers are saying about AWS Elastic Disaster Recovery vs. Dell RecoverPoint for Virtual Machines and other solutions. Updated: June 2026.
902,270 professionals have used our research since 2012.