Disaster recovery strategies in Azure - Mini Project: Build & Apply

Disaster Recovery Strategies with Azure

📖 Scenario: You are working as a cloud engineer for a company that wants to protect its critical data and applications from disasters. You will use Azure services to set up a simple disaster recovery strategy.

🎯 Goal: Build an Azure disaster recovery setup by creating a resource group, configuring a storage account with geo-redundant storage, and enabling recovery services vault for backup.

📋 What You'll Learn

Create an Azure resource group named DRResourceGroup in the eastus region.

Create a storage account named drstorageacct with GeoRedundantStorage replication in the DRResourceGroup.

Create a Recovery Services vault named DRVault in the eastus region within DRResourceGroup.

Enable backup protection for the storage account using the Recovery Services vault.

💡 Why This Matters

🌍 Real World

Companies use disaster recovery strategies to keep their data safe and services running during unexpected failures or disasters.

💼 Career

Cloud engineers and administrators must know how to configure disaster recovery to meet business continuity requirements.

1

Create the Azure resource group

Write an Azure CLI command to create a resource group named DRResourceGroup in the eastus region.

Azure

# Your Azure CLI command here

Hint

Use az group create with --name and --location options.

2

Create a storage account with geo-redundant storage

Write an Azure CLI command to create a storage account named drstorageacct in the resource group DRResourceGroup with GeoRedundantStorage replication.

Azure

az group create --name DRResourceGroup --location eastus
# Your Azure CLI command to create storage account here

Hint

Use az storage account create with --sku Standard_GRS for geo-redundant storage.

3

Create a Recovery Services vault

Write an Azure CLI command to create a Recovery Services vault named DRVault in the eastus region within the resource group DRResourceGroup.

Azure

az group create --name DRResourceGroup --location eastus
az storage account create --name drstorageacct --resource-group DRResourceGroup --location eastus --sku Standard_GRS
# Your Azure CLI command to create Recovery Services vault here

Hint

Use az backup vault create with the correct resource group, vault name, and location.

4

Enable backup protection for the storage account

Write an Azure CLI command to enable backup protection for the storage account drstorageacct using the Recovery Services vault DRVault in the resource group DRResourceGroup.

Azure

az group create --name DRResourceGroup --location eastus
az storage account create --name drstorageacct --resource-group DRResourceGroup --location eastus --sku Standard_GRS
az backup vault create --resource-group DRResourceGroup --name DRVault --location eastus
# Your Azure CLI command to enable backup protection here

Hint

Use az backup protection enable-for-azurefileshare with the correct resource group, vault name, and storage account.

Practice

1. What is the main purpose of a disaster recovery strategy in Azure?

easy

A. To keep cloud services safe and running during failures

B. To reduce the cost of cloud services

C. To increase the speed of the internet connection

D. To create new cloud services automatically

Solution

1. Step 1: Understand disaster recovery goals

   Disaster recovery aims to keep services available and safe during unexpected problems.

2. Step 2: Identify the main purpose in Azure context

   Azure disaster recovery focuses on maintaining service continuity and data protection.

3. Final Answer:

   To keep cloud services safe and running during failures -> Option A

4. Quick Check:

   Disaster recovery = keep services running [OK]

Hint: Disaster recovery means keeping services running during problems [OK]

Common Mistakes:

• Confusing disaster recovery with cost saving
• Thinking it improves internet speed
• Assuming it creates new services automatically

2. Which Azure service is used to organize backups and failover plans for disaster recovery?

easy

A. Azure Virtual Machines

B. Azure Recovery Services Vault

C. Azure Blob Storage

D. Azure Functions

Solution

1. Step 1: Identify the service for backup and failover

   Azure Recovery Services Vault is designed to manage backups and disaster recovery plans.

2. Step 2: Compare with other services

   Virtual Machines run workloads, Blob Storage stores data, Functions run code, but only Recovery Services Vault organizes recovery.

3. Final Answer:

   Azure Recovery Services Vault -> Option B

4. Quick Check:

   Recovery Vault = backup and failover organizer [OK]

