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

AWS Elastic Disaster Recovery vs Nimesa Backup and Recovery for AWS comparison

 

Comparison Buyer's Guide

Executive Summary

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 Backup and Recovery
11th
Ranking in Disaster Recovery (DR) Software
9th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
25
Ranking in other categories
Cloud Backup (11th)
Nimesa Backup and Recovery ...
Ranking in Backup and Recovery
45th
Ranking in Disaster Recovery (DR) Software
24th
Average Rating
8.4
Reviews Sentiment
5.8
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Backup and Recovery category, the mindshare of AWS Elastic Disaster Recovery is 0.9%, up from 0.5% compared to the previous year. The mindshare of Nimesa Backup and Recovery for AWS is 0.2%. It is calculated based on PeerSpot user engagement data.
Backup and Recovery Mindshare Distribution
ProductMindshare (%)
AWS Elastic Disaster Recovery0.9%
Nimesa Backup and Recovery for AWS0.2%
Other98.9%
Backup and Recovery
 

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.
Sumanth Chowdary - PeerSpot reviewer
Senior Technical Consultant
Centralized automation has improved cloud backups and strengthens disaster recovery readiness
One area where Nimesa Backup and Recovery for AWS could improve is expanding advanced analytics and predictive monitoring capabilities, especially for identifying backup risks, storage optimization opportunities, and recovery readiness trends more proactively. The platform could also benefit from deeper automation around recovery orchestration and policy-based remediation workflows for large-scale enterprise environments. Another improvement area is more granular customization in reporting and dashboard views to support different operational and compliance requirements. I also think broader integrations with security monitoring, ITSM, and DevSecOps ecosystems would further enhance operational visibility and workflow efficiency. Overall, the core backup and recovery capabilities are strong, but continued enhancements around automation, analytics, and ecosystem integration would make the platform even more effective. In my day-to-day operation, I have found that in larger or more complex AWS environments, deeper filtering and more granular reporting customization would be helpful for operational teams managing multiple workloads and accounts. More advanced automation for recovery orchestration and proactive alerting around backup anomalies would also improve efficiency further. Expanding predictive insights around storage growth, backup optimization, and recovery readiness would add a lot of value for long-term cloud resilience planning. Overall, the platform works effectively operationally, but these enhancements would make large-scale management even smoother and more proactive.

Quotes from Members

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

Pros

"CloudEndure Disaster Recovery is a fairly stable solution."
"The initial setup is pretty straightforward, it's not complex."
"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."
"It's on the cheaper side and not too expensive for users."
"We have never had any issues with scalability."
"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."
"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."
"AWS Elastic Disaster Recovery is a reliable and cost-effective solution for business continuity."
"Nimesa Backup and Recovery for AWS helped us automate backup scheduling and policy management, gave us centralized visibility with a dashboard across AWS workloads of multiple accounts, helped us with a faster recovery process, and majorly reduced our operational overhead while improving our ransomware and data protection."
"Overall, these features make day-to-day backup operations more structured, reduce operational overhead, and improve confidence around recovery preparedness and cloud resilience."
"Previously, if we had any disaster or any issue, it would take days to bring the environment back up to the original state, and with Nimesa Backup and Recovery for AWS, we can do that within a couple of hours, which greatly reduces downtime in the case of disaster recovery."
 

Cons

"The cost of AWS Elastic Disaster Recovery is seen as expensive."
"Sometimes, one of the servers will get behind for one reason or another, and it does not notify us when that happens."
"The failback could be improved. It should be more intuitive."
"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 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."
"There is definitely a scope of improvement, and for year-end licensing, they should definitely improve the cost."
"AWS Elastic Disaster Recovery is stable, but it can be improved."
"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."
"Nimesa Backup and Recovery for AWS has a fairly small market presence."
"Regarding customer support, as this is a very new product and relatively new in the market, I am not sure how long they have been around, but there seems to be a lack of understanding with the support team."
"One area where Nimesa Backup and Recovery for AWS could improve is expanding advanced analytics and predictive monitoring capabilities, especially for identifying backup risks, storage optimization opportunities, and recovery readiness trends more proactively."
 

Pricing and Cost Advice

"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."
"It has saved us money from having to buy hardware for disaster recovery."
"CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution."
"I rate the price of CloudEndure Disaster Recovery a six out of ten."
"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."
"We were happy with the pricing that they gave us."
"I feel the product's pricing is a good value. Licensing is pretty straightforward."
Information not available
report
Use our free recommendation engine to learn which Backup and Recovery solutions are best for your needs.
900,277 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Construction Company
7%
Comms Service Provider
7%
Computer Software Company
7%
Construction Company
50%
Comms Service Provider
16%
Healthcare Company
7%
Outsourcing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise12
No data available
 

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 Nimesa Backup and Recovery for AWS?
One area where Nimesa Backup and Recovery for AWS could improve is expanding advanced analytics and predictive monitoring capabilities, especially for identifying backup risks, storage optimization...
What is your primary use case for Nimesa Backup and Recovery for AWS?
The main use case has been improving backup automation, disaster recovery readiness, and centralized protection for AWS-hosted workloads. I mainly use Nimesa Backup and Recovery for AWS to protect ...
What advice do you have for others considering Nimesa Backup and Recovery for AWS?
One piece of advice that I would give is to clearly define specific backup, recovery, and disaster recovery objectives before implementation so that backup policies and retention strategies align p...
 

Also Known As

CloudEndure Disaster Recovery
No data available
 

Overview

 

Sample Customers

Agio, Cloud Nation, Limelight Networks
Information Not Available
Find out what your peers are saying about Veeam Software, Hewlett Packard Enterprise, Rubrik and others in Backup and Recovery. Updated: June 2026.
900,277 professionals have used our research since 2012.