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?
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.
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?
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
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
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.
Ecstatic
What do you like best about the product?
Using block level replication a minimum rpo and rto is acheuved with an optimized use of infrastructure.
What do you dislike about the product?
Uptil now i have found cloud endure a very interesting product
What problems is the product solving and how is that benefiting you?
A minimum rto and rpois acheuved using block level replication which was very hard to acheive prior to the deployment
CloudEndure Disaster Recovery: A Reliable Cloud-Based Solution with Room for Improvement
What do you like best about the product?
Best things about CloudEndure Disaster Recovery is Ease of Use, Automated Replication and Recovery,Cost-Effective,Minimal Downtime,Multi-Platform Support,Replication Across Regions,Non-Disruptive Testing,Scalability
What do you dislike about the product?
Somethings which i dislike are Costs and Pricing Complexity,Dependency on AWS Ecosystem,Initial Replication Time,Complexity for Non-AWS Users,RTO and RPO Limitations,Lack of Physical Server Support,Support and Response Time
What problems is the product solving and how is that benefiting you?
CloudEndure Disaster Recovery solves the critical challenges of data loss, downtime, and costly disaster recovery solutions. Its cloud-based approach, automation, and scalability benefit businesses by providing a cost-effective, reliable, and easy-to-manage disaster recovery solution, ensuring business continuity and minimizing potential losses during disruptive events
Exceptional Solution in Disaster Recovery
What do you like best about the product?
CloudEndure Disaster Recovery is an exceptional solution that offers businesses the peace of mind they need in the face of unforeseen disasters. As a customer who has relied on this platform, I can confidently say that CloudEndure's capabilities go above and beyond in safeguarding critical data and ensuring business continuity.
One of the most impressive aspects of CloudEndure Disaster Recovery is its ease of implementation. The platform seamlessly integrates with existing infrastructure, regardless of the cloud provider or on-premises environment being used. Setting up the solution is straightforward, thanks to its user-friendly interface and comprehensive documentation. From initial setup to ongoing maintenance, CloudEndure simplifies the complex task of implementing and managing disaster recovery.
What do you dislike about the product?
Complexity for Non-Technical Users
Cost
Lack of Integration
What problems is the product solving and how is that benefiting you?
Data Loss Prevention
Business Continuity
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
