CloudEndure Disaster Recovery to AWS

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 has positively impacted my organization. We have a priority one application that was recently deployed, and it was important for us to recover the data when the cloud stack went down. Since deploying AWS Elastic Disaster Recovery, we have mostly seen an improvement in uptime, which contributes to reducing downtime.

The best features AWS Elastic Disaster Recovery offers are the insights and alerting, which inform developers or application developers about what's going on and how the system is running.

The insights and alerting features help my team day-to-day by allowing SREs to know when an event has happened and how we are supposed to be doing recovery. They provide alerts to the SREs and groups that are subscribed, and they are alerted early. I am currently exploring the features, but for now, I find it very useful in the event of the disaster that happened.

I think insights are an area for improvement. It would be beneficial to get some insights when a disaster happens, including identification and probable solutions to ensure effective recovery. That insight and solution suggestion area is the main thing I would want to see improved.

We believe that customer support for AWS Elastic Disaster Recovery needs to be improved because although we do raise tickets, the response can take some time.

I have been using AWS Elastic Disaster Recovery for two years.

AWS Elastic Disaster Recovery is stable. It is definitely a stable application.

The scalability of AWS Elastic Disaster Recovery is good. We can expand it to multiple data centers or different areas such as EMEA and APAC.

I would rate the customer support an eight, as it often takes a lot of time to engage and get a solution. About eighty percent of the time, I think it will be resolved quickly.

Positive

Previously, we were using a homegrown application that tracks these systems before switching to AWS Elastic Disaster Recovery.

We did purchase AWS Elastic Disaster Recovery through the AWS Marketplace , but it's mostly the procurement team that has handled that. The management, particularly the procurement team, looks at pricing and setup costs, so I know a little about pricing, but I'm not directly involved in it.

We are just customers and consume a lot of AWS  services, and do not have another business relationship with this vendor.

We have seen a return on investment by needing fewer employees for maintenance and related matters. We no longer have to schedule employees on weekends since the system automatically triggers alerts, allowing engineers to respond as needed.

We did not evaluate other options before choosing AWS Elastic Disaster Recovery.

My advice for others looking into using AWS Elastic Disaster Recovery is to definitely consider it if you are scaling your applications significantly, especially if your applications are spanned across different regions. I would give this product an eight out of ten because it's a fair score. The education of our technology and operations or SRE teams is needed since most people don't know, only a few do. I suggest that improvement in customer service for disaster recovery and the alerting system would be great.

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.

AWS Elastic Disaster Recovery offers continuous data replication for minimal data loss, automated disaster recovery drills for regular testing, rapid recovery in minutes, and cost savings by only paying for active replication and staging resources.

It features a unified process for testing, recovering, and falling back applications.

It also offers automated network replication, point-in-time recovery, and support for a wide range of source servers, including on-premises and other cloud workloads. These are the standout aspects.

Implementing AWS Elastic Disaster Recovery in my organization eliminated the need for costly idle resources by only using minimal compute and affordable storage for the staging area during normal operations.

The only cost incurred is for full-scale recovery resources when needed.

The performance of non-disruptive automated drills to test the recovery plans ensures the environment is ready to go live with automated cleanup of drill resources. Rapid recovery in minutes allowed services to launch recovery instances within minutes, significantly reducing downtime. After reducing this downtime, my organization made a profit in the previous financial year.

AWS Elastic Disaster Recovery performs well at this moment. However, some points can be mentioned for further improvement. It may benefit from optimizing replication settings, right-sizing different instances, and conducting frequent recovery drills.

Improving performance and resilience also involves automatic recovery processes, leveraging multi-account strategies for isolation, and using tools such as AWS CDK for automated deployments. Monitoring logs with tools such as CloudWatch Log Insights and creating cross-region replications are additional strategies for enhancement.

Small improvements pertain to right-sizing instances, enabling features, and choosing instance types for the recovery environment that match our source server requirements to avoid unnecessary costs while ensuring performance during recovery events. The rest functions well.

