Installing SQL Server 2008 R2 on a Failover Cluster using Server 2008 R2

Scenario

You’ve configured a Failover Cluster using Server 2008 R2, and now you want to install SQL Server 2008 R2.

Solution

Changes

A few changes were made to the simple Failover Cluster that was previously configured:

• Several LUNs were added to the FreeNAS VM so separate disks could be used for each function:
  
• 3 x Network Interface Cards (NICs) were configured on each node, each on a different subnet:
  • LAN: 10.10.10.0/24
  • SAN: 10.10.20.0/24
  • Heartbeat: 10.10.30.0/24
• The FreeNAS interface was configured on the SAN subnet (10.10.20.220).

This time round, the Failover Cluster Validation Report didn’t have a single warning; all green ticks 😉

Microsoft Distributed Transaction Coordinator (MSDTC)

We need to set up the MSDTC to support distributed transactions. Do the following on all nodes:

1. Navigate to Server Manager > Roles > Add Roles.
2. Select Application Server.
3. Select Incoming and Outgoing Remote Transactions:
   
4. Click Next, Finish.
5. Navigate to Failover Cluster Manager > [Clustername]
6. Right-click Services and applications > Configure a Service or Application:
   
7. Select Distributed Transaction Coordinator (DTC):
   
8. Choose a name and IP address for the DTC service:
   
9.  Select a disk:
   
10.  Confirm settings and click Next:
    
11.  Once completed, view the report or click Finish:
    
12. If successful, you will see the DTC service under Services and applications:
    

SQL Server Failover Cluster Installation

1. From the setup menu, select Installation > New SQL Server failover cluster installation:
   
2. Click OK after the first set of checks:
   
3.  Enter a product key or leave it on Evaluation if you’re in a lab like me:
   
4. Accept the license terms:
   
5.  Click Install to start the SQL Server setup:
   
6.  Click Next after more checks have completed:
   
7.  Choose which components you want to install. I’m keeping it simple here:
   
8.  Choose a SQL Server Network and Instance Name:
   
9. Review the Disk Usage Summary:
   
10.  Choose a Resource Group Name:
    
11. Choose all of the disks to be used:
    
12.  Choose an IP Address:
    
13.  Select the Cluster Security Policy:
    
14.  Enter the user accounts for each service. It’s recommended to create a separate Domain Account for each service:
    
15.  Select the Authentication Mode and specify the SQL Server administrators:
    
16.  Map the directories to the separate disks you set up earlier:
    
17. Select your Error Reporting preference:
    
18. More checks please landlord…oh go on then!
    
19. Review your selections and click Install:
    
20.  Setup complete:
    
21.  All being well, your new SQL Instance should appear under Services and applications:
    

Although there are quite a few steps here, relax, as it’s easier adding a node to a SQL Server 2008 R2 Failover Cluster.