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.
CloudEndure Disaster Recovery to AWS
CloudEndure, an AWS companyExternal reviews
12 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Rapid recovery has minimized downtime and protects critical data during frequent outages
What is our primary use case?
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?
Positive
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)
Cross-region recovery has protected critical apps and reduces downtime with proactive alerts
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using AWS Elastic Disaster Recovery for two years.
What do I think about the stability of the solution?
AWS Elastic Disaster Recovery is stable. It is definitely a stable application.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously, we were using a homegrown application that tracks these systems before switching to AWS Elastic Disaster Recovery.
How was the initial setup?
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.
What about the implementation team?
We are just customers and consume a lot of AWS services, and do not have another business relationship with this vendor.
What was our ROI?
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.
Which other solutions did I evaluate?
We did not evaluate other options before choosing AWS Elastic Disaster Recovery.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Centralized backup facilitates quick recovery processes and effective disaster recovery drills
What is our primary use case?
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.
What is most valuable?
I appreciate the automated orchestration of recovery processes in this solution. That's a good thing, especially once you are able to configure something with this tool. I haven't tested the automated recovery, but they do support it. It is beneficial, especially integration with Route 53 and automatically using Route 53 to switch to a different region directly.
Because it has native integrations with all the Route 53 features, that's a good aspect. The part I really appreciated about it was they're not just AWS Backup; along with that, they give you an option to quickly do the drills. If you want to conduct DR drills, it's very useful.
What needs improvement?
I don't think there is any bad feature in AWS Elastic Disaster Recovery as such. It's more of when you do disaster recovery, you think of it more holistically. You want flexibility in terms of options. I would say it did not provide enough flexibility for all our backup needs. It had one single way of just supporting the EBS backup, or you can say volume-level backup. But let's say you want to integrate with your current backup solution; that kind of flexibility is what I would say is missing.
In terms of improvements for AWS Elastic Disaster Recovery, for any backup and disaster products, I would want it when companies are trying to evaluate these products, the biggest challenge is you want the most cost-optimal way because it's insurance.
AWS is already highly available, and you can have your infrastructure just in multiple AZs, and your life will be fine, considering the low probability of an AZ going down because of AWS's scale. You do disaster recovery basically for insurance and compliance, so it's crucial to ensure that it's very cost-optimal. There are different models that balance cost and recovery time objectives, but I have not seen any innovation; these are very old practices.
Additionally, while the storage side is key because you want your data to be there on both sides, the speed at which you can build your infrastructure also matters. It's mostly about data storage. For data storage, if you architect your storage properly, you can actually bring it up faster. For example, with a database cluster, if your database size doesn't exceed certain limits, it will significantly improve recovery time. However, these guidelines aren't offered by backup tools, as they sort of work against them. Still, to make backup cost-optimal, it is not just about the tool; it's also about how you architect your infrastructure.
For how long have I used the solution?
I have experience working with AWS Elastic Disaster Recovery for about six or seven months.
How are customer service and support?
Being an enterprise customer, I find the technical support from AWS very supportive.
How would you rate customer service and support?
Neutral
What other advice do I have?
Regarding the security features, including encryption provided by AWS Elastic Disaster Recovery, security is dependent on the user's needs. Encryption is something you need to enable based on your data and where you're storing it. I don't remember if they have an option where, by default, whatever backup you have is secured, since what you're storing is still in your own S3 or something. I think they charge you based on the amount of data. It's a shared responsibility model, but I believe they do offer a feature where you can enable encryption at rest and encryption in transit for your data, but it's our responsibility as customers; I don't think AWS does it for you.
For AWS Elastic Disaster Recovery, regarding the deployment model, we mostly tried the backup restore option. We typically haven't explored the other deployment options they offer yet. We start with a very simple backup restore and chose it for specific use cases, MongoDB backup, but as of right now, we haven't looked at it more holistically. Overall, we felt that it doesn't support all the types of backup that we have.
On a scale of one to ten, I would rate AWS Elastic Disaster Recovery an eight.
Seamless service management and integration with good flexibility
What is our primary use case?
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 is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have used it for about seven months now.
What do I think about the stability of the solution?
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.
How are customer service and support?
I never had to contact the support team.
Which solution did I use previously and why did I switch?
I didn't really use Azure. However, that was in my last organization before I joined this new one.
What other advice do I have?
I would rate AWS nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Managed services with seamless integration and good reliability
What is our primary use case?
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.
What is most valuable?
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.
What needs 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. I have to calculate whether my data is replicated to the Adarabad region or not. These features, if available in AWS, would be beneficial.
For how long have I used the solution?
I have been using it since 2019.
What do I think about the stability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
There were no issues during the initial setup.
What about the implementation team?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
Although no financial benefit from using it has been observed, I recommend the solution. The overall product rating is eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Prevents security breaches and covers data leak and recovery
What is our primary use case?
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.
What is most valuable?
AWS, as a cloud platform, helps build trust in its services. There have been incidents where clients using Amazon services faced security breaches, but these stories seem more frequent with Microsoft. This might be a personal bias, and others may have different experiences. AWS proactively protects its reputation by addressing issues and investing heavily in its tools, app tech, and engineers.
What needs improvement?
Pricing could be improved.
What do I think about the stability of the solution?
The solution is stable because we haven't had any incidents.
What do I think about the scalability of the solution?
It's scalable because of the value and investment it has made in terms of capacity.
What was our ROI?
Every business survives because of its reputation. In case of any disaster, AWS cannot guarantee 100% security, but it helps protect the company's reputation. It also assists in providing remedies to solve any particular problems that may arise. AWS is a platform that supports businesses.
What's my experience with pricing, setup cost, and licensing?
It has pay-as-you-go pricing. The cost will be different if you are not utilizing it as often as possible because there are costs beforehand and after an incident.
What other advice do I have?
If you are using AWS for your disaster recovery, it's important to use AWS Elastic Disaster Recovery to ensure continuity in case of any failures. Having a strategic approach means considering the cost of disaster recovery as part of your overall planning.
Overall, I rate the solution an eight out of ten.
Provides ease of deployment and continuous data protection
What is our primary use case?
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.
What is most valuable?
The product's most valuable features include its ease of deployment, cost-effectiveness due to AWS's pay-as-you-go pricing model, and continuous data protection.
What needs improvement?
The product could be improved by incorporating more AI-driven automation for deployment and additional security features. These enhancements would make the solution even more user-friendly and secure.
For how long have I used the solution?
I have been using AWS Elastic Disaster Recovery for several years.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
The platform offers excellent scalability, allowing it to accommodate the needs of both small-scale environments and large enterprises without significant changes to the setup.
How are customer service and support?
The technical support has been effective, providing necessary assistance and resolving issues promptly.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used solutions like Double-Take and Carbon. We switched to AWS Elastic Disaster Recovery because of its versatility in deployment across different environments without requiring specific hardware or hypervisor dependencies.
How was the initial setup?
The initial setup can vary in complexity depending on the specific environment and setup requirements. While the deployment process is generally straightforward, detailed planning and configuration are essential to ensure a successful implementation.
What about the implementation team?
The implementation was handled by our in-house team.
What was our ROI?
The ROI has been substantial, primarily due to its cost-effective pricing model. It reduces downtime and data loss during disaster recovery scenarios.
Which other solutions did I evaluate?
We evaluated several other options, including traditional on-premises disaster recovery solutions and cloud-based offerings.
What other advice do I have?
AWS Elastic Disaster Recovery is a robust and reliable solution for disaster recovery needs. However, thorough planning and regular monitoring are crucial to maximizing its benefits and ensuring seamless operation.
I rate it a nine.
Cloud-based solution enhances company backup but comes with high costs
What is our primary use case?
We are using AWS Elastic Disaster Recovery for backup purposes in our company.
How has it helped my organization?
AWS Elastic Disaster Recovery is convenient because it is cloud-based technology.
What is most valuable?
The strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based.
What needs improvement?
The cost of AWS Elastic Disaster Recovery is seen as expensive.
For how long have I used the solution?
We have been using AWS Elastic Disaster Recovery for five or six years.
What do I think about the stability of the solution?
I rate the stability of AWS Elastic Disaster Recovery as nine out of ten.
What do I think about the scalability of the solution?
I rate the scalability of AWS Elastic Disaster Recovery as nine out of ten.
How are customer service and support?
The customer service and technical support for AWS are very good and helpful. I rate it ten out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did not work with any other products before AWS.
What about the implementation team?
We use a third-party consultant company to help with integration.
What's my experience with pricing, setup cost, and licensing?
The pricing of AWS is considered expensive compared to other options.
Which other solutions did I evaluate?
We have also used Microsoft Azure as an alternate solution.
What other advice do I have?
I would recommend AWS Elastic Disaster Recovery to other users.
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)
Has a complex setup and takes about a day to get the network configured properly for a network failover test
What is our primary use case?
We were using CloudEndure Disaster Recovery as a backup for websites when we had a double ISP outage.
What is most valuable?
CloudEndure Disaster Recovery is a fairly stable solution.
What needs improvement?
The solution never reduced our system's downtime. It would take us about a day to get the network configured properly for even doing a network failover test. The solution's orchestration capabilities did not simplify our disaster recovery process.
The solution's network setup and a lot of the control tower setup could be improved. The solution should provide more ease of use for the creation of cloud appliances for firewalls.
For how long have I used the solution?
I have been using CloudEndure Disaster Recovery for three years.
What do I think about the stability of the solution?
I rate the solution an eight out of ten for stability.
What do I think about the scalability of the solution?
I rate the solution a five or six out of ten for scalability.
How was the initial setup?
The solution's initial setup was fairly complex, and the company that did the initial setup for us messed up a couple of times.
On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a one or two out of ten.
What about the implementation team?
The solution was deployed by three people from my team and two engineers from the company.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
The solution's replication was fine. We faced issues when we actually tried to utilize it. Every time we made a big change to any of the on-premise servers that were being replicated, we'd always have to change our replication engines, sizing, and the disc it's written on. Otherwise, it would end up taking around 30 days for a small monthly Windows update to replicate.
I would not recommend CloudEndure Disaster Recovery to other users because of all the issues we had with the wrong sizing and the fact that there are better solutions in the market.
Overall, I rate the solution a two out of ten.
CloudEndure Disaster Recovery
What do you like best about the product?
Cross-infrastructure machine conversion and facilitates Block-level
replication
replication
What do you dislike about the product?
It is good and nothing as of now for disliking.
What problems is the product solving and how is that benefiting you?
Block-level
replication
replication
showing 1 - 10