Configure an availability group across Azure regions - SQL Server on Azure VMs

Applies to: SQL Server on Azure VM

This tutorial explains how to configure an Always On availability group replica for SQL Server on Azure virtual machines (VMs) in an Azure region that is remote to the primary replica. You can use this configuration for the purpose of disaster recovery (DR).

You can also use the steps in this article to extend an existing on-premises availability group to Azure.

This tutorial builds on the tutorial to manually deploy an availability group in a single subnet in a single region. Mentions of the local region in this article refer to the virtual machines and availability group already configured in the first region. The remote region is the new infrastructure that's being added in this tutorial.

Overview

The following image shows a common deployment of an availability group on Azure virtual machines:

In the deployment shown in the diagram, all virtual machines are in one Azure region. The availability group replicas can have synchronous commit with automatic failover on SQL-1 and SQL-2. To build this architecture, see the availability group template or tutorial.

This architecture is vulnerable to downtime if the Azure region becomes inaccessible. To overcome this vulnerability, add a replica in a different Azure region. The following diagram shows how the new architecture looks:

The diagram shows a new virtual machine called SQL-3. SQL-3 is in a different Azure region. It's added to the Windows Server failover cluster and can host an availability group replica.

The Azure region for SQL-3 has a new Azure load balancer. In this architecture, the replica in the remote region is normally configured with asynchronous commit availability mode and manual failover mode.

When availability group replicas are on Azure virtual machines in different Azure regions, you can connect the virtual networks by using virtual network peering or a site-to-site VPN gateway.

Create the network and subnet

Before you create a virtual network and subnet in a new region, decide on the address space, subnet network, cluster IP, and availability group listener IP addresses that you'll use for the remote region.

The following table lists details for the local (current) region and what will be set up in the new remote region.

Type	Local	Remote region
Address space	192.168.0.0/16	10.36.0.0/16
Subnet network	192.168.15.0/24	10.36.1.0/24
Cluster IP	192.168.15.200	10.36.1.200
Availability group listener IP	192.168.15.201	10.36.1.201

To create a virtual network and subnet in the new region in the Azure portal:

1. Go to your resource group in the Azure portal and select + Create.

2. Search for virtual network in the Marketplace search box, and then select the virtual network tile from Microsoft.

3. On the Create virtual network page, select Create. Then enter the following information on the Basics tab:

   1. Under Project details, for Subscription, select the appropriate Azure subscription. For Resource group, select the resource group that you created previously, such as SQL-HA-RG.
   2. Under Instance details, provide a name for your virtual network, such as remote_HAVNET. Then choose a new remote region.

   

4. On the IP addresses tab, select the ellipsis (...) next to + Add a subnet. Select Delete address space to remove the existing address space, if you need a different address range.

   

5. Select Add an IP address space to open the pane to create the address space that you need. This tutorial uses the address space of the remote region: 10.36.0.0/16. Select Add.

   

6. Select + Add a subnet, and then:

   1. Provide a value for the Subnet name, such as admin.

   2. Provide a unique subnet address range within the virtual network address space.

      For example, if your address range is 10.36.0.0/16, enter these values for the admin subnet: 10.36.1.0 for Starting address and /24 for Subnet size.

   3. Select Add to add your new subnet.

   

Connect the virtual networks in the two Azure regions

After you create the new virtual network and subnet, you're ready to connect the two regions so they can communicate with each other. There are two methods to do this:

• Connect virtual networks with virtual network peering by using the Azure portal (recommended)

  In some cases, you might have to use PowerShell to create the connection between virtual networks. For example, if you use different Azure accounts, you can't configure the connection in the portal. In this case, review Configure a network-to-network connection by using the Azure portal.

• Configure a site-to-site VPN gateway connection by using the Azure portal

This tutorial uses virtual network peering. To configure virtual network peering:

1. In the search box at the top of the Azure portal, type autoHAVNET, which is the virtual network in your local region. When autoHAVNET appears in the search results, select it.

2. Under Settings, select Peerings, and then select + Add.

   

