Storage redundancy (LRS, ZRS, GRS) in Azure - Time & Space Complexity

Time Complexity: Storage redundancy (LRS, ZRS, GRS)

O(n)

Understanding Time Complexity

When storing data in the cloud, redundancy means keeping extra copies to stay safe.

We want to know how the work grows when more copies are made automatically.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Create storage account with redundancy
az storage account create --name mystorage --resource-group mygroup --location eastus --sku Standard_LRS

// Create container
az storage container create --account-name mystorage --name mycontainer

// Upload a file to storage
az storage blob upload --account-name mystorage --container-name mycontainer --name file.txt --file ./file.txt

// Repeat upload for multiple files
for file in files; do
  az storage blob upload --account-name mystorage --container-name mycontainer --name "$file" --file "./$file"
done

This sequence creates a storage account with local redundancy and uploads files to it.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Uploading each file to the storage account.
• How many times: Once per file uploaded.
• Redundancy copies: LRS keeps 3 copies locally, ZRS keeps 3 copies across zones, GRS replicates to another region asynchronously.
• Dominant operation: Data replication behind the scenes for each upload.

How Execution Grows With Input

Each file upload triggers copying data multiple times depending on redundancy type.

Input Size (n files)	Approx. Data Copies Made
10	30 (LRS), 30 (ZRS), 60 (GRS)
100	300 (LRS), 300 (ZRS), 600 (GRS)
1000	3000 (LRS), 3000 (ZRS), 6000 (GRS)

Pattern observation: The number of copies grows linearly with the number of files uploaded.

Final Time Complexity

Time Complexity: O(n)

This means the work to store data grows directly with how many files you upload.

Common Mistake

[X] Wrong: "Adding redundancy does not affect upload time or work done."

[OK] Correct: More copies mean more data is written behind the scenes, so work and time increase with redundancy.

Interview Connect

Understanding how redundancy affects work helps you design storage solutions that balance safety and speed.

Self-Check

"What if we switch from LRS to GRS? How would the time complexity and data replication change?"

Practice

1. Which Azure storage redundancy option keeps copies of your data only within a single data center?

easy

A. Zone-Redundant Storage (ZRS)

B. Read-Access Geo-Redundant Storage (RA-GRS)

C. Geo-Redundant Storage (GRS)

D. Locally Redundant Storage (LRS)

Solution

1. Step 1: Understand LRS scope

   LRS keeps three copies of data within a single data center to protect against hardware failures.

2. Step 2: Compare with other options

   ZRS replicates data across zones, GRS replicates across regions, so they are broader than LRS.

3. Final Answer:

   Locally Redundant Storage (LRS) -> Option D

4. Quick Check:

   Single data center copies = LRS [OK]

Hint: LRS = copies inside one data center only [OK]

Common Mistakes:

• Confusing ZRS with LRS because both mention redundancy
• Thinking GRS is inside one data center
• Mixing RA-GRS with LRS

2. Which redundancy option is correctly written in Azure Storage configuration syntax?

easy

A. "redundancy": "ZRS"

B. "redundancy": "LZR"

C. "redundancy": "GRZ"

D. "redundancy": "RAGRS"

Solution

1. Step 1: Identify valid redundancy codes

   Azure uses LRS, ZRS, GRS, and RA-GRS as standard redundancy codes.

2. Step 2: Check each option

   "redundancy": "ZRS" uses "ZRS" which is valid. Others have incorrect or invalid codes.

3. Final Answer:

   "redundancy": "ZRS" -> Option A

4. Quick Check:

   Valid Azure redundancy code = ZRS [OK]

Hint: Use exact Azure codes: LRS, ZRS, GRS, RA-GRS [OK]

Common Mistakes:

• Typos in redundancy codes like LZR or GRZ
• Using unsupported codes
• Confusing RA-GRS abbreviation

3. If you configure Azure Storage with redundancy: "GRS", what happens when the primary region fails?

medium

A. Data is available only if zones in the primary region are healthy

B. Data is lost because copies are only in one data center

C. Data is available from a secondary region copy

D. Data is immediately deleted from all regions

Solution

1. Step 1: Understand GRS behavior

   GRS replicates data asynchronously to a secondary region for disaster recovery.

2. Step 2: Effect of primary region failure

   If the primary region fails, data can be accessed from the secondary region copy.

3. Final Answer:

   Data is available from a secondary region copy -> Option C

4. Quick Check:

   GRS = secondary region copy available [OK]

Hint: GRS keeps copies in another region for failover [OK]

Common Mistakes:

• Thinking GRS only copies inside one data center
• Confusing zone redundancy with region redundancy
• Assuming data is lost on primary failure

4. You set Azure Storage redundancy to "ZRS" but notice data is not replicated across zones. What is the likely cause?

medium

A. You must enable GRS for zone replication

B. ZRS is not supported in the selected region

C. LRS setting overrides ZRS automatically

D. Data replication only happens manually with ZRS

Solution

1. Step 1: Check ZRS regional support

   ZRS requires the region to support availability zones; some regions do not support ZRS.

2. Step 2: Understand replication behavior

   If the region lacks zone support, ZRS cannot replicate across zones, causing no zone replication.

3. Final Answer:

   ZRS is not supported in the selected region -> Option B

4. Quick Check:

   ZRS needs region with zones [OK]

Hint: ZRS needs region with zones enabled [OK]

Common Mistakes:

• Confusing GRS with ZRS replication
• Assuming LRS overrides ZRS
• Thinking ZRS replication is manual

5. A company wants to minimize cost but needs protection against data center failure and regional disaster. Which Azure storage redundancy option should they choose?

hard

A. Geo-Redundant Storage (GRS)

B. Zone-Redundant Storage (ZRS)

C. Read-Access Geo-Redundant Storage (RA-GRS)

D. Locally Redundant Storage (LRS)

Solution

1. Step 1: Analyze protection needs

   Protection against data center failure requires zone or local redundancy; regional disaster needs geo-redundancy.

2. Step 2: Balance cost and protection

   LRS is cheapest but no regional protection; ZRS protects zones but not regions; GRS protects regions at moderate cost; RA-GRS adds read access but costs more.

3. Final Answer:

   Geo-Redundant Storage (GRS) -> Option A

4. Quick Check:

   Regional disaster + cost balance = GRS [OK]

Hint: GRS balances cost and regional disaster protection [OK]

Common Mistakes:

• Choosing LRS which lacks regional protection
• Picking RA-GRS which costs more than needed
• Assuming ZRS protects against regional disasters