Remove Architecture Remove Disaster Recovery Remove High Availability Remove Whitepaper
article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part IV: Multi-site Active/Active

AWS Disaster Recovery

In my first blog post of this series , I introduced you to four strategies for disaster recovery (DR). The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. Each Region hosts a highly available, multi- Availability Zone (AZ) workload stack.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part II: Backup and Restore with Rapid Recovery

AWS Disaster Recovery

In a previous blog post , I introduced you to four strategies for disaster recovery (DR) on AWS. These strategies enable you to prepare for and recover from a disaster. Every AWS Region consists of multiple Availability Zones (AZs). To reduce recovery time, detection should be automated. Related information.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Minimizing Dependencies in a Disaster Recovery Plan

AWS Disaster Recovery

The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. What does static stability mean with regard to a multi-Region disaster recovery (DR) plan? Testing your disaster recovery plan. Even a simple distributed system may be too complex to operate reliably.

article thumbnail

Using Route 53 Private Hosted Zones for Cross-account Multi-region Architectures

AWS Disaster Recovery

Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. Your business units can use flexibility and autonomy to manage the hosted zones for their applications and support multi-region application environments for disaster recovery (DR) purposes.

article thumbnail

Journey to Adopt Cloud-Native Architecture Series: #3 – Improved Resilience and Standardized Observability

AWS Disaster Recovery

In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. Building disaster recovery (DR) strategies into your system requires you to work backwards from recovery point objective (RPO) and recovery time objective (RTO) requirements.