Examkin

Soru

Zorluk: ZorDesign Azure Site Recovery Solutions

An enterprise is designing a disaster recovery (DR) solution from the East US region to the West US region for an e-commerce application. The application consists of the following three tiers:

* Web Tier: Two virtual machines (VMs) with a write churn of 2 MB/s2\text{ MB/s} per VM.
* Application Tier: Two VMs with a write churn of 5 MB/s5\text{ MB/s} per VM.
* Database Tier: One SQL Server VM (`db-prod-01`) with three Premium SSD disks:
* OS disk: 1 MB/s1\text{ MB/s} write churn.
* Data disk: 6 MB/s6\text{ MB/s} write churn.
* Transaction log disk: 22 MB/s22\text{ MB/s} write churn.

The business requires a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 1 hour.

Which disaster recovery design should you recommend to meet the requirements?

  1. Replicate the web and application tier VMs using Azure Site Recovery. Configure SQL Server Always On Availability Groups to replicate the database tier to a target VM in the West US region.Cevap
  2. B
    Replicate all VMs, including the database VM, to the West US region using Azure Site Recovery with the standard protection tier.
  3. C
    Replicate all VMs, including the database VM, to the West US region using Azure Site Recovery with the high-churn protection tier.
  4. D
    Configure Azure Backup with Cross-Region Restore (CRR) to replicate all virtual machines to a Recovery Services vault in the West US region.

Cevap

Replicate the web and application tier VMs using Azure Site Recovery. Configure SQL Server Always On Availability Groups to replicate the database tier to a target VM in the West US region.
The correct design uses Azure Site Recovery for the web and application tier VMs because their write churn rates (2 MB/s2\text{ MB/s} and 5 MB/s5\text{ MB/s} respectively) are well within the capabilities of Azure Site Recovery. For the database tier, the transaction log disk has a write churn rate of 22 MB/s22\text{ MB/s}, which exceeds both the standard replication limit (10 MB/s10\text{ MB/s}) and the high-churn replication limit (20 MB/s20\text{ MB/s}) per disk in Azure Site Recovery. Therefore, database-native replication using SQL Server Always On Availability Groups must be recommended to handle the high churn rate while achieving the target RPO and RTO.

Adım Adım Çözüm

1
Analyze the write churn metrics for all disks in the application tiers.
Web tier VMs (2 MB/s2\text{ MB/s}) and application tier VMs (5 MB/s5\text{ MB/s}) are within standard limits. The database VM has a transaction log disk with 22 MB/s22\text{ MB/s} write churn.
To determine which Azure Site Recovery limits might be exceeded by the workload.
2
Compare the database transaction log disk churn (22 MB/s22\text{ MB/s}) against Azure Site Recovery limits.
The churn rate exceeds both the standard (10 MB/s10\text{ MB/s}) and high-churn (20 MB/s20\text{ MB/s}) replication limits per disk for Azure Site Recovery.
To evaluate if Azure Site Recovery can replicate the database virtual machine.
3
Select the appropriate replication mechanism for the database tier and the other tiers.
Recommend Azure Site Recovery for the web and application tiers, and SQL Server Always On Availability Groups (database-native replication) for the database tier.
To ensure that all workloads are replicated successfully within their technical limits and meet the 15-minute RPO and 1-hour RTO.

Anahtar Kavram

Azure Site Recovery disk write churn limitations and database-native replication alternatives.
Bu soruyu puanla

Konular

Design Azure Site Recovery Solutions

Bu konudan daha fazla soru