AWS Disaster Recovery

NOVEMBER 24, 2020

That’s why many customers replicate their mission-critical workloads in multiple places using a Disaster Recovery (DR) strategy suited for their needs. Depending on the RPO and RTO of the mission-critical workload, the requirement for disaster recovery ranges from simple backup and restore, to multi-site, active-active, setup.

Disaster Recovery 63

Disaster Recovery Architecture Internet Outage 63

AWS Disaster Recovery

MARCH 10, 2023

Welcome to the third post of a multi-part series that addresses disaster recovery (DR) strategies with the use of AWS-managed services to align with customer requirements of performance, cost, and compliance. Related information Want to learn more? Explore the following resources within this series and beyond!

Disaster Recovery 93

Disaster Recovery Activation Failover Management 93

AWS Disaster Recovery

JANUARY 20, 2021

This post was co-written by Anandprasanna Gaitonde, AWS Solutions Architect and John Bickle, Senior Technical Account Manager, AWS Enterprise Support. Many AWS customers have internal business applications spread over multiple AWS accounts and on-premises to support different business units. Introduction.

Architecture 70

Architecture Failover High Availability Application 70

AWS Disaster Recovery

APRIL 27, 2021

Building disaster recovery (DR) strategies into your system requires you to work backwards from recovery point objective (RPO) and recovery time objective (RTO) requirements. Earlier, we were able to restore from the backup but wanted to improve availability further. Minimum business continuity for failover.

Architecture 76

Architecture Resilience Application Backup 76