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

AWS Elastic Disaster Recovery vs InfoScale comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 21, 2026

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 (9th), Cloud Backup (9th)
InfoScale
Ranking in Disaster Recovery (DR) Software
14th
Average Rating
8.4
Reviews Sentiment
6.3
Number of Reviews
8
Ranking in other categories
Data Loss Prevention (DLP) (20th), IT Infrastructure Monitoring (28th), High Availability Clustering (1st), Data Storage for Kubernetes (2nd), Autonomous Operational Resilience (4th)
 

Mindshare comparison

As of July 2026, in the Disaster Recovery (DR) Software category, the mindshare of AWS Elastic Disaster Recovery is 2.5%, up from 1.5% compared to the previous year. The mindshare of InfoScale is 0.3%, up from 0.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Disaster Recovery (DR) Software Mindshare Distribution
ProductMindshare (%)
AWS Elastic Disaster Recovery2.5%
InfoScale0.3%
Other97.2%
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.
TJ
Site Reliability Engineer (Certified) at Kyndryl India
Automated recovery has minimized downtime and supports seamless multi‑datacenter failover
Beyond pricing, there are areas where I would like to see InfoScale improved or enhanced. Veritas offers three management approaches. The first, which Veritas currently recommends, is Veritas Operation Manager. The second is the Cluster Manager Java Console graphical interface. The Cluster Manager Java Console has not been revised since version 6.1 or 6.2. This tool was critical for me, particularly valuable when managing small cluster footprints of 20 to 30 server nodes. I relied heavily on this tool, but Veritas has moved away from it in favor of Operation Manager. I recommend Veritas continue evolving this tool rather than discarding it. The third approach is the command line, suitable for individuals with extensive Veritas expertise and experience, but command line use in live environments consumed excessive time, leading me to prefer the graphical interface. Apart from pricing, I have not discovered disadvantages. The product is excellent. My concern is Veritas discarding the Cluster Manager Java Console in favor of Veritas Operation Manager. Setting up Operation Manager requires time and a dedicated server that runs continuously. I had to create a single server just for Veritas Operation Manager. While this works well for larger environments with hundreds of clusters, it is less useful for smaller deployments. I still recommend Veritas reconsider this application and evolve it by incorporating new features from Veritas Operation Manager. Adding these new features to the Java console would be beneficial because that tool runs on my laptop without consuming environment resources, and I can connect directly to clusters from my laptop. I am not opposing Veritas Operation Manager, which is excellent and resembles hardware management consoles for power machines, but smaller tools that previously performed these tasks should remain as options to provide clients with greater ease. From a features and functionality perspective, I do not find missing features in InfoScale at this moment. However, I am not actively using Veritas, managing only legacy machines on older hardware. I am upgrading operating systems but not Veritas due to contract expiration and end-of-life status. The contract is not being renewed because the customer wants to move away. Since I have not logged into VCS since 2021 and transferred responsibilities to another team, I am unaware of features arriving in version 8 or beyond and cannot comment specifically on recent Veritas introductions.

Quotes from Members

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

Pros

"The solution's cost is reasonable."
"​The initial setup is really straightforward."
"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."
"Since it is a managed service, I reduce my time to manage infrastructure and applications."
"Since deploying AWS Elastic Disaster Recovery, we have mostly seen an improvement in uptime, which contributes to reducing downtime."
"CloudEndure is easy, and block-level replication will happen."
"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."
"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."
"From a recovery standpoint, InfoScale is excellent and easy to manage."
"The best feature is that it supports high availability and automatic failover, which minimizes downtime and helps the environment reduce downtime and improve high availability for critical applications."
"InfoScale's ability to maintain data integrity and availability during a cyber event such as a ransomware attack is excellent."
"It's a stable solution."
"In a live incident scenario, the data replication process occurs in real-time, and compared to other products, this data replication feature works effectively, ensuring data availability, and we can implement this scenario using Veritas Volume Replication (VVR), which is the most usable feature in InfoScale for data replication."
"It offers High Availability for many applications, including Oracle and SAP environment."
"Over the last two years, we did not experience any application failover or receive alerts due to the immediate switchover mechanism in active-active mode that ensures no downtime, helping us significantly with confidence and trust in our organization."
"InfoScale does that all by itself without any dependency on different solutions."
 

Cons

"An improved AWS pricing model is needed."
"The failback could be improved. It should be more intuitive."
"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."
"The cost of AWS Elastic Disaster Recovery is seen as expensive."
"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."
"Pricing could be improved."
"AWS Elastic Disaster Recovery is stable, but it can be improved."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"Many customers can see the benefit of InfoScale, but they are usually not able to purchase the product because the license cost is very high."
"It could be more stable and more secure."
"Many customers can see the benefits of InfoScale, but they are usually not able to buy the products and solutions because of the licensing costs."
"My experience with pricing, setup cost, and licensing indicates that pricing is a little higher and should be reduced since most companies cannot afford it."
"The primary concern is licensing cost, as the customer is unwilling to invest further and has begun cost-cutting measures."
"It's very difficult to implement."
"While InfoScale is mainly used by enterprise-level customers, it does not inherently support many applications, which presents a scalability issue."
"Based on my experience with support, I would rate them a nine, only because occasionally the first person I talk to does not know more than I do and it needs to be escalated to reach someone more knowledgeable."
 

Pricing and Cost Advice

"CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution."
"They license us on a per machine basis. We have a set number of machines, which we have licensed.​"
"I rate the price of CloudEndure Disaster Recovery a six 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."
"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."
"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."
"Our clients pay for licensing on a yearly basis."
report
Use our free recommendation engine to learn which Disaster Recovery (DR) Software solutions are best for your needs.
902,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Construction Company
8%
Healthcare Company
7%
Comms Service Provider
7%
Financial Services Firm
20%
Manufacturing Company
9%
Media Company
7%
Computer Software Company
7%
 

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 Enterprise3
Large Enterprise5
 

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 is your experience regarding pricing and costs for Veritas InfoScale Availability?
Does that include the licensing costs? It is really a real blocker in Turkey because of economic situations in Turkey. From a personal perspective, I would say nine. But from a business perspective...
What needs improvement with Veritas InfoScale Availability?
This is a question that is hard to answer because everyone is moving towards microservices and cloud native applications, and they are mostly running on Kubernetes or systems similar to Kubernetes....
What is your primary use case for Veritas InfoScale Availability?
To have high availability of data center resources, especially databases and applications, I needed data replicated from one data center to a disaster recovery data center or another data center, a...
 

Also Known As

CloudEndure Disaster Recovery
Veritas InfoScale Availability, Arctera InfoScale for Kubernetes
 

Overview

 

Sample Customers

Agio, Cloud Nation, Limelight Networks
Wayne State University, Zenith Mart
Find out what your peers are saying about AWS Elastic Disaster Recovery vs. InfoScale and other solutions. Updated: June 2026.
902,894 professionals have used our research since 2012.