AWS Elastic Disaster Recovery is a fully managed service that enables fast, reliable recovery of on-premises or cloud-based applications to AWS. We use it for minimizing downtime and data loss. There have been multiple situations where our production servers hosted on AWS went down, and we were able to shift to different servers, thereby minimizing the downtime with no data loss.
My main use case for AWS Elastic Disaster Recovery is for any databases or applications when they go down on a cross-region. For instance, when an application is spinning up into multiple regions, we lost one, and AWS Elastic Disaster Recovery helped us recover. In that situation, when there was an event that happened in the cloud stack, AWS Elastic Disaster Recovery helped us get things back up and running. Although this happened only once, we would like to have this multi-region, multi-data center level recovery for disaster recovery, so we are incorporating this technology.
AWS Elastic Disaster Recovery provides my team with a low-cost way to protect critical applications and ensure minimal service interruptions and data loss when a disaster occurs. The rapid recovery accelerates and automates the recovery process, allowing for quick failover to a staging area in AWS and minimal downtime. It replicates servers and data from on-premises data centers and other clouds to AWS, converting them to run natively on AWS after a disaster. These are the main use cases in my organization as well as in external situations. A specific example of how AWS Elastic Disaster Recovery helped my organization during a real incident occurred last year when a major outage happened in our 5G RAN network. Due to the business continuity feature, it provided long-term support to resolve that emergency situation by raising emergency tickets and providing different commercial benefits. The rapid recovery accelerated the recovery processes because the entire recovery process was automated rather than manual. This allowed for quick failover to a staging area with minimal downtime required. We were able to resolve that situation in a very effective and advanced way.
I have worked with AWS Elastic Disaster Recovery for the past year. My feedback is that when we compare it, it's a good thing to have a centralized backup. When your stack is on AWS, it is very helpful, but I think when you have multi-cloud, that's where it may not be a great product. Also, from the cost side, it is good. The best use case for this would be if you're in AWS and you want to try things quickly without the actual disaster recovery cost that you usually have to incur. However, the challenge is the EBS snapshot. At the end of the day, they have snapshots, and they do have EBS snapshots which they capture. We ended up not using it, but we explored it for our own disaster recovery solutions that we were evaluating.
Our human resources solution is used by higher management competency. This is critical to the organization since it is used by higher management. ITM is really essential for the organization.
Learn what your peers think about AWS Elastic Disaster Recovery. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
If there is a data leak, incident, or compliance issue, auditors may want to verify whether there is a policy and plan in place for utilizing AWS Elastic Disaster Recovery. As part of a strategic approach, I have been part of a team ensuring compliance with various regulations, including HIPAA compliance. I have contributed to developing strategies to satisfy audits and inspections from various government bodies. These strategies outline the plans and features to be utilized if needed.
The primary use case for AWS Elastic Disaster Recovery is to ensure data replication and protection across diverse environments without the need for hypervisor integration.
AWS Solution Engineer at a tech services company with 51-200 employees
Real User
Apr 11, 2023
I've used the solution for migrations. I worked for a company that went Chapter 13, and we had to migrate into the cloud. I've used it for disaster recovery as well.
Infrastructure analyst specialized in cloud computing at IT2GO Solutions
Real User
Mar 9, 2023
My purpose for utilizing CloudEndure Disaster Recovery is to streamline our disaster recovery procedure. In the event of any issue arising in our on-premise infrastructure, we aim to quickly switch over to AWS. Our setup is designed to facilitate this process, and we frequently conduct tests to ensure its reliability. While we have yet to experience an actual disaster, we conduct multiple tests annually. Furthermore, as a partner, I implement this solution for our clients. Currently, we have five customers using it, with the number steadily increasing. We have the solution deployed on-premise located on the Amazon AWS infrastructure.
Lead DBA at a computer software company with 501-1,000 employees
MSP
May 12, 2022
For the CloudEndure DR, I have been using this for Oracle E-Business Suite and Oracle OBIEE. I've used it for the operating system and directory services as well.
Cloud Consultant at sonata information Technology Limited
Real User
Apr 28, 2022
We use CloudEndure Disaster Recovery for backing up our data and for recovery. My customers have some databases. They were looking for the DR solution. CloudEndure is easy, and block-level replication will happen. Whenever my primary site goes down, the DR site will be up, and the data will be there. The DR data is there, and it will be a replication back will be my primary site.
I am a solution architect and I analyze customer's information in order to suggest products for them. CloudEndure Disaster Recovery is one of the solutions that I am familiar with. It is used for backup and restore operations.
The entire company uses it for reports we are sent to research. We also have reports that we write for various clients and it helps us look for our research requirements. All of the data and information is stored on the cloud. There were a few instances in which the entire system got hacked. There was an issue with the system, the hard drive, so we used the cloud backup to retrieve all the information from three to four years down the line.
CloudEndure Disaster Recovery enables real-time replication and rapid recovery to enhance organizational resilience. Key features include block-level data replication, ease of use, cost-effectiveness, and automated recovery orchestration. Users benefit from increased efficiency, improved workflows, and enhanced data management, significantly improving organizational performance and business continuity.
AWS Elastic Disaster Recovery is a fully managed service that enables fast, reliable recovery of on-premises or cloud-based applications to AWS. We use it for minimizing downtime and data loss. There have been multiple situations where our production servers hosted on AWS went down, and we were able to shift to different servers, thereby minimizing the downtime with no data loss.
My main use case for AWS Elastic Disaster Recovery is for any databases or applications when they go down on a cross-region. For instance, when an application is spinning up into multiple regions, we lost one, and AWS Elastic Disaster Recovery helped us recover. In that situation, when there was an event that happened in the cloud stack, AWS Elastic Disaster Recovery helped us get things back up and running. Although this happened only once, we would like to have this multi-region, multi-data center level recovery for disaster recovery, so we are incorporating this technology.
AWS Elastic Disaster Recovery provides my team with a low-cost way to protect critical applications and ensure minimal service interruptions and data loss when a disaster occurs. The rapid recovery accelerates and automates the recovery process, allowing for quick failover to a staging area in AWS and minimal downtime. It replicates servers and data from on-premises data centers and other clouds to AWS, converting them to run natively on AWS after a disaster. These are the main use cases in my organization as well as in external situations. A specific example of how AWS Elastic Disaster Recovery helped my organization during a real incident occurred last year when a major outage happened in our 5G RAN network. Due to the business continuity feature, it provided long-term support to resolve that emergency situation by raising emergency tickets and providing different commercial benefits. The rapid recovery accelerated the recovery processes because the entire recovery process was automated rather than manual. This allowed for quick failover to a staging area with minimal downtime required. We were able to resolve that situation in a very effective and advanced way.
I have worked with AWS Elastic Disaster Recovery for the past year. My feedback is that when we compare it, it's a good thing to have a centralized backup. When your stack is on AWS, it is very helpful, but I think when you have multi-cloud, that's where it may not be a great product. Also, from the cost side, it is good. The best use case for this would be if you're in AWS and you want to try things quickly without the actual disaster recovery cost that you usually have to incur. However, the challenge is the EBS snapshot. At the end of the day, they have snapshots, and they do have EBS snapshots which they capture. We ended up not using it, but we explored it for our own disaster recovery solutions that we were evaluating.
I use the solution to deploy a Docker image application. It is hosted on GitHub, and the servers we run on are not ECR.
Our human resources solution is used by higher management competency. This is critical to the organization since it is used by higher management. ITM is really essential for the organization.
If there is a data leak, incident, or compliance issue, auditors may want to verify whether there is a policy and plan in place for utilizing AWS Elastic Disaster Recovery. As part of a strategic approach, I have been part of a team ensuring compliance with various regulations, including HIPAA compliance. I have contributed to developing strategies to satisfy audits and inspections from various government bodies. These strategies outline the plans and features to be utilized if needed.
The primary use case for AWS Elastic Disaster Recovery is to ensure data replication and protection across diverse environments without the need for hypervisor integration.
We are using AWS Elastic Disaster Recovery for backup purposes in our company.
We were using CloudEndure Disaster Recovery as a backup for websites when we had a double ISP outage.
I've used the solution for migrations. I worked for a company that went Chapter 13, and we had to migrate into the cloud. I've used it for disaster recovery as well.
My purpose for utilizing CloudEndure Disaster Recovery is to streamline our disaster recovery procedure. In the event of any issue arising in our on-premise infrastructure, we aim to quickly switch over to AWS. Our setup is designed to facilitate this process, and we frequently conduct tests to ensure its reliability. While we have yet to experience an actual disaster, we conduct multiple tests annually. Furthermore, as a partner, I implement this solution for our clients. Currently, we have five customers using it, with the number steadily increasing. We have the solution deployed on-premise located on the Amazon AWS infrastructure.
For the CloudEndure DR, I have been using this for Oracle E-Business Suite and Oracle OBIEE. I've used it for the operating system and directory services as well.
We use CloudEndure Disaster Recovery for backing up our data and for recovery. My customers have some databases. They were looking for the DR solution. CloudEndure is easy, and block-level replication will happen. Whenever my primary site goes down, the DR site will be up, and the data will be there. The DR data is there, and it will be a replication back will be my primary site.
I am a solution architect and I analyze customer's information in order to suggest products for them. CloudEndure Disaster Recovery is one of the solutions that I am familiar with. It is used for backup and restore operations.
The entire company uses it for reports we are sent to research. We also have reports that we write for various clients and it helps us look for our research requirements. All of the data and information is stored on the cloud. There were a few instances in which the entire system got hacked. There was an issue with the system, the hard drive, so we used the cloud backup to retrieve all the information from three to four years down the line.
Enterprise disaster recovery.