Disaster recovery strategies in Azure - Step-by-Step Execution

Process Flow - Disaster recovery strategies

Disaster Occurs

↓

Detect Disaster

↓

Activate Recovery Plan

↓

Failover to Backup Site

↓

Restore Services

↓

Failback to Primary Site

↓

Resume Normal Operations

This flow shows how a disaster recovery strategy detects a disaster, activates a recovery plan, switches to backup resources, restores services, and then returns to normal operations.

Execution Sample

Azure

1. Detect disaster event
2. Trigger failover to backup region
3. Restore data from backup
4. Redirect traffic to backup
5. Monitor system health
6. Failback when primary is ready

This sequence outlines the key steps in an Azure disaster recovery process.

Process Table

Step	Action	Condition/Check	Result/State Change
1	Detect disaster event	Disaster detected?	Yes - proceed to failover
2	Trigger failover	Backup site available?	Failover initiated to backup region
3	Restore data	Backup data integrity?	Data restored successfully
4	Redirect traffic	Backup services running?	Traffic redirected to backup site
5	Monitor system	System stable?	Monitoring continues, no issues
6	Failback	Primary site ready?	Failback initiated to primary site
7	Resume operations	Primary site operational?	Normal operations resumed
8	End	All systems normal	Disaster recovery complete

💡 Disaster recovery completes when primary site is operational and normal operations resume.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
DisasterDetected	False	True	True	True	True	True	True	False
FailoverActive	False	False	True	True	True	True	False	False
DataRestored	False	False	False	True	True	True	True	True
TrafficRedirected	False	False	False	False	True	True	True	True
SystemStable	True	True	True	True	True	True	True	True
FailbackActive	False	False	False	False	False	False	True	False
OperationsNormal	True	False	False	False	False	False	False	True

Key Moments - 3 Insights

Why do we redirect traffic only after data is restored?

Traffic is redirected after data restoration to ensure users access consistent and complete data, as shown in step 4 of the execution_table.

What happens if the backup site is not available during failover?

Failover cannot proceed without a backup site, so the recovery plan must include alternate sites or manual intervention, as implied in step 2.

Why do we failback only when the primary site is fully operational?

Failback occurs only when the primary site is ready to avoid service disruption, as indicated in step 6 and 7.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is traffic redirected to the backup site?

A Step 4

B Step 2

C Step 6

D Step 1

💡 Hint

Check the 'Action' column for 'Redirect traffic' in the execution_table.

According to variable_tracker, what is the value of FailoverActive after Step 3?

A Undefined

B False

C True

D Null

💡 Hint

Look at the 'FailoverActive' row under 'After Step 3' in variable_tracker.

If the primary site is not ready, what happens to the failback process according to the execution_table?

A Failback proceeds anyway

B Failback is delayed

C Traffic is redirected to primary site

D Disaster recovery ends

💡 Hint

Refer to step 6 in execution_table where 'Primary site ready?' condition controls failback.

Concept Snapshot

Disaster recovery in Azure:
1. Detect disaster event.
2. Failover to backup region.
3. Restore data and redirect traffic.
4. Monitor system health.
5. Failback when primary is ready.
Ensures minimal downtime and data loss.

Full Transcript

Disaster recovery strategies in Azure involve detecting a disaster, activating a recovery plan, failing over to a backup site, restoring data, redirecting traffic, monitoring system health, and finally failing back to the primary site when it is ready. This process ensures services continue with minimal interruption and data integrity is maintained. The execution flow starts with disaster detection and ends when normal operations resume. Variables like FailoverActive and OperationsNormal track the system state through each step. Key moments include understanding why traffic redirection waits for data restoration and why failback requires the primary site to be fully operational.

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