QuestionQ74

VerifiedPlan and configure a high availability and disaster recovery (HA/DR) environment

You have an Azure subscription that uses a domain named contoso.com.

You have two Azure VMs named DBServer1 and DBServer2, each hosting a default SQL Server instance. DBServer1 is located in the East US Azure region and contains a database named DatabaseA. DBServer2 is located in the West US Azure region.

DBServer1 experiences a high volume of data changes and has low-latency requirements for data writes.

You need to configure a new availability group for DatabaseA, with the secondary replica residing on DBServer2.

What should you do?

Explanation

SQL Server Always On Availability Group (database mirroring) endpoints listen on TCP port 5022 by default, not 445, so the endpoint must be configured as TCP://DBServer1.contoso.com:5022 and TCP://DBServer2.contoso.com:5022. Because DBServer1 and DBServer2 are in different, geographically distant Azure regions (East US and West US), the network latency between them is too high to support synchronous-commit mode without degrading write performance, since synchronous-commit requires the primary to wait for the secondary to harden the log before committing. Given DatabaseA's high volume of changes and low write-latency requirement, the availability mode should be set to Asynchronous, which lets the primary commit transactions without waiting on the secondary.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!