3. Enter or select the following information, accept the defaults for the remaining settings, and then select Add.

   Setting	Value
   This virtual network
   Peering link name	Enter autoHAVNET-remote_HAVNET for the name of the peering from autoHAVNET to the remote virtual network.
   Remote virtual network
   Peering link name	Enter remote_HAVNET-autoHAVNET for the name of the peering from the remote virtual network to autoHAVNET.
   Subscription	Select your subscription for the remote virtual network.
   Virtual network	Select remote_HAVNET for the name of the remote virtual network. The remote virtual network can be in the same region of autoHAVNET or in a different region.

   

4. On the Peerings page, Peering status is Connected.

   

   If you don't see a Connected status, select the Refresh button.

Create a domain controller

A domain controller in the new region is necessary to provide authentication if the primary site is not available. To create the domain controller in the new region:

1. Return to the SQL-HA-RG resource group.
2. Select + Create.
3. Type Windows Server 2016 Datacenter, and then select the Windows Server 2016 Datacenter result.
4. In Windows Server 2016 Datacenter, verify that the deployment model is Resource Manager, and then select Create.

The following table shows the settings for the two machines:

Setting	Value
Name	Remote domain controller: ad-remote-dc
VM disk type	SSD
User name	DomainAdmin
Password	Contoso!0000
Subscription	Your subscription
Resource group	SQL-HA-RG
Location	Your location
Size	DS1_V2
Storage	Use managed disks: Yes
Virtual network	remote_HAVNET
Subnet	admin
Public IP address	Same name as the VM
Network security group	Same name as the VM
Diagnostics	Enabled
Diagnostics storage account	Automatically created

Azure creates the virtual machines.

Configure the domain controller

In the following steps, configure the ad-remote-dc machine as a domain controller for corp.contoso.com:

Set preferred DNS server address

The preferred DNS server address should not be updated directly within a VM, it should be edited from the Azure portal, or Powershell, or Azure CLI. The steps below are to make the change inside of the Azure portal:

1. Sign-in to the Azure portal.

2. In the search box at the top of the portal, enter Network interface. Select Network interfaces in the search results.

3. Select the network interface for the second domain controller that you want to view or change settings for from the list.

4. In Settings, select DNS servers.

5. Since this domain controller is not in the same virtual network as the primary domain controller select Custom and input the IP address of the primary domain controller, such as 192.168.15.4. The DNS server address you specify is assigned only to this network interface and overrides any DNS setting for the virtual network the network interface is assigned to.

6. Select Save.

7. Return to the virtual machine in the Azure portal and restart the VM. Once the virtual machine has restarted, you can join the VM to the domain.

Join the domain

Next, join the corp.contoso.com domain. To do so, follow these steps:

1. Remotely connect to the virtual machine using the BUILTIN\DomainAdmin account.
2. Open Server Manager, and select Local Server.
3. Select WORKGROUP.
4. In the Computer Name section, select Change.
5. Select the Domain checkbox and type corp.contoso.com in the text box. Select OK.
6. In the Windows Security popup dialog, specify the credentials for the default domain administrator account (CORP\DomainAdmin) and the password (Contoso!0000).
7. When you see the "Welcome to the corp.contoso.com domain" message, select OK.
8. Select Close, and then select Restart Now in the popup dialog.

Configure domain controller

Once your server has joined the domain, you can configure it as the second domain controller. To do so, follow these steps:

1. If you're not already connected, open an RDP session to your secondary domain controller, and open Server Manager Dashboard (which may be open by default).

2. Select the Add roles and features link on the dashboard.

   

3. Select Next until you get to the Server Roles section.

4. Select the Active Directory Domain Services and DNS Server roles. When you're prompted, add any additional features that are required by these roles.

5. After the features finish installing, return to the Server Manager dashboard.

6. Select the new AD DS option on the left-hand pane.

7. Select the More link on the yellow warning bar.

8. In the Action column of the All Server Task Details dialog, select Promote this server to a domain controller.

9. Under Deployment Configuration, select Add a domain controller to an existing domain.

10. Click Select.

11. Connect by using the administrator account (CORP.CONTOSO.COM\domainadmin) and password (Contoso!0000).

12. In Select a domain from the forest, choose your domain and then select OK.

13. In Domain Controller Options, use the default values and set a DSRM password.

    Note

    The DNS Options page might warn you that a delegation for this DNS server can't be created. You can ignore this warning in non-production environments.