I have been using AWS Elastic Disaster Recovery for around 4.5 years.

AWS Elastic Disaster Recovery seems very stable and performs reliably in my experience.

AWS Elastic Disaster Recovery handles workloads in a very good manner, smoothly accommodating growing needs regarding scalability.

I have interacted with the customer support for AWS Elastic Disaster Recovery multiple times, and their support is very strong. They have excellent technical skills and resolve issues within hours.

Positive

My experience with pricing, setup cost, and licensing is satisfactory and sufficient.

I have seen a return on investment after using AWS Elastic Disaster Recovery. Cost reduction happened in my organization, resulting in approximately 15 to 20% profit made in the last financial year.

The rapid recovery in minutes directly helped decrease downtime, which benefited our customers significantly.

Regarding financial impact, the downtime decrease and cost-effective model helped my organization make a profit in the last year that was approximately 20 to 25% bigger than the previous year when AWS Elastic Disaster Recovery was not used.

I did not evaluate other options before choosing AWS Elastic Disaster Recovery because everyone suggested using it from both LinkedIn and other social media platforms.

My advice for others looking into using AWS Elastic Disaster Recovery is to try it for at least a few months, and you will see the differences. I assure you that you will not want to stop using it. I have rated this review a 9.

Neutral

I use the solution to deploy a Docker  image application. It is hosted on GitHub , and the servers we run on are not ECR.

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. 

It offers seamless integration with services like ACL , EKS, and Fargate for deploying containerized applications. It works great with AWS, and it is flexible to use a public repository for open-source projects or a private repository for secure storage.

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 push or pull. This would detail user activity directly in the ACL  console for easier debugging and auditing. 

Additionally, an improved AWS pricing model is needed. AWS charges for storage and data transfer, which can add up, especially with large images or frequent pulls. Improvement should focus on offering more storage or better volume discounts for long-term use. It would also be beneficial to allow free pulls within the AWS account and vision. 

Moreover, image scanning for vulnerabilities can sometimes be slow, especially for large images. Speeding up the scanning process or providing optimized scanning for critical workflows would be welcome advancements.

I have used it for about seven months now.

Since the time I have been using ECL, my application on AWS has not broken down. I have not had any issues with it for now. It is working well. It is very good and very reliable.

I never had to contact the support team.

I didn't really use Azure . However, that was in my last organization before I joined this new one. 

I would rate AWS nine out of ten.

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.

For the past year, I have been using AWS , as there was previously no native replication service available. Initially, they offered services like CloudEndure, which was a third-party service. This caused problems with integrations with existing servers. However, with AWS Elastic Disaster Recovery  Service being a native service, integration is seamless. Moreover, since it is a managed service, I reduce my time to manage infrastructure and applications, which adds another benefit.

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.

I have been using it since 2019.

AWS is not difficult, but the cost associated with replicating data to another region can be significant. This is due to services like the duplication server, which continuously runs in AWS. I have more than 200 hosts, including email solutions and others, which contribute to the high cost. Cost is a concern. Otherwise, the service is reliable.

Customer service is quite helpful. I have AWS enterprise-level support, which is very beneficial. In case of any issue, they are ready to provide support within the defined SLA timeline.

Positive

Earlier, I worked with IBM Sonavi. I stopped using it since we moved from on-premise to cloud. It's not in use right now.

There were no issues during the initial setup.

The implementation is actually managed by our partner. I have taken a rate per user storage. The licensing part is completely managed by the partner.

For the past year, I have been using AWS, as there was previously no native replication service available. Initially, they offered services like CloudEndure, which was a third-party service. This caused problems with integrations with existing servers. However, with AWS Elastic Disaster Recovery  Service being a native service, integration is seamless, highlighting the return on investment.

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 cost is separate.

Although no financial benefit from using it has been observed, I recommend the solution. The overall product rating is eight out of ten.