Sql Server 2012 Cluster Step By Step Installation Guide
Now that Sql server 2012 ( Denali ) is released it seemed fitting to create a new setup guide for the Cluster. We will cover the setup of HADRON / AlwaysOn in subsequenet posts but for now this post is involved with the creation of the cluster which can be used standalone or as part of an AlwaysOn implementation later on. As with Sql Server 2008 R2, the first step to installing a a sql server cluster is to create the windows server 2008 cluster. This is described in a similar article on this site.
On Sql server 2012, setup windows cluster
Let the setup support rules get checked by the installer
Warnings about firewall configuration can be ignored or if there is an issue with the network binding such as the following:
Rule “Network binding order” generated a warning.
The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order.
Then follow the below steps to set the network binding order
Set Network Binding Order
To resolve this error, go to Control Panel -> Network and Internet -> Network and Sharing Center
And select the option that says change adapter settings.
Hold down the alt button and a menu will appear.
Select advanced and advanced settings
Browse to the primary Local area connection and move the entry up using the arrow button.
If the problem persists, open a command prompt and run
wmic nicconfig get description, SettingID, IPAddress
Note the GUID of the primary Local Area Connection.
Open regedit and browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Linkage.
Open the Bind key and ensure that the primary connection is at the top of the list.
Select Sql Server Installation
Select the required features
Press next to go to the feature rules screen
If the following error appears:
Rule Check Result
Rule “Microsoft .NET Framework 3.5 Service Pack 1 is required” failed.
This computer does not have the Microsoft .NET Framework 3.5 Service Pack 1 installed. If the operating system is Windows Vista or Windows Server 2008, download and install Microsoft .NET Framework 3.5 SP1 from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=22. If the operating system is Windows 7 or Windows Server 2008 R2, enable the .NET Framework 3.5 feature. A computer restart may be required after installing.
If this occurs you will need to install from the server manager -> features -> add features
Then rerun the feature rules and press next to go to the instance configuration.
The sql server network name will be used to identify the specific sql server cluster by end clients. You can also choose a specific instance name or select default.
Confirm disk space requirements
Select the correct cluster group name ( usually just accept default if this is the first install of an instance)
Specify the disks to be included as part of the cluster (these will be the LUNS that are used for data, log, TempdDB etc)
Specify the IP Address and subnets for the cluster network configuration. Note a new IP address needs to be assigned for the Sql server instance. This is different from the IP address of the windows cluster.
Enter the correct username and password for both the Sql Server Engine and the agent. Note for the purposes of avoiding problems with SPN’s and Kerberos you should use the same service account on all nodes of the cluster.
If you have collation specific databases, be sure to check and adjust the collation setting
On the server configuration screen, add the Sql Server administrator’s active directory group to the Server Admins of this Sql Server Instance. You may want to also add the current user depending on security requirements.
Got to the data directories tab and set the correct directories for the instance. If there are multiple instances sharing the LUN it’s important to prefix with the directory structure with the instance name.
Select your desired error reporting settings.
Ensure that the cluster installation rules passed
Select install and allow the completion to finish. That will complete the installation of the Sql Cluster, however at that stage, the cluster will only consist of one node.
To add a second node, log on to second node and run the setup utility.
Select add node to a sql server failover cluster
You will be prompted to accept licence terms and install setup files
Verify that the support roles pass the test.
Verify the cluster node configuration by selecting the correct instance name and verify all the network configuration is correct.
Verify the cluster node configuration
Enter the correct passwords for the service accounts
Select appropriate error reporting settings
Check that all the rules pass
If you get a message saying .net 3.5 is required then enable the feature as described previously
Press Install to install node
Once install is complete, go to passive node
Run latest service pack upgrade on the passive node.
Once service pack is completed failover to the passive node by right clicking services and applications and selecting “move this service to another node” and selecting the currently active node.