14. Select Next until the dialog reaches the Prerequisites check. Then select Install.

After the server finishes the configuration changes, restart the server.

Create a SQL Server VM

After the domain controller restarts, the next step is to create a SQL Server virtual machine in the new region.

Before you proceed, consider the following design decisions:

• Storage: Azure managed disks

  For the virtual machine storage, use Azure managed disks. We recommend managed disks for SQL Server virtual machines. Managed disks handle storage behind the scenes. In addition, when virtual machines with managed disks are in the same availability set, Azure distributes the storage resources to provide appropriate redundancy.

  For more information, see Introduction to Azure managed disks. For specifics about managed disks in an availability set, see Use managed disks for VMs in an availability set.

• Network: Private IP addresses in production

  For the virtual machines, this tutorial uses public IP addresses. A public IP address enables remote connection directly to the virtual machine over the internet and makes configuration steps easier. In production environments, we recommend only private IP addresses. Private IP addresses reduce the vulnerability footprint of the SQL Server VM.

• Network: Single NIC per server

  Use a single network interface card (NIC) per server (cluster node) and a single subnet. Azure networking has physical redundancy, which makes additional NICs and subnets unnecessary on an Azure VM guest cluster. The cluster validation report will warn you that the nodes are reachable on only a single network. You can ignore this warning on Azure VM guest failover clusters.

Create and configure the SQL Server VM

To create the SQL Server VM, go back to the SQL-HA-RG resource group, and then select Add. Search for the appropriate gallery item, select Virtual Machine, and then select From Gallery. Use the information in the following table to help you create the VMs:

Page	Setting
Select the appropriate gallery item	SQL Server 2016 SP2 Enterprise on Windows Server 2016
Virtual machine configuration: Basics	Name = sqlserver-2 User Name = DomainAdmin Password = Contoso!0000 Subscription = Your subscription Resource group = SQL-HA-RG Location = Your remote region
Virtual machine configuration: Size	Size = DS2_V2 (2 vCPUs, 7 GB) The size must support SSD storage (premium disk support).
Virtual machine configuration: Settings	Storage: Use managed disks Virtual network = remote-HAVNET Subnet = admin (10.36.1.0/24) Public IP address = Automatically generated Network security group = None Monitoring Diagnostics = Enabled Diagnostics storage account = Use an automatically generated storage account
Virtual machine configuration: SQL Server settings	SQL connectivity = Private (within Virtual Network) Port = 1433 SQL Authentication = Disabled Storage configuration = General Automated patching = Sunday at 2:00 Automated backup = Disabled Azure Key Vault integration = Disabled

After the VM is fully provisioned, you need to join it to the corp.contoso.com domain and grant CORP\Install administrative rights to the machines.

Join the server to the domain

To join the VM to corp.contoso.com, use the following steps for the SQL Server VM:

1. Remotely connect to the virtual machine by using BUILTIN\DomainAdmin.
2. In Server Manager, select Local Server.
3. Select the WORKGROUP link.
4. In the Computer Name section, select Change.
5. Select the Domain check box, and enter corp.contoso.com in the text box. Then select OK.
6. In the Windows Security pop-up dialog, specify the credentials for the default domain administrator account (CORP\DomainAdmin) and the password (Contoso!0000).
7. When you see the "Welcome to the corp.contoso.com domain" message, select OK.
8. Select Close, and then select Restart Now in the pop-up dialog.

Add accounts

The next task is to add the installation account as an administrator on the SQL Server VM, and then grant permission to that account and to local accounts within SQL Server. You can then update the SQL Server service account.

Add the CORP\Install user as an administrator on each cluster VM

After the SQL Server virtual machine restarts as a member of the domain, add CORP\Install as a member of the local administrators group:

1. Wait until the VM is restarted, and then open the RDP file again from the primary domain controller. Sign in to sqlserver-2 by using the CORP\DomainAdmin account.

   Tip

   In earlier steps, you were using the BUILTIN administrator account. Now that the server is in the domain, make sure that you sign in with the domain administrator account. In your RDP session, specify DOMAIN\username.

2. In Server Manager, select Tools, and then select Computer Management.

3. In the Computer Management window, expand Local Users and Groups, and then select Groups.

4. Double-click the Administrators group.

5. In the Administrator Properties dialog, select the Add button.

