The best features that AWS Elastic Disaster Recovery offers is continuous block-level replication with a very low RPO. It keeps replicating the changes from the source servers to the DR region almost in real-time. Even if any failure happens, we can recover the servers with minimal data loss, which is one of the best features. The other thing which I really value is the Test Launch feature; we can perform DR drills anytime without affecting the production environment. Overall, the best combination of AWS Elastic Disaster Recovery is its near real-time replication and quick recovery testing, and this makes the service very useful in real-world scenarios.

AWS Elastic Disaster Recovery has impacted my organization positively by significantly reducing our recovery time, which is our RTO, and also the data loss risk. Because the servers are continuously replicating to the DR region with minimal downtime, in case of any major issue in the primary environment, we can launch the recovery instance within minutes. Another positive impact was during the DR drills and audits. Since AWS Elastic Disaster Recovery allows non-disruptive test launches, we were able to demonstrate our DR capabilities more confidently to the internal teams and management. Overall, it gave the organization more confidence in handling any outages and also improved the overall resilience of our infrastructure.

AWS Elastic Disaster Recovery offers many best features including continuous data replication, fast failover and recovery, non-disruptive testing and disaster recovery drills, automated failover and orchestration, cost-efficient staging environment, and integration with AWS ecosystem.

The automated failover and orchestration features of AWS Elastic Disaster Recovery have made our recovery process much more efficient. Instead of manually rebuilding servers or configuring environments during a failure, the platform allows us to quickly launch recovery instances with predefined settings. This automation reduces the chance of human error and significantly shortens our recovery time. It has also made disaster recovery testing easier because we can simulate failure scenarios and verify that our system can be restored quickly without disrupting production workloads.

The features of AWS Elastic Disaster Recovery reduce manual work, lower human error, enable faster recovery, and allow for better disaster recovery testing.

AWS Elastic Disaster Recovery has positively impacted our organization by improving our overall resilience and reducing downtime risk. With continuous data replication and fast system recovery, it reduces downtime risk and simplifies disaster recovery operations through automation and easy testing. The key positive impacts include reduced downtime, improved business continuity, and simplified recovery operations.

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.

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.

We use AWS Elastic Disaster Recovery because it provides low RPO, RTO, supports failover testing, and eliminates the need for a secondary data center. It is cost-effective and suitable for business continuity planning.

AWS Elastic Disaster Recovery uses continuous block-level replication. Its lightweight agent is installed on a source server, so data replicates to a low-cost staging area in AWS. During a disaster, we launch EC2 instances from replicated data. The low RPO at a seconds-level replication and a fast recovery with a low RTO provide the most cost-effective way, paying mostly for storage until failover.

The best feature that AWS Elastic Disaster Recovery offers is the full server-level replication and near-real-time disaster recovery. The benefits are fast recovery, low RPO, and it is cost-effective.

The fast recovery and low RPO of AWS Elastic Disaster Recovery have made a significant difference for my team and organization by ensuring minimal data loss and quick restoration of services.

Using AWS Elastic Disaster Recovery services, our organization noticed a very positive impact. The first positive impact is that it significantly improved our disaster recovery posture. We minimized data loss, which increased system reliability. It also reduced the need for maintaining a separate DR data center, which lowered infrastructure costs.

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.

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 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.

The strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based.

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.

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.

The ability to clone is very helpful.

The installation process is very easy.

The solution's cost is reasonable. It's on the cheaper side and not too expensive for users. 

It is a scalable product. 

In terms of stability, it's reliable.

CloudEndure Disaster Recovery is a fairly stable solution.

It is easy to use. I haven't had any issues with the client and console. 

When we tested it, it worked fine. 

The solution is free to use. 

The setup is pretty straightforward.

It's stable.

The solution is scalable.

Technical support is helpful and responsive. 

The most valuable aspect of CloudEndure Disaster Recovery is its instant block replication feature. This allows us to perform live block verification and eliminates the need to concern ourselves with recovery point objectives. This capability is particularly advantageous for critical workloads.

For regular backup and restore solutions, this product is fine.

The speedy, quick configuration and installation was the initial reason for the product and what I enjoyed about it. Now, it just continues to be simple and works well.

• Ease of use
• Reliability
• Cost
• Stability

Disaster recovery. It is what we have the product for.

The ability to replicate our database and our data from one cloud to another is the most valuable feature. We are using it for disaster recovery so we replicated all our databases from Rackspace Cloud to Amazon Cloud. We moved from Rackspace to AWS because we didn't want to end up in a situation where we would be locked, so we chose to replicate our databases to another public cloud.