Continuous replication has reduced our recovery costs and secures critical workloads in minutes
What is our primary use case?
My main use case for AWS Elastic Disaster Recovery is continuous replication.
A specific example of how I use continuous replication with AWS Elastic Disaster Recovery is that we use it for low-cost EBS volumes and smaller replication servers to keep our data synchronized in near real-time.
For us, it results in approximately 50 to 80% cost reduction.
What is most valuable?
The best features AWS Elastic Disaster Recovery offers, in my opinion, are its RTO and cost-effective replication.
When I say cost-effective for replication, it makes a difference for my team and my operations compared to warm standby or active-active configuration. The RTO is excellent.
AWS Elastic Disaster Recovery has positively impacted my organization by securing and stabilizing our platform. It has improved RPO in seconds and RTO in minutes.
What needs improvement?
I would like to add a point of improvement about the features, specifically concerning native cyber resilience and air gapping.
AWS Elastic Disaster Recovery can be improved regarding ransomware and insider threats.
Because the replication is continuous and block-level, if a production server is hit by ransomware, the encrypted garbage data is often replicated to the DR site in near-real time. This is an area that needs improvement.
For how long have I used the solution?
I have been using AWS Elastic Disaster Recovery for almost five years.
What do I think about the stability of the solution?
AWS Elastic Disaster Recovery is absolutely stable.
What do I think about the scalability of the solution?
The scalability of AWS Elastic Disaster Recovery is 10 out of 10.
How are customer service and support?
The customer support is amazing, and it is the best customer support I have ever had.
I rate the customer support of AWS Elastic Disaster Recovery 10 out of 10.
Which solution did I use previously and why did I switch?
I did not previously use a different solution.
How was the initial setup?
I purchased AWS Elastic Disaster Recovery through the AWS Marketplace.
What was our ROI?
I have seen a return on investment, specifically in terms of time saved in case of disaster recovery.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that pricing is fair, and you pay for the use.
Which other solutions did I evaluate?
Before choosing AWS Elastic Disaster Recovery, I did not evaluate other options because of the pre-existing relationship with AWS.
What other advice do I have?
My advice to others looking into using AWS Elastic Disaster Recovery is that you only pay for the full-scale compute and high-performance storage after you initiate a drill or an actual failover.
I rate this review a 10 out of 10.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Rapid recovery has minimized downtime and protects critical data during frequent outages
What is our primary use case?
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.
What is most valuable?
This service is very handy in terms of using affordable storage, minimal compute resources, and point-in-time recovery to ensure business continuity during outages or disasters.
Continuous block-level replication stands out for me the most. AWS Elastic Disaster Recovery continuously replicates block-level data from the source environment to a staging area in AWS, ensuring that data is always up to date and minimizing data loss during a disaster. Other valuable features include automated failover and recovery as well as non-disruptive testing.
AWS Elastic Disaster Recovery supports a wide range of source environments, including VMware, Hyper-V, physical servers, and other cloud providers, making it versatile for different IT infrastructures. The flexible recovery options allow recovery of applications to their original environment or to a new instance in AWS while retaining the existing metadata and security parameters. The cost-effective staging area design reduces costs by utilizing affordable storage and minimal compute resources, making it economical for ongoing replication.
It has greatly impacted our company's specific outcomes and improved production failures. For customers, it has been quite beneficial in terms of providing automated failover and recovery options as well as flexible recovery options, which allows recovery of applications to the original environment or to a new instance in AWS while retaining the existing metadata and security parameters, which is quite useful. Encryption and security is also one of the best features. Data is encrypted during transit and at rest, ensuring information remains secure throughout the disaster recovery process.
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. There has been approximately a thirty percent improvement in terms of recovery time.
What needs improvement?
AWS Elastic Disaster Recovery can be improved through regular drills to ensure that all resources are properly prepared for disasters with scheduled drills. This includes testing and understanding failback, which is crucial for a comprehensive disaster recovery plan.
Monitoring and health checks are important to continuously monitor the health of the ongoing replication using the AWS Elastic Disaster Recovery console or programmatically. This helps identify any servers that may require attention and ensures that the application is functioning correctly. Creating a CloudFormation template that can create the necessary network resources on demand is useful for disaster recovery.
There should be documentation and best practices guidance so that teams can follow best practices for implementation and maintenance of disaster recovery from on-premises using AWS. This includes a written recovery plan as well as regularly updating it with findings and required changes.
Within the scope of improvements, there are many possibilities, but it is currently providing some great results. The scope of improvements can include monitoring and health checks as well as documentation with best practices for documentations, and conducting regular drills.
For how long have I used the solution?
I have been using AWS Elastic Disaster Recovery for around two years.
What do I think about the stability of the solution?
AWS Elastic Disaster Recovery has been quite stable.
What do I think about the scalability of the solution?
The scalability is quite good and we were able to scale this service to many of the services that our company uses. It has been quite fast with reliable recovery of on-premises as well as our private cloud.
How are customer service and support?
Customer support has been quite good and has definitely solved many issues we have faced.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, we were using Azure Elastic Disaster Recovery, but now we are using AWS Elastic Disaster Recovery, which is doing a great job.
What was our ROI?
In terms of time saved, it has greatly improved because of production failures, and that time is definitely saved because of the great documentation and plans that everyone understands. There are also fewer employees needed now because of the good structured planning for AWS Elastic Disaster Recovery, so fewer site reliability engineers are required.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
We evaluated other alternatives, but they were not providing good cost options. Commvault Cloud, Rubrik, and OpenText Recover were evaluated, but the number of features in AWS Elastic Disaster Recovery is quite huge and they cannot match that.
What other advice do I have?
The features that really make AWS Elastic Disaster Recovery a ten out of ten include continuous block-level replication, automated failover and recovery, non-disruptive testing, support for various environments, flexible recovery options, integration with AWS services, cost-effective staging area, encryption and security, customizable launch settings, and post-launch actions.
There are a lot of features that should make AWS Elastic Disaster Recovery appealing to potential users because of the huge market capture by AWS and the fact that most companies are using AWS, so that option should be considered.
We have been a customer only. I give this product a rating of ten out of ten. AWS Elastic Disaster Recovery has been doing quite a good job overall.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Best desaster recovery in this digital Era!
What do you like best about the product?
CloudEndure Disaster Recovery is a product that provides robust disaster recovery solutions, ensuring business continuity and resilience to IT systems. What I appreciate most about CloudEndure Disaster Recovery is its ability to minimize downtime and data loss in any disaster scenario.
What do you dislike about the product?
While CloudEndure Disaster Recovery has been largely effective in ensuring business continuity and minimizing data loss for our organization, I believe Initial Setup Complexity Could be improved. Although the overall use is quite intuitive, the initial setup can be complex and might require specialized knowledge. More detailed documentation or guided setup wizards could simplify this process.
What problems is the product solving and how is that benefiting you?
CloudEndure Disaster Recovery is designed to address critical challenges related to data protection, disaster recovery, and business continuity. CloudEndure ensures that systems are quickly recoverable in the event of any failure, minimizing downtime. In the fast-paced fintech industry, downtime can result in significant revenue loss and customer dissatisfaction, so this quick recovery is essential.
Propose CloudaEndure DR to Client for their AWS to compete with Azure Site Recovery (ASR)
What do you like best about the product?
Allows low cost failover while maintaining high RTO and RPO.
Instead of running full fledged workloads in DR env, cloud endure allows the ability to run small no. of VMs to replicate data for mass VMs.
What do you dislike about the product?
None that come to mind at the moment. I have been very content in my experience with leveraging CloudEndure.
What problems is the product solving and how is that benefiting you?
It is allowing automated failover to DR region at low cost
Hassle free disaster data recovery.
What do you like best about the product?
What I like best about this service is that it supports all types of infrastructures physical machines, virtual machines (including VM wares), Cloud-based machines like OpenStack etc.
What do you dislike about the product?
Nothing much to dislike, it works perfectly good for my use case.
What problems is the product solving and how is that benefiting you?
For me, this service saves a lot of time and money by carrying out this process manually, and since the recovery is fast it reduces the downtime by a substantial amount.