6. Enter the user as CORP\Install, and then select OK.

7. Select OK to close the Administrator Properties dialog.

Create a sign-in on each SQL Server VM for the installation account

Use the installation account (CORP\Install) to configure the availability group. This account needs to be a member of the sysadmin fixed server role on each SQL Server VM. The following steps create a sign-in for the installation account. Complete them on both SQL Server VMs.

1. Connect to the server through RDP by using the <MachineName>\DomainAdmin account.

2. Open SQL Server Management Studio and connect to the local instance of SQL Server.

3. In Object Explorer, select Security.

4. Right-click Logins. Select New Login.

5. In Login - New, select Search.

6. Select Locations.

7. Enter the domain administrator's network credentials. Use the installation account (CORP\Install).

8. Set the sign-in to be a member of the sysadmin fixed server role.

9. Select OK.

Configure system account permissions

To create a system account and grant appropriate permissions, complete the following steps on each SQL Server instance:

1. Use the following script to create an account for [NT AUTHORITY\SYSTEM]:

   USE [master]
   GO
   CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS WITH DEFAULT_DATABASE=[master]
   GO 
   

2. Grant the following permissions to [NT AUTHORITY\SYSTEM]:

   • ALTER ANY AVAILABILITY GROUP
   • CONNECT SQL
   • VIEW SERVER STATE

   The following script grants these permissions:

   GRANT ALTER ANY AVAILABILITY GROUP TO [NT AUTHORITY\SYSTEM]
   GO
   GRANT CONNECT SQL TO [NT AUTHORITY\SYSTEM]
   GO
   GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM]
   GO 
   

Set the SQL Server service accounts

On each SQL Server VM, complete the following steps to set the SQL Server service account. Use the accounts that you created when you configured the domain accounts.

1. Open SQL Server Configuration Manager.
2. Right-click the SQL Server service, and then select Properties.
3. Set the account and password.

For SQL Server availability groups, each SQL Server VM needs to run as a domain account.

Create an Azure load balancer

A load balancer is required in the remote region to support the SQL Server availability group. The load balancer holds the IP addresses for the availability group listeners and the Windows Server failover cluster. This section summarizes how to create the load balancer in the Azure portal.

The load balancer must:

• Be in the same network and subnet as the new virtual machine.
• Have a static IP address for the availability group listener.
• Include a backend pool that consists of only the virtual machines in the same region as the load balancer.
• Use a TCP port probe that's specific to the IP address.
• Have a load-balancing rule that's specific to the SQL Server instance in the same region.
• Be a standard load balancer if the virtual machines in the backend pool aren't part of either a single availability set or a virtual machine scale set. For more information, review What is Azure Load Balancer?.
• Be a standard load balancer if the two virtual networks in two different regions are peered over global virtual network peering. For more information, see Azure Virtual Network frequently asked questions (FAQ).

The steps to create the load balancer are:

1. In the Azure portal, go to the resource group where your SQL Server instance is, and then select + Add.

2. Search for Load Balancer. Choose the load balancer that Microsoft publishes.

3. Select Create.

4. Configure the following parameters for the load balancer:

   Setting	Value
   Subscription	Use the same subscription as the virtual machine.
   Resource group	Use the same resource group as the virtual machine.
   Name	Use a text name for the load balancer (for example, remoteLB).
   Region	Use the same region as the virtual machine.
   SKU	Select Standard.
   Type	Select Internal.

   The Azure portal pane should look like this:

   

5. Select Next: Frontend IP Configuration.

6. Select Add a frontend IP configuration.

   

7. Set up the frontend IP address by using the following values:

   • Name: Use a name that identifies the frontend IP configuration.
   • Virtual network: Use the same network as the virtual machines.
   • Subnet: Use the same subnet as the virtual machines.
   • Assignment: Select Static.
   • IP address: Use an available address from the subnet. Use this address for your availability group listener. This address is different from your cluster IP address.
   • Availability zone: Optionally, choose an availability zone to deploy your IP address to.

   

8. Select Add.

9. Select Review + Create to validate the configuration, and then select Create to create the load balancer and the frontend IP address.

To configure the load balancer, you need to create a backend pool, create a probe, and set the load-balancing rules.

