Storage redundancy (LRS, ZRS, GRS) in Azure - Step-by-Step Execution

Process Flow - Storage redundancy (LRS, ZRS, GRS)

Start: Choose Redundancy Type

↓

Use LRS: Local Redundancy

↓

Use ZRS: Zone Redundancy

↓

Data replicated across zones

This flow shows how to pick storage redundancy: LRS keeps copies in one data center, ZRS spreads copies across zones in one region, and GRS replicates data to another region.

Execution Sample

Azure

CreateStorageAccount(redundancy="LRS")
CreateStorageAccount(redundancy="ZRS")
CreateStorageAccount(redundancy="GRS")

Creates storage accounts with different redundancy options to protect data.

Process Table

Step	Redundancy Type	Data Location	Replication Scope	Resulting Data Copies
1	LRS	Single data center	Within one data center	3 copies in same data center
2	ZRS	Multiple zones in one region	Across zones in one region	3 copies across zones
3	GRS	Primary region + secondary region	Across regions	3 copies in primary + 3 copies in secondary
4	End	-	-	Replication ensures data durability and availability

💡 Replication setup completes based on chosen redundancy type

Status Tracker

Variable	Start	After LRS	After ZRS	After GRS
Data Copies	0	3 copies in one data center	3 copies across zones	3 copies primary + 3 copies secondary
Replication Scope	None	Within one data center	Across zones in one region	Across regions
Data Location	None	Single data center	Multiple zones in one region	Primary + secondary region

Key Moments - 3 Insights

Why does LRS only keep copies in one data center?

LRS replicates data three times within the same data center to protect against hardware failures but not against data center-wide issues, as shown in step 1 of the execution_table.

How is ZRS different from LRS in terms of data location?

ZRS spreads copies across multiple zones in the same region to protect against zone failures, unlike LRS which keeps all copies in one data center (see step 2 in execution_table).

What extra protection does GRS provide compared to ZRS?

GRS replicates data to a secondary region far away, protecting against regional disasters, as shown in step 3 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, how many copies does LRS keep and where?

A 3 copies in primary and 3 in secondary region

B 3 copies in one data center

C 3 copies across zones

D 1 copy only

💡 Hint

Check row 1 under 'Resulting Data Copies' in execution_table

At which step does data get replicated across regions?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at 'Replication Scope' column in execution_table for cross-region replication

If you want to protect data from zone failures but keep it in one region, which redundancy should you choose?

A ZRS

B LRS

C GRS

D No redundancy

💡 Hint

Refer to 'Data Location' and 'Replication Scope' in execution_table step 2

Concept Snapshot

Storage redundancy protects data by making copies.
LRS: 3 copies in one data center.
ZRS: 3 copies across zones in one region.
GRS: 3 copies in primary + 3 in secondary region.
Choose based on needed protection level and cost.

Full Transcript

Storage redundancy means making copies of your data to keep it safe. Local Redundancy (LRS) keeps three copies in the same data center, protecting against hardware failure but not data center failure. Zone Redundancy (ZRS) spreads copies across different zones in one region, protecting against zone failures. Geo Redundancy (GRS) copies data to a different region, protecting against regional disasters. When creating a storage account, you pick one of these options based on how much protection you want. The execution table shows how many copies are made and where for each type. Variables like data copies and replication scope change depending on the redundancy chosen. Understanding these helps you pick the right option for your needs.