Holds disaster-recovery copies of data or workloads, typically hundreds of miles away from the primary location. Geo-redundant storage always uses the primary's pair for this, with no option to change it.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Secondary region in context, with comparison tables and the common traps.
Terms in this definition
- GRS
Geo-redundant storage keeps six copies in total: three locally redundant in the primary region and three in the paired region. The secondary copy can be read only once a failover has happened.
Related terms
- GZRS
Geo-zone-redundant storage. Writes go synchronously to at least three availability zones in the primary region, as ZRS does, and are later copied asynchronously to a secondary region that keeps LRS copies. With RA-GZRS that secondary can also be read.
- GZRS / RA-GZRS
Geo-zone-redundant storage combines zone-redundant copies in the primary region with locally redundant copies in a secondary region. The RA- variant lets you read from the secondary.
- RA-GRS
Geo-redundant storage with an extra read-only endpoint in the secondary region that can be read from without a failover.
- RA-GZRS
Geo-zone-redundant storage that also lets you read the secondary region's copy at any time, with no failover required. Microsoft suggests it where the highest availability and durability are wanted.
- Redundancy
So that hardware failures, datacentre outages or a regional disaster cannot destroy data, Azure Storage keeps multiple copies: only in the primary region with LRS and ZRS, or in a secondary region as well with GRS and GZRS.
- ZRS
Zone-redundant storage: data is written three times, each copy in a different availability zone of the same region, and nothing is replicated to a secondary region.