Add a backend pool for the availability group listener

1. In the Azure portal, go to your availability group. You might need to refresh the view to see the newly created load balancer.

2. Select the load balancer, select Backend pools, and then select +Add.

3. For Name, provide a name for the backend pool.

4. For Backend Pool Configuration, select NIC.

5. Select Add to associate the backend pool with the newly created SQL Server VM.

6. Under Virtual machine, choose the virtual machine that will host the availability group replica.

7. Select Add to add the virtual machine to the backend pool.

8. Select Save.

Set the probe

1. In the Azure portal, select the load balancer, select Health probes, and then select +Add.

2. Set the listener health probe as follows:

   Setting	Description	Example
   Name	Text	SQLAlwaysOnEndPointProbe
   Protocol	Choose TCP	TCP
   Port	Any unused port	59999
   Interval	The amount of time between probe attempts, in seconds	5

3. Select Add.

Set the load-balancing rules

1. In the Azure portal, select the load balancer, select Load balancing rules, and then select +Add.

2. Set the listener load-balancing rules as follows:

   Setting	Description	Example
   Name	Text	SQLAlwaysOnEndPointListener
   Frontend IP address	Choose an address	Use the address that you created when you created the load balancer.
   Backend pool	Choose the backend pool	Select the backend pool that contains the virtual machines targeted for the load balancer.
   Protocol	Choose TCP	TCP
   Port	Use the port for the availability group listener	1433
   Backend Port	This field is not used when you set a floating IP for direct server return	1433
   Health Probe	The name that you specified for the probe	SQLAlwaysOnEndPointProbe
   Session Persistence	Dropdown list	None
   Idle Timeout	Minutes to keep a TCP connection open	4
   Floating IP (direct server return)		Enable this setting.

   Warning

   Direct server return is set during creation. You can't change it.

3. Select Save.

Add failover clustering to SQL Server VMs

To add failover clustering features, complete the following steps on both SQL Server VMs:

1. Connect to the SQL Server virtual machine through RDP by using the CORP\Install account. Open the Server Manager dashboard.

2. Select the Add roles and features link on the dashboard.

   

3. Select Next until you get to the Server Features section.

4. In Features, select Failover Clustering.

5. Add any required features.

6. Select Install.

Tune network thresholds for a failover cluster

When you're running Windows failover cluster nodes in Azure VMs with SQL Server availability groups, change the cluster setting to a more relaxed monitoring state. This change will make the cluster more stable and reliable. For details, see IaaS with SQL Server: Tuning failover cluster network thresholds.

Configure the firewall on each SQL Server VM

The solution requires the following TCP ports to be open in the firewall:

• SQL Server VM: Port 1433 for a default instance of SQL Server.
• Azure load balancer probe: Any available port. Examples frequently use 59999.
• Cluster core load balancer IP address health probe: Any available port. Examples frequently use 58888.
• Database mirroring endpoint: Any available port. Examples frequently use 5022.

The firewall ports need to be open on the new SQL Server VM. The method of opening the ports depends on the firewall solution that you use. The following steps show how to open the ports in Windows Firewall:

1. On the SQL Server Start screen, open Windows Firewall with Advanced Security.

2. On the left pane, select Inbound Rules. On the right pane, select New Rule.

3. For Rule Type, select Port.

4. For the port, specify TCP and enter the appropriate port numbers. The following screenshot shows an example:

   

5. Select Next.

6. On the Action page, keep Allow the connection selected and select Next.

7. On the Profile page, accept the default settings and select Next.

8. On the Name page, specify a rule name (such as Azure LB Probe) in the Name box, and then select Finish.

Add SQL Server to the Windows Server failover cluster

The new SQL Server VM needs to be added to the Windows Server failover cluster that exists in your local region.

To add the SQL Server VM to the cluster:

1. Use RDP to connect to a SQL Server VM in the existing cluster. Use a domain account that's an administrator on both SQL Server VMs and the witness server.

2. On the Server Manager dashboard, select Tools, and then select Failover Cluster Manager.

3. On the left pane, right-click Failover Cluster Manager, and then select Connect to Cluster.

4. In the Select Cluster window, under Cluster name, choose <Cluster on this server>. Then select OK.

5. In the browser tree, right-click the cluster and select Add Node.

