Storage redundancy (LRS, ZRS, GRS) in Azure - Mini Project: Build & Apply

Storage redundancy (LRS, ZRS, GRS)

📖 Scenario: You are setting up Azure Storage accounts for a company that wants to protect their data against hardware failures and regional outages. You will create storage accounts with different redundancy options to understand how data is replicated and protected.

🎯 Goal: Create three Azure Storage accounts with different redundancy settings: Locally-redundant storage (LRS), Zone-redundant storage (ZRS), and Geo-redundant storage (GRS). This will help you see how Azure keeps data safe in different ways.

📋 What You'll Learn

Create a storage account named storageLRS with redundancy set to LRS

Create a storage account named storageZRS with redundancy set to ZRS

Create a storage account named storageGRS with redundancy set to GRS

Use the Azure CLI syntax for storage account creation

Use the resource group myResourceGroup and location eastus

💡 Why This Matters

🌍 Real World

Companies use storage redundancy to protect their data from hardware failures and disasters. Understanding how to configure redundancy helps ensure data availability and durability.

💼 Career

Cloud engineers and administrators often create and manage storage accounts with appropriate redundancy to meet business continuity and disaster recovery requirements.

1

Create a storage account with Locally-redundant storage (LRS)

Use the Azure CLI command az storage account create to create a storage account named storageLRS in the resource group myResourceGroup and location eastus. Set the redundancy option to LRS using the --sku Standard_LRS parameter.

Azure

# Your code here

Hint

Use az storage account create with --sku Standard_LRS to specify LRS redundancy.

2

Create a storage account with Zone-redundant storage (ZRS)

Add a new Azure CLI command to create a storage account named storageZRS in the resource group myResourceGroup and location eastus. Set the redundancy option to ZRS using the --sku Standard_ZRS parameter.

Azure

az storage account create --name storageLRS --resource-group myResourceGroup --location eastus --sku Standard_LRS
# Your code here

Hint

Use --sku Standard_ZRS to specify Zone-redundant storage.

3

Create a storage account with Geo-redundant storage (GRS)

Add another Azure CLI command to create a storage account named storageGRS in the resource group myResourceGroup and location eastus. Set the redundancy option to GRS using the --sku Standard_GRS parameter.

Azure

az storage account create --name storageLRS --resource-group myResourceGroup --location eastus --sku Standard_LRS
az storage account create --name storageZRS --resource-group myResourceGroup --location eastus --sku Standard_ZRS
# Your code here

Hint

Use --sku Standard_GRS to specify Geo-redundant storage.

4

Verify storage accounts and their redundancy

Add Azure CLI commands to list all storage accounts in the resource group myResourceGroup and show their redundancy type using the az storage account show command with the --query sku.name option for each account: storageLRS, storageZRS, and storageGRS.

Azure

az storage account create --name storageLRS --resource-group myResourceGroup --location eastus --sku Standard_LRS
az storage account create --name storageZRS --resource-group myResourceGroup --location eastus --sku Standard_ZRS
az storage account create --name storageGRS --resource-group myResourceGroup --location eastus --sku Standard_GRS
# Your code here

Hint

Use az storage account show --name <accountName> --resource-group myResourceGroup --query sku.name to check redundancy.

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