Skip to content

Commit e6059b0

Browse files
authored
Merge pull request #116151 from Jak-MS/virtual-machines-windows
edit passes - Virtual machines windows - group 1
2 parents 231cc4f + 6d17c06 commit e6059b0

File tree

5 files changed

+98
-77
lines changed

5 files changed

+98
-77
lines changed

articles/azure-sql/virtual-machines/windows/availability-group-azure-marketplace-template-configure.md

Lines changed: 45 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Set up high availability for Azure Resource Manager VMs | Microsoft Docs
3-
description: This tutorial shows you how to create an Always On availability group with Azure virtual machines in Azure Resource Manager mode.
2+
title: Set up high availability for Azure Resource Manager virtual machines | Microsoft Docs
3+
description: This tutorial shows you how to create an Always On availability group with Azure Virtual Machines in Azure Resource Manager mode.
44
services: virtual-machines-windows
55
documentationcenter: na
66
author: MikeRayMSFT
@@ -19,9 +19,10 @@ ms.author: mikeray
1919

2020
---
2121
# Configure Always On availability groups in Azure Virtual Machines automatically: Resource Manager
22+
2223
[!INCLUDE[appliesto-sqlvm](../../includes/appliesto-sqlvm.md)]
2324

24-
This tutorial shows you how to create a SQL Server availability group that uses Azure Resource Manager virtual machines. The tutorial uses Azure blades to configure a template. You can review the default settings, type required settings, and update the blades in the portal as you walk through this tutorial.
25+
This tutorial shows you how to create a SQL Server availability group that uses Azure Resource Manager virtual machines (VM). The tutorial uses Azure blades to configure a template. You can review the default settings, type required settings, and update the blades in the portal as you walk through this tutorial.
2526

2627
The complete tutorial creates a SQL Server availability group on Azure Virtual Machines that include the following elements:
2728

@@ -46,7 +47,6 @@ Before you start this tutorial, confirm the following:
4647
> [!NOTE]
4748
> If you are interested in using availability groups with SharePoint, also see [Configure SQL Server 2012 Always On availability groups for SharePoint 2013](/SharePoint/administration/configure-an-alwayson-availability-group).
4849
>
49-
>
5050
5151
In this tutorial, use the Azure portal to:
5252

@@ -58,18 +58,20 @@ In this tutorial, use the Azure portal to:
5858
[!INCLUDE [availability-group-template](../../../../includes/virtual-machines-windows-portal-sql-alwayson-ag-template.md)]
5959

6060
## Provision the cluster from the gallery
61+
6162
Azure provides a gallery image for the entire solution. To locate the template:
6263

6364
1. Sign in to the Azure portal by using your account.
64-
2. In the Azure portal, click **Create a resource** to open the **New** pane.
65+
2. In the Azure portal, select **Create a resource** to open the **New** pane.
6566
3. On the **New** pane, search for **AlwaysOn**.
6667
![Find AlwaysOn Template](./media/availability-group-azure-marketplace-template-configure/16-findalwayson.png)
6768
4. In the search results, locate **SQL Server AlwaysOn Cluster**.
6869
![AlwaysOn Template](./media/availability-group-azure-marketplace-template-configure/17-alwaysontemplate.png)
6970
5. On **Select a deployment model**, choose **Resource Manager**.
7071

7172
### Basics
72-
Click **Basics** and configure the following settings:
73+
74+
Select **Basics** and configure the following settings:
7375

7476
* **Administrator user name** is a user account that has domain administrator permissions and is a member of the SQL Server sysadmin fixed server role on both instances of SQL Server. For this tutorial, use **DomainAdmin**.
7577
* **Password** is the password for the domain administrator account. Use a complex password. Confirm the password.
@@ -81,10 +83,11 @@ The following screenshot is a completed **Basics** blade:
8183

8284
![Basics](./media/availability-group-azure-marketplace-template-configure/1-basics.png)
8385

84-
Click **OK**.
86+
Select **OK**.
8587

8688
### Domain and network settings
87-
This Azure gallery template creates a domain and domain controllers. It also creates a network and two subnets. The template cannot create servers in an existing domain or virtual network. The next step configures the domain and network settings.
89+
90+
This Azure gallery template creates a domain and domain controllers. It also creates a network and two subnets. The template can't create servers in an existing domain or virtual network. The next step configures the domain and network settings.
8891

8992
On the **Domain and network settings** blade, review the preset values for the domain and network settings:
9093

@@ -101,9 +104,10 @@ The **Domain and network settings** should look like the following screenshot:
101104

102105
If necessary, you can change these values. For this tutorial, use the preset values.
103106

104-
Review the settings, and then click **OK**.
107+
Review the settings, and then select **OK**.
105108

