Share via

Azure SQL Server Always on AG with multi-sibnets

Venkata Yeleswarapu 0 Reputation points
2024-04-22T04:09:32.97+00:00

We are planning to set-up always on AG in azure which SQL server 2016 on WS2016. As perdocumentation, we want to avoid load balancer and go with multi-subnet. The question here is, does the 2 azure VM's/nodes must be in different zones in a region ? We want to have both the VM's in same zone under same virtual network but different subnets. Does this configuation work ?

Azure SQL Database
Windows for business | Windows Server | Storage high availability | Clustering and high availability
SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories


1 answer

Sort by: Most helpful
  1. PhilBarry 5 Reputation points Microsoft Employee
    2024-04-23T11:02:25.1066667+00:00

    You don't have to use different Availability Zones, but if you are not then you should use an Availability Set to ensure that the SQL VMs are not placed on the same Update or Fault Domains. It is documented in https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial-multi-subnet?view=azuresql#create-sql-server-vms:

    Availability - Availability Zones For the highest level of redundancy, resiliency and availability deploy the VMs within separate Availability Zones. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters with independent power, cooling, and networking. For Azure regions that do not support Availability Zones yet, use Availability Sets instead. Place all the VMs within the same Availability Set.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.