Choosing a redundancy option for durability and availability targets, and what customer-managed account failover does.
From Ultra Transcenders AZ-305 by Tony Rough (publishing soon)
Redundancy decides how many copies of your data exist and how large a failure they can survive, from a single rack up to a whole region. Choose the cheapest option that meets the failure scenario you must tolerate, and remember that only the geo-redundant options support account failover.
Figure 5.1 shows where the copies live under each option.
| Option | Copies | Survives | Secondary readable |
|---|---|---|---|
| LRS | 3 in one datacentre | Disk/rack failure | – |
| ZRS | 3 across availability zones, one region | Datacentre (zone) failure | – |
| GRS | 6: LRS primary + LRS in paired region | Regional outage | Only after failover |
| RA-GRS | As GRS | Regional outage | Yes, read-only secondary endpoint |
| GZRS / RA-GZRS | ZRS primary + LRS secondary | Zone and region | RA- only |
Common trap: Configuring ZRS before a failover — ZRS keeps all copies in one region and has no secondary, so there is nothing to fail over to. Failover needs GRS, RA-GRS, GZRS or RA-GZRS.
This note is one section of Ultra Transcenders AZ-305: Designing Microsoft Azure Infrastructure Solutions, an independent study guide that explains every topic the exam covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to Microsoft Learn.
Publishing soon on Amazon in Kindle and paperback editions.
About the book · Free AZ-305 glossary · All AZ-305 study notes
How to pick between Azure SQL Database, Azure SQL Managed Instance and SQL Server on Azure VMs from compatibility and management requirements.
Zone redundancy, active geo-replication and failover groups for Azure SQL, with the RPO and RTO each design gives.
A decision guide to Azure compute services by control, scale and operational effort.
How private endpoints and service endpoints differ, and how to design private DNS for hybrid networks.
Choosing between Azure's global and regional, layer 4 and layer 7 load-balancing services.
The five Cosmos DB consistency levels, what each guarantees, and the latency and availability trade-offs.
System-assigned vs user-assigned managed identities, workload identity federation and when to use each.