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

AWS Elastic Disaster Recovery vs Catalogic DPX 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
20th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
22
Ranking in other categories
Cloud Backup (12th), Disaster Recovery (DR) Software (11th)
Catalogic DPX
Ranking in Backup and Recovery
73rd
Average Rating
6.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the Backup and Recovery category, the mindshare of AWS Elastic Disaster Recovery is 0.8%, up from 0.4% compared to the previous year. The mindshare of Catalogic DPX is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Backup and Recovery Mindshare Distribution
ProductMindshare (%)
AWS Elastic Disaster Recovery0.8%
Catalogic DPX0.5%
Other98.7%
Backup and Recovery
 

Featured Reviews

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.
it_user292722 - PeerSpot reviewer
Data Center Global SAP Operations Manager at a wholesaler/distributor with 1,001-5,000 employees
We use it to backup some high output critical physical servers, knowing that in case of disaster we could still recover to our VM environment. The user interface needs improvement.
The user interface needs improvement, the selection boxes to select a backup job are very small not adequate for managing 400+ backup jobs, we only see 8 job names in the small scroll window. The scheduler features are lacking, we must edit backup specs to reach the option to change the schedule. The new reporting feature has greatly improved the product, prior to this it was very difficult to have a full view of our backup schedules when scheduling a new job. Since the move from Syncsort to Catalogic, the quality control of upgrades has diminished and backups that used to work could not be restored without contacting Catalogic for a fix. We still see a lot of value in the product, but hope that the next few updates will not cause more issues... We wanted a mission critical enterprise solution, and sincerely hope that the future upgrades will bring the product back on track.

Quotes from Members

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

Pros

"Since deploying AWS Elastic Disaster Recovery, we have mostly seen an improvement in uptime, which contributes to reducing downtime."
"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."
"Scalability is pretty good; it's seamless and can do it automatically."
"CloudEndure is easy, and block-level replication will happen."
"The setup is pretty straightforward."
"It's on the cheaper side and not too expensive for users."
"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."
"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."
"Catalogic has great features including the ability to P2V from snapvaults, and recently the addition of agent-less backups for Linux."
"By implementing an OVF (docker based) and without any agents on your servers, you’ll get a system which provides you with: Orchestration, Automation DR and Data analytics."
 

Cons

"Definitely there should be better logging. From a customer perspective I would like to see more logs on what is happening."
"I would like to see better support for creating and working with archives. Right now, it is difficult and painful to do."
"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."
"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."
"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 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."
"It could be a bit more automated."
"And hearing about all these awesome posibilities, it kind of struck me that this was only possible with NetApp storage."
"Since the move from Syncsort to Catalogic, the quality control of upgrades has diminished and backups that used to work could not be restored without contacting Catalogic for a fix."
 

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."
"I feel the product's pricing is a good value. Licensing is pretty straightforward."
"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."
"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."
"They license us on a per machine basis. We have a set number of machines, which we have licensed.​"
Information not available
report
Use our free recommendation engine to learn which Backup and Recovery solutions are best for your needs.
885,376 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
10%
Computer Software Company
8%
Government
8%
Healthcare Company
8%
Construction Company
17%
Computer Software Company
16%
Comms Service Provider
11%
Educational Organization
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise5
Large Enterprise11
No data available
 

Questions from the Community

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

Also Known As

CloudEndure Disaster Recovery
BEX
 

Overview

 

Sample Customers

Agio, Cloud Nation, Limelight Networks
Hendrick Medical, CommonFund, Red-8, Fairfax County Schools, Tectrade, Storage Assessments
Find out what your peers are saying about Veeam Software, Hewlett Packard Enterprise, Rubrik and others in Backup and Recovery. Updated: March 2026.
885,376 professionals have used our research since 2012.