6. In the Add Node Wizard, select Next.

7. On the Select Servers page, add the name of the new SQL Server instance. Enter the server name in Enter server name, select Add, and then select Next.

8. On the Validation Warning page, select No. (In a production scenario, you should perform the validation tests). Then, select Next.

9. On the Confirmation page, if you're using Storage Spaces, clear the Add all eligible storage to the cluster checkbox.

   Warning

   If you don't clear Add all eligible storage to the cluster, Windows detaches the virtual disks during the clustering process. As a result, they don't appear in Disk Manager or Explorer until the storage is removed from the cluster and reattached via PowerShell.

10. Select Next.

11. Select Finish.

    Failover Cluster Manager shows that your cluster has a new node and lists it in the Nodes container.

Add the IP address for the Windows Server failover cluster

Next, create the IP address resource and add it to the cluster for the new SQL Server VM:

1. In Failover Cluster Manager, select the name of the cluster. Right-click the cluster name under Cluster Core Resources, and then select Properties:

   

2. In the Cluster Properties dialog, select Add under IP Addresses, and then add the IP address of the cluster name from the remote network region. Select OK in the IP Address dialog, and then select OK in the Cluster Properties dialog to save the new IP address.

   

3. Add the IP address as a dependency for the cluster core name.

   Open the Cluster Properties dialog once more, and select the Dependencies tab. Configure an OR dependency for the two IP addresses.

   

Add an IP address for the availability group listener

The IP address for the listener in the remote region needs to be added to the cluster. To add the IP address:

1. In Failover Cluster Manager, right-click the availability group role. Point to Add Resource, point to More Resources, and then select IP Address.

   

2. To configure this IP address, right-click the resource under Other Resources, and then select Properties.

   

3. For Name, enter a name for the new resource. For Network, select the network from the remote datacenter. Select Static IP Address, and then in the Address box, assign the static IP address from the new Azure load balancer.

   

4. Select Apply, and then select OK.

5. Add the IP address resource as a dependency for the listener client access point (network name) cluster.

   Right-click the listener client access point, and then select Properties. Browse to the Dependencies tab and add the new IP address resource to the listener client access point. The following screenshot shows a properly configured IP address cluster resource:

   

   Important

   The cluster resource group includes both IP addresses. Both IP addresses are dependencies for the listener client access point. Use the OR operator in the cluster dependency configuration.

6. Set the cluster parameters in PowerShell.

   Run the PowerShell script with the cluster network name, IP address, and probe port that you configured on the load balancer in the new region:

   $ClusterNetworkName = "<MyClusterNetworkName>" # The cluster name for the network in the new region (Use Get-ClusterNetwork on Windows Server 2012 or later to find the name.)
   $IPResourceName = "<IPResourceName>" # The cluster name for the new IP address resource.
   $ILBIP = "<n.n.n.n>" # The IP address of the internal load balancer in the new region. This is the static IP address for the load balancer that you configured in the Azure portal.
   [int]$ProbePort = <nnnnn> # The probe port that you set on the internal load balancer.
   
   Import-Module FailoverClusters
   
   Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ILBIP";"ProbePort"=$ProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
   

Enable availability groups

Next, enable the Always On availability groups feature. Complete these steps on the new SQL Server VM:

1. From the Start screen, open SQL Server Configuration Manager.

2. In the browser tree, select SQL Server Services. Right-click the SQL Server (MSSQLSERVER) service, and then select Properties.

3. Select the AlwaysOn High Availability tab, and then select Enable AlwaysOn Availability Groups.

   

4. Select Apply. Select OK in the pop-up dialog.

5. Restart the SQL Server service.

Add a replica to the availability group

After SQL Server has restarted on the newly created virtual machine, you can add it as a replica to the availability group:

1. Open a remote desktop session to the primary SQL Server instance in the availability group, and then open SQL Server Management Studio (SSMS).

2. In Object Explorer in SSMS, open Always On High Availability > Availability Groups. Right-click your availability group name, and then select Add Replica.

3. Connect to the existing replica, and then select Next.

4. Select Add Replica and connect to the new SQL Server VM.

   Important

   A replica in a remote Azure region should be set to asynchronous replication with manual failover.