106109
### Availability group settings
110+
107111
On **Availability group settings**, review the preset values for the availability group and the listener.
108112

109113
* **Availability group name** is the clustered resource name for the availability group. For this tutorial, use **Contoso-ag**.
@@ -114,19 +118,21 @@ If necessary, you can change these values. For this tutorial, use the preset val
114118

115119
![availability group settings](./media/availability-group-azure-marketplace-template-configure/3-availabilitygroup.png)
116120

117-
Click **OK**.
121+
Select **OK**.
118122

119123
### Virtual machine size, storage settings
120-
On **VM size, storage settings**, choose a SQL Server virtual machine size, and review the other settings.
121124

122-
* **SQL Server virtual machine size** is the size for both virtual machines that run SQL Server. Choose an appropriate virtual machine size for your workload. If you are building this environment for the tutorial, use **DS2**. For production workloads, choose a virtual machine size that can support the workload. Many production workloads require **DS4** or larger. The template builds two virtual machines of this size and installs SQL Server on each one. For more information, see [Sizes for virtual machines](../../../virtual-machines/windows/sizes.md).
125+
On **VM size, storage settings**, choose a SQL Server virtual machine size, and review the other settings.
123126

124-
?toc=%2fazure%2fvirtual-machines%2fwindows%2ftoc.json
127+
* **SQL Server virtual machine size** is the size for both virtual machines that run SQL Server. Choose an appropriate virtual machine size for your workload.
128+
* If you are building this environment for the tutorial, use **DS2**.
129+
* For production workloads, choose a virtual machine size that can support the workload.
130+
* Many production workloads require **DS4** or larger. The template builds two virtual machines of this size and installs SQL Server on each one.
131+
* For more information, see [Sizes for virtual machines](../../../virtual-machines/windows/sizes.md).
125132

