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

AWS Elastic Disaster Recovery vs Iron Mountain Connect comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 11, 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 Backup and Recovery
30th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
16
Ranking in other categories
Cloud Backup (19th), Disaster Recovery (DR) Software (16th)
Iron Mountain Connect
Ranking in Backup and Recovery
67th
Average Rating
8.6
Reviews Sentiment
8.3
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Backup and Recovery category, the mindshare of AWS Elastic Disaster Recovery is 0.5%, up from 0.2% compared to the previous year. The mindshare of Iron Mountain Connect is 0.3%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Backup and Recovery
 

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.
RB
Good policies related to data
I primarily use it for various policies related to data, such as data retention, data deletion, and archiving policies. All policies can be set using this system The most valuable feature for me is the policy management capabilities. I would like to see more integration with different platforms,…

Quotes from Members

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

Pros

"The strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based."
"Since it is a managed service, I reduce my time to manage infrastructure and applications."
"CloudEndure Disaster Recovery is a fairly stable solution."
"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."
"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."
"Technical support has been very good. They usually respond quickly to our requests.​"
"The initial setup is pretty straightforward, it's not complex."
"The most valuable feature for me is the policy management capabilities"
 

Cons

"Sometimes a server will get a bit behind. ​"
"I have not seen any areas that need improvement at this time."
"The failback could be improved. It should be more intuitive."
"The UI could be a little sleeker."
"I set up a test, deleted the source, and went to fail it back, and it didn't work."
"An improved AWS pricing model is needed."
"I would like to see better support for creating and working with archives."
"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 would like to see more integration with different platforms."
 

Pricing and Cost Advice

"It has saved us money from having to buy hardware for disaster recovery."
"We were happy with the pricing that they gave us."
"I rate the price of CloudEndure Disaster Recovery a six out of ten."
"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.​"
"CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution."
"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 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.
850,236 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%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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...
Ask a question
Earn 20 points
 

Also Known As

CloudEndure Disaster Recovery
No data available
 

Overview

 

Sample Customers

Agio, Cloud Nation, Limelight Networks
University of La Verne
Find out what your peers are saying about AWS Elastic Disaster Recovery vs. Iron Mountain Connect and other solutions. Updated: April 2025.
850,236 professionals have used our research since 2012.