Well-Architected & resilience
19 posts, newest first.
#availability#availability-zones#azure-automation#azure-backup#azure-service-health#azure-site-recovery#backup#business-continuity#chaos-studio#data-replication#disaster-recovery#dns#failover#health-checks#high-availability#identity#incident-response#migration#recovery-planning#reliability#replication#rpo-rto#troubleshooting#well-architected-framework#zonal-deployment#zone-redundant
Use recovery evidence to refine an availability target Run a Well-Architected review with the operations team
All posts in this category
Check hidden dependencies after an application failover 
Plan regional recovery without overlooking identity and DNS Record a recovery decision before an infrastructure change Choose a deployment approach that limits the impact of failure Define health checks across application and infrastructure layers Review resilience trade-offs in a cost-constrained workload Investigate a failover that leaves an application unavailable Build a recovery runbook with an explicit validation step Plan an outage test that produces useful evidence Document an application dependency map for a recovery exercise 
Choose availability zones without assuming application resilience Review a workload against the Well-Architected reliability pillar 
Set RPO and RTO before selecting a recovery design 
Map an Azure workload across its failure domains 
Separate backup, high availability and disaster recovery Turn an application availability target into design decisions
Plan regional recovery without overlooking identity and DNS Record a recovery decision before an infrastructure change Choose a deployment approach that limits the impact of failure Define health checks across application and infrastructure layers Review resilience trade-offs in a cost-constrained workload Investigate a failover that leaves an application unavailable Build a recovery runbook with an explicit validation step Plan an outage test that produces useful evidence Document an application dependency map for a recovery exercise Choose availability zones without assuming application resilience Review a workload against the Well-Architected reliability pillar Set RPO and RTO before selecting a recovery design Map an Azure workload across its failure domains Separate backup, high availability and disaster recovery Turn an application availability target into design decisions