126-
> [!NOTE]
127-
> Azure installs the Enterprise Edition of SQL Server. The cost depends on the edition and the virtual machine size. For detailed information about current costs, see [virtual machines pricing](https://azure.microsoft.com/pricing/details/virtual-machines/#Sql).
128-
>
129-
>
133+
> [!NOTE]
134+
> Azure installs the Enterprise Edition of SQL Server. The cost depends on the edition and the virtual machine size. For detailed information about current costs, see [virtual machines pricing](https://azure.microsoft.com/pricing/details/virtual-machines/#Sql).
135+
>
130136
131137
* **Domain controller virtual machine size** is the virtual machine size for the domain controllers. For this tutorial use **D2**.
132138
* **File Share Witness virtual machine size** is the virtual machine size for the file share witness. For this tutorial, use **A1**.
@@ -143,18 +149,18 @@ For this tutorial, use **General workload**.
143149

144150
![VM size storage settings](./media/availability-group-azure-marketplace-template-configure/4-vm.png)
145151

146-
Review the settings, and then click **OK**.
152+
Review the settings, and then select **OK**.
147153

148154
#### A note about storage
155+
149156
Additional optimizations depend on the size of the SQL Server data disks. For each terabyte of data disk, Azure adds an additional 1 TB premium storage. When a server requires 2 TB or more, the template creates a storage pool on each SQL Server virtual machine. A storage pool is a form of storage virtualization where multiple discs are configured to provide higher capacity, resiliency, and performance. The template then creates a storage space on the storage pool and presents a single data disk to the operating system. The template designates this disk as the data disk for SQL Server. The template tunes the storage pool for SQL Server by using the following settings:
150157

151158
* Stripe size is the interleave setting for the virtual disk. Transactional workloads use 64 KB. Data warehousing workloads use 256 KB.
152159
* Resiliency is simple (no resiliency).
153160

154-
> [!NOTE]
155-
> Azure premium storage is locally redundant and keeps three copies of the data within a single region, so additional resiliency at the storage pool is not required.
156-
>
157-
>
161+
> [!NOTE]
162+
> Azure premium storage is locally redundant and keeps three copies of the data within a single region, so additional resiliency at the storage pool is not required.
163+
>
158164
159165
* Column count equals the number of disks in the storage pool.
160166

@@ -167,48 +173,52 @@ For more information about SQL Server configuration best practices, see
167173
[Performance best practices for SQL Server in Azure virtual machines](performance-guidelines-best-practices.md).
168174

169175
### SQL Server settings
176+
170177
On **SQL Server settings**, review and modify the SQL Server virtual machine name prefix, SQL Server version, SQL Server service account and password, and the SQL auto-patching maintenance schedule.
171178

172179
* **SQL Server Name Prefix** is used to create a name for each SQL Server virtual machine. For this tutorial, use **sqlserver**. The template names the SQL Server virtual machines *sqlserver-0* and *sqlserver-1*.
173180
* **SQL Server version** is the version of SQL Server. For this tutorial use **SQL Server 2014**. You can also choose **SQL Server 2012** or **SQL Server 2016**.
174181
* **SQL Server service account user name** is the domain account name for the SQL Server service. For this tutorial, use **sqlservice**.
175-
* **Password** is the password for the SQL Server service account. Use a complex password. Confirm the password.
182+
* **Password** is the password for the SQL Server service account. Use a complex password. Confirm the password.
176183
* **SQL Auto Patching maintenance schedule** identifies the day of the week that Azure automatically patches the SQL Servers. For this tutorial, type **Sunday**.
177184
* **SQL Auto Patching maintenance start hour** is the time of day for the Azure region when automatic patching begins.
178185

179186
> [!NOTE]
180187
> The patching window for each virtual machine is staggered by one hour. Only one virtual machine is patched at a time to prevent disruption of services.
181188
>
182-
>
183189
184190
![SQL Server settings](./media/availability-group-azure-marketplace-template-configure/5-sql.png)
185191

186-
Review the settings, and then click **OK**.
192+
Review the settings, and then select **OK**.
187193

188194
### Summary
189-
On the summary page, Azure validates the settings. You can also download the template. Review the summary. Click **OK**.
195+
196+
On the summary page, Azure validates the settings. You can also download the template. Review the summary. Select **OK**.
190197

191198
### Buy
192-
This final blade contains **terms of use**, and **privacy policy**. Review this information. When you are ready for Azure to start to create the virtual machines and all the other required resources for the availability group, click **Create**.
199+
200+
This final blade contains **terms of use**, and **privacy policy**. Review this information. When you are ready for Azure to start to create the virtual machines and all the other required resources for the availability group, select **Create**.
193201

194202
The Azure portal creates the resource group and all the resources.
195203

196204
## Monitor deployment
205+
197206
Monitor the deployment progress from the Azure portal. An icon that represents the deployment is automatically pinned to the Azure portal dashboard.
198207

199208
![Azure Dashboard](./media/availability-group-azure-marketplace-template-configure/11-deploydashboard.png)
200209

201210
## Connect to SQL Server
202-
The new instances of SQL Server are running on virtual machines that have internet-connected IP addresses. You can remote desktop (RDP) directly to each SQL Server virtual machine.
203211

204-
To RDP to a SQL Server, follow these steps:
212+
The new instances of SQL Server are running on virtual machines that have internet-connected IP addresses. You can connect directly to each SQL Server virtual machine with remote desktop (RDP).
213+
214+
To use RDP to connect to a SQL Server VM, follow these steps:
205215

206216
1. From the Azure portal dashboard, verify that the deployment has succeeded.
207-
2. Click **Resources**.
208-
3. In the **Resources** blade, click **sqlserver-0**, which is the computer name of one of the virtual machines that's running SQL Server.
209-
4. On the blade for **sqlserver-0**, click **Connect**. Your browser asks if you want to open or save the remote connection object. Click **Open**.
210-
5. **Remote desktop connection** might warn you that the publisher of this remote connection can’t be identified. Click **Connect**.
211-
6. Windows security prompts you to enter your credentials to connect to the IP address of the primary domain controller. Click **Use another account**. For **User name**, type **contoso\DomainAdmin**. You configured this account when you set the administrator user name in the template. Use the complex password that you chose when you configured the template.
212-
7. **Remote desktop** might warn you that the remote computer could not be authenticated due to problems with its security certificate. It shows you the security certificate name. If you followed the tutorial, the name is **sqlserver-0.contoso.com**. Click **Yes**.
217+
2. Select **Resources**.
218+
3. In the **Resources** blade, select **sqlserver-0**, which is the computer name of one of the virtual machines that's running SQL Server.
219+
4. On the blade for **sqlserver-0**, select **Connect**. Your browser asks if you want to open or save the remote connection object. Select **Open**.
220+
5. **Remote desktop connection** might warn you that the publisher of this remote connection can’t be identified. Select **Connect**.
221+
6. Windows security prompts you to enter your credentials to connect to the IP address of the primary domain controller. Select **Use another account**. For **User name**, type **contoso\DomainAdmin**. You configured this account when you set the administrator user name in the template. Use the complex password that you chose when you configured the template.
222+
7. **Remote desktop** might warn you that the remote computer could not be authenticated due to problems with its security certificate. It shows you the security certificate name. If you followed the tutorial, the name is **sqlserver-0.contoso.com**. Select **Yes**.
213223

214224
You are now connected with RDP to the SQL Server virtual machine. You can open SQL Server Management Studio, connect to the default instance of SQL Server, and verify that the availability group is configured.

0 commit comments

Comments
 (0)