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.
Also called geo-zone-redundant storage.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains GZRS / RA-GZRS in context, with comparison tables and the common traps.
Terms in this definition
- 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.
- Zone-redundant
Distributed over every availability zone in a region, allowing it to withstand losing one zone; a StandardV2 NAT gateway is an example.
- region
A provider-defined grouping in VCF Automation of Supervisors that all share one NSX Local Manager; tenants consume its compute, storage and memory via quotas set per region.
- Secondary region
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.
- VARIANT
A type for semi-structured data like JSON whose structure isn't fixed, available from Databricks Runtime 15.4. It is preferred to storing JSON as strings but can't serve as a partition column.
- CRUD
Shorthand for create, read, update and delete, the four basic things you do with data. Data-plane roles in Azure Cosmos DB, for instance, authorise those operations on items.