Hint: Recovery Services Vault manages backups and failover plans [OK]

Common Mistakes:

• Choosing Virtual Machines as backup organizer
• Confusing Blob Storage with recovery management
• Selecting Functions for disaster recovery

3. Consider this Azure CLI command snippet for disaster recovery setup:

az backup vault create --resource-group MyGroup --name MyVault
az backup protection enable-for-vm --vault-name MyVault --vm MyVM --policy-name DefaultPolicy

What is the expected result after running these commands?

medium

A. The backup policy DefaultPolicy is deleted

B. A virtual machine named MyVault is created and backed up

C. A backup vault named MyVault is created and MyVM is protected by backup

D. The resource group MyGroup is deleted

Solution

1. Step 1: Analyze the first command

   The first command creates a backup vault named MyVault in resource group MyGroup.

2. Step 2: Analyze the second command

   The second command enables backup protection for the VM named MyVM using the DefaultPolicy in the vault MyVault.

3. Final Answer:

   A backup vault named MyVault is created and MyVM is protected by backup -> Option C

4. Quick Check:

   Vault created + VM backup enabled = A backup vault named MyVault is created and MyVM is protected by backup [OK]

Hint: First create vault, then enable VM backup in that vault [OK]

Common Mistakes:

• Thinking a VM named MyVault is created
• Assuming resource group is deleted
• Believing backup policy is deleted

4. You wrote this Azure Recovery Services Vault configuration but backups are not starting:

resource "azurerm_recovery_services_vault" "example" {
  name                = "example-vault"
  location            = "eastus"
  resource_group_name = "example-rg"
  sku                 = "Standard"
}

resource "azurerm_backup_policy_vm" "example_policy" {
  name                = "example-policy"
  resource_group_name = "example-rg"
  recovery_vault_name = azurerm_recovery_services_vault.example.name

  backup {
    frequency = "Daily"
    time      = "02:00"
    timezone  = "UTC"
  }

  retention_daily {
    count = 7
  }
}

What is the likely error preventing backups from starting?

medium

A. The backup frequency must be hourly, not daily

B. The vault SKU must be Premium, not Standard

C. The resource group name is incorrect

D. The backup policy is missing the 'timezone' setting

Solution

1. Step 1: Review backup policy requirements

   Azure backup policies require a timezone setting to schedule backups correctly.

2. Step 2: Check configuration details

   The policy lacks a timezone field, which can prevent backups from starting.

3. Final Answer:

   The backup policy is missing the 'timezone' setting -> Option D

4. Quick Check:

   Missing timezone in policy stops backups [OK]

Hint: Backup policies need timezone to schedule backups [OK]

Common Mistakes:

• Assuming SKU Standard is invalid
• Thinking resource group name is wrong without evidence
• Believing frequency must be hourly

5. You want to design a disaster recovery plan in Azure that automatically fails over your web app to a secondary region if the primary region goes down. Which combination of Azure services and features should you use?

hard

A. Azure Traffic Manager with Recovery Services Vault and automated failover runbooks

B. Azure Blob Storage with manual backup and restore scripts

C. Azure Functions with local backups only

D. Azure Virtual Machines without any backup or failover setup

Solution

1. Step 1: Identify failover automation tools

   Azure Traffic Manager can route traffic to a secondary region automatically when the primary fails.

2. Step 2: Combine with backup and automation

   Recovery Services Vault stores backups, and runbooks automate failover processes for quick recovery.

3. Step 3: Evaluate other options

   Blob Storage and Functions alone do not provide automated failover; VMs without backup lack recovery.

4. Final Answer:

   Azure Traffic Manager with Recovery Services Vault and automated failover runbooks -> Option A

5. Quick Check:

   Traffic Manager + Recovery Vault + automation = automated failover [OK]

Hint: Use Traffic Manager plus Recovery Vault and automation for failover [OK]

Common Mistakes:

• Choosing manual backup without automation
• Using Functions without failover setup
• Ignoring backup and failover in VM-only option