5. On the Select Initial Data Synchronization page, select Full and specify a shared network location. For the location, use the backup share that you created. In the example, it was \\<First SQL Server>\Backup\. Then select Next.

   Note

   Full synchronization takes a full backup of the database on the first instance of SQL Server and restores it to the second instance. For large databases, we don't recommend full synchronization because it might take a long time.

   You can reduce this time by manually backing up the database and restoring it with NO RECOVERY. If the database is already restored with NO RECOVERY on the second SQL Server instance before you configure the availability group, select Join only. If you want to take the backup after you configure the availability group, select Skip initial data synchronization.

   

6. On the Validation page, select Next. This page should look similar to the following image:

   

   Note

   A warning for the listener configuration says you haven't configured an availability group listener. You can ignore this warning because the listener is already set up. It was created after you created the Azure load balancer in the local region.

7. On the Summary page, select Finish, and then wait while the wizard configures the new availability group. On the Progress page, you can select More details to view the detailed progress.

   After the wizard finishes the configuration, inspect the Results page to verify that the availability group is successfully created.

8. Select Close to close the wizard.

Check the availability group

In Object Explorer, expand Always On High Availability, and then expand Availability Groups. Right-click the availability group and select Show Dashboard.

Your availability group dashboard should look similar to the following screenshot, now with another replica:

The dashboard shows the replicas, the failover mode of each replica, and the synchronization state.

Check the availability group listener

1. In Object Explorer, expand Always On High Availability, expand Availability Groups, and then expand Availability Group Listener.

2. Right-click the listener name and select Properties. Both IP addresses should now appear for the listener (one in each region).

   

Set the connection for multiple subnets

The replica in the remote datacenter is part of the availability group, but it's in a different subnet. If this replica becomes the primary replica, application connection time-outs might occur. This behavior is the same as an on-premises availability group in a multiple-subnet deployment. To allow connections from client applications, either update the client connection or configure name resolution caching on the cluster network name resource.

Preferably, update the cluster configuration to set RegisterAllProvidersIP=1 and the client connection strings to set MultiSubnetFailover=Yes. See Connecting with MultiSubnetFailover.

If you can't modify the connection strings, you can configure name resolution caching. See Timeout occurs when you connect to an Always On listener in a multi-subnet environment.

Fail over to the remote region

To test listener connectivity to the remote region, you can fail the replica over to the remote region. While the replica is asynchronous, failover is vulnerable to potential data loss. To fail over without data loss, change the availability mode to synchronous and set the failover mode to automatic. Use the following steps:

1. In Object Explorer, connect to the instance of SQL Server that hosts the primary replica.

2. Under Always On Availability Groups, right-click your availability group and select Properties.

3. On the General page, under Availability Replicas, set the secondary replica on the disaster recovery (DR) site to use Synchronous Commit availability mode and Automatic failover mode.

   If you have a secondary replica in same site as your primary replica for high availability, set this replica to Asynchronous Commit and Manual.

4. Select OK.

5. In Object Explorer, right-click the availability group and select Show Dashboard.

6. On the dashboard, verify that the replica on the DR site is synchronized.

7. In Object Explorer, right-click the availability group and select Failover. SQL Server Management Studio opens a wizard to fail over SQL Server.

8. Select Next, and select the SQL Server instance on the DR site. Select Next again.

9. Connect to the SQL Server instance on the DR site, and then select Next.

10. On the Summary page, verify the settings and select Finish.

After you test connectivity, move the primary replica back to your primary datacenter and set the availability mode back to its normal operating settings. The following table shows the normal operating settings for the architecture described in this article:

Location	Server instance	Role	Availability mode	Failover mode
Primary datacenter	SQL-1	Primary	Synchronous	Automatic
Primary datacenter	SQL-2	Secondary	Synchronous	Automatic
Secondary or remote datacenter	SQL-3	Secondary	Asynchronous	Manual

For more information about planned and forced manual failover, see the following articles:

• Perform a planned manual failover of an availability group (SQL Server)
• Perform a forced manual failover of an availability group (SQL Server)

Next steps

To learn more, see:

• Windows Server failover cluster with SQL Server on Azure VMs
• Always On availability groups with SQL Server on Azure VMs
• Overview of Always On availability groups
• HADR settings for SQL Server on Azure VMs