There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter

Install SQL Server 2016 Always-On Cluster

I a big believer in SQL Server's Always-On technology. With storage being cheap, and the fast fail-over of an Always-On server, there is no reason to use the older clustering technology that required shared storage and could take up to 30 seconds in my experience to start the SQL Database Engine and complete the fail-over. With Always-On, there is also the ability to do “geo” based replication and fail-over. Geo-Replication enables you to configure readable secondary databases in the same or different data center locations. Secondary databases are available for querying and for fail-over in the case of a data center outage or the inability to connect to the primary database.

Here is how I set-up SQL Server 2016 Always-On Clusters. For these examples I'll use the following assumptions:

  • Active Directory Domain: contoso.com
  • SQL Server Node 1: SQLAO1N1
  • SQL Server Node 2: SQLAO1N2
  • SQL Cluster Name: SQLAO1
  • Group Managed Service Account: svc-sqlao1

The first step is to install Install Windows Server 2012 R2 on both nodes. I also add two additional disks: one for data and one for logs. I also format them with 64K allocation units which I think gives SQL better performance:

$disks = @(
    $(Get-Disk -Number 1),
    $(Get-Disk -Number 2)
)
 
foreach ($disk in $disks) {
    Set-Disk -Number $disk.Number -IsOffline $false
    Set-Disk -Number $disk.Number -IsReadOnly $false
 
    Initialize-Disk -Number $disk.Number -PartitionStyle GPT
    New-Partition -DiskNumber $disk.Number -UseMaximumSize -GptType '{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}' -AssignDriveLetter
 
    $partition = (Get-Partition -DiskNumber $disk.Number | Sort-Object Size -Descending | Select-Object -First 1)
 
    Format-Volume -FileSystem NTFS -Partition $partition -AllocationUnitSize 65536 -Confirm:$false
}

The next step is to create an Active Directory Group for DBAs and the Group Managed Service Accounts for the SQL Engine to use. On the Domain Controller or a system with a remote server administrative tools (RSAT) installed:

Import-Module ActiveDirectory
 
New-ADGroup -Name SQLAO1DBA -GroupCategory Security -GroupScope Global
 
New-ADServiceAccount -Name svc-sqlao1 -Enable $true -DNSHostName sqlao1.contoso.com
 
New-ADGroup -Name SQLAO1Nodes -GroupCategory Security -GroupScope Global
Add-ADGroupMember SQLAO1Nodes SQLAO1N1$,SQLAO1N2$ 
 
Set-ADServiceAccount -Identity svc-sqlao1 -PrincipalsAllowedToRetrieveManagedPassword SQLAO1Nodes

Then, reboot each node and then execute the following on each node:

Add-WindowsFeature RSAT-AD-PowerShell
Import-Module ActiveDirectory
 
Install-ADServiceAccount -Identity svc-sqlao1

Now the account is available on each node.

  1. Mount the SQL 2016 Installation ISO.
  2. Since Always-On does not use the traditional clustering technology or clustering services, select the SQL server stand-alone installation option.
  3. On the license key page make sure you have a enterprise edition license key. Click Next.
  4. On the next page accept the license key. Click Next.
  5. One feature I like about the SQL installer is the ability to download and apply updates as part of the installation process. Click Next.
  6. As part of the installation, the installer will conduct a series of system checks and will not let you proceed until all tests have passed. Click Next.
  7. At this point, select SQL Server features to be installed. This will be very dependent on the environment but I typically do a minimum install for my Always-On nodes and then will setup things like Analysis or Reporting Services on a separate server.
  8. For the SQL Instance configuration, Accept the the default instance. Click Next.
  9. Select the group managed service account created above. The installer will blank out the password field for the gMSA account. Click Next.
  10. Next, choose the authentication option. I choose Windows, since I set most application up to use integrated authentication but have on occasion set up Mixed Mode authentication if an application couldn't work with integrated authentication, I also add the DBA group created above to manage the node. I never add individual accounts to the SQL Server Administrators. Click on the Data Directories tab.
  11. I Set the Data root Directory to D:\ and remove the extra Program Files\Microsoft SQL Server from the path. I also switch the Log Directory to the E:\ drive.
  12. On the TempDB tab, I change the log directory to the E:\ drive as well. Click Next.
  13. Finally, review all of the configuration settings. Click Install and wait for it to complete.

While SQL is being installed on the first node, repeat this on the other node to get it ready.

Fail-Over Clustering

Once both nodes are up and running and have SQL Server installed, it is time to install Fail-Over Clustering. Open an elevated PowerShell session on each node:

Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools 
 
Test-Cluster -Node SQLAO1N1,SQLAO1N2

You may get warnings regarding one network interface or no shared disk but these are ok as the Fail-over is only managing a shared IP address for the listener. On one of the nodes, execute the following in an elevated PowerShell session:

New-Cluster -Name SQLAO1 -Node SQLAO1N1,SQLAO1N2 -StaticAddress 172.16.101.81 -NoStorage

I usually set up Cluster-Aware Updating at this point so that I can apply updates easily, but I'll put the directions in another page since it is pretty much the same on all types of Windows clusters.

Availability Group Preparation

Always-On needs a place to store the database during the initial replication. I typically create a folder D:\Backups drive for backups and the initial replication. Share this folder and give the SQL gMSA account permission to Modify, Read & execute. Then:

  1. On each node, open SQL Server Configuration Manager and locate the SQL Server service. Open the properties and click on the AlwaysOn High Availability. Check the Enable AlwaysOn Availability Groups and make sure that the Windows fail-over cluster name is correct.
  2. Restart the SQL Service on both nodes.

Availability Group Configuration

  1. Open SQL Server Management Studio. In the Connect To Server window, ensure that SQLAO1N1 is listed, and use Windows Authentication to log in. Click Connect.
  2. Create a Database named AOSeed. This database will be used to set-up the availability group.
  3. Preform a full backup prior to proceeding.
  4. In the left pane, expand Always-On High Availability.
  5. Right-click Availability Groups, and select New Availability Group Wizard.
  6. On the Introduction page, click Next.
  7. On the Specify Availability Group Name page, enter SQLAO1.
  8. On the Select Databases page, select the check box next to AOSeed. Note that this database is marked as meeting the prerequisites. Click Next.
  9. On the Specify Replicas page, click Add Replica. In the Connect To Server window, enter SQLAO1N2 next to Server Name, and click Connect.
  10. For SQLAO1N1 and the newly added SQLAO1N2 server instance, select the box for Automatic Failover. This will also automatically select the box for synchronous replication for each SQL Server instance.
  11. On the Select Initial Data Synchronization page, select Full. The wizard subsequently triggers a full backup of the database, logs to a location you specify, and restores this backup to the secondary SQL Server instance, in this case, SQLAO1N2. From there, replication begins synchronously between SQLAO1N1 and SQLAO1N2.
  12. In the Specify A Shared Network Location Accessible By All Replicas text box, enter \\SQLAO1N1\Backup, and click Next to begin validation.
  13. After validation is complete, review the results, and click Next.
  14. On the Summary page, review all of your selections, and click Finish to begin the process. This will take a few moments to complete. When the process is complete, close SQL Server Management Studio.

At this point you should be able to use the cluster name as the database server name just like any other SQL server to access the databases. Unless you have a need to have separate listeners to segregate access to databases, there is no need to configure a listener. Skipping a separate listener also consume one less IP address on the network.

Copyright © 2019 by Julian Easterling. SOME RIGHTS RESERVED.
Privacy Policy              Terms of Use             


Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.


All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.