Question

Difficulty: MediumDesign Azure Site Recovery Solutions

An organization is designing a disaster recovery (DR) solution from the East US region to the West US region for a database workload hosted on an Azure virtual machine named VM2. The disaster recovery requirements specify a Recovery Point Objective (RPO) of 1515 minutes and a Recovery Time Objective (RTO) of 11 hour.

VM2 is configured with three Premium SSD v1 disks as detailed in the following table:

DiskContentWrite Churn
Disk 1Operating System2 MB/s2\text{ MB/s}
Disk 2User Databases12 MB/s12\text{ MB/s}
Disk 3TempDB25 MB/s25\text{ MB/s}

Which two actions should you include in the Azure Site Recovery (ASR) design to ensure replication is successful and meets the workload requirements?

  1. Configure Azure Site Recovery to exclude the TempDB disk (Disk 3) from replication.Answer
  2. Configure the replication policy for VM2 to use the High Churn tier.Answer
  3. C
    Replicate all three disks using the default standard replication policy.
  4. D
    Replicate Disk 3 by changing its storage tier to Standard HDD.

Answer

To design a successful replication strategy using Azure Site Recovery, you must configure Azure Site Recovery to exclude the TempDB disk (Disk 3) from replication and configure the replication policy for the virtual machine to use the High Churn tier.
Excluding the TempDB disk (Disk 3) from replication is the correct approach because TempDB contains temporary data that is recreated when SQL Server starts, and its write churn of 25 MB/s25\text{ MB/s} exceeds the maximum supported limit (20 MB/s20\text{ MB/s}) for Azure Site Recovery. Enabling the High Churn replication policy is also required because Disk 2 has a write churn of 12 MB/s12\text{ MB/s}, which exceeds the standard limit of 10 MB/s10\text{ MB/s} but is supported under the High Churn policy tier.

Step-by-Step Solution

1
Analyze the write churn for each disk against Azure Site Recovery limits.
Disk 1 (2 MB/s2\text{ MB/s}) is within standard limits. Disk 2 (12 MB/s12\text{ MB/s}) exceeds the standard limit of 10 MB/s10\text{ MB/s} but is within the high churn limit of 20 MB/s20\text{ MB/s}. Disk 3 (25 MB/s25\text{ MB/s}) exceeds the high churn limit of 20 MB/s20\text{ MB/s}.
This identifies which disks require special handling or policies due to exceeding replication thresholds.
2
Determine if any disk contents can be excluded from replication.
Disk 3 contains TempDB, which is non-persistent and recreated when the SQL Server service starts on the failover VM.
Excluding TempDB reduces replication bandwidth and removes a disk that violates the absolute ASR write churn limits.
3
Select the appropriate replication policy for the remaining disks.
Since Disk 2 has a churn rate of 12 MB/s12\text{ MB/s} (exceeding standard limits), configuring the replication policy to use the High Churn tier is necessary to successfully replicate the VM.
Assigning the High Churn policy ensures that Disk 2 can replicate to the target region without failing due to rate limits.

Key Concept

Azure Site Recovery VM replication limits, High Churn policy support, and disk exclusion strategies for temporary data workloads.
Rate this question