Windows Cluster Setup with Windows 2008 R2

Shares

Creating a Microsoft Windows Cluster with Windows 2008 R2

Windows Cluster Setup and Configuration with Windows 2008 R2

1. I have created a shared Quorum Drive via iSCSI on both my windows cluster nodes named SQL1 and SQL1. My Quorum drive has a drive letter of E:


Microsoft Windows Cluster

2. I have added 3 network adapters to each of my cluster nodes: LAN, iSCSI and Heartbeat. Lan will be used for client connections, iSCSI for storage and Heartbeat for private heartbeat communication between the windows cluster nodes. Each Network adapter is in a separate vlan.


Microsoft Windows Cluster

3. I have also set the following adapter order. Lan being number 1, followed by Heartbeat and lastly iSCSI.


Microsoft Windows Cluster

4. Now we need to install the Failover Clustering Feature on both servers, SQL1 and SQL2. Enter into Server Manager, click on Features and tick Failover Clustering.


Microsoft Windows Cluster

5. Click Install.


Microsoft Windows Cluster

6. Installation is successful, click Close.


Microsoft Windows Cluster

7. On SQL1, click Start and select Failover Cluster Manager under Administration Tools.


Microsoft Windows Cluster

8. Click on Validate a Configuration and the wizard will begin. click Next.


Microsoft Windows Cluster

9. I will enter in the name sql1 and click Add, then enter in the name sql2 and click Add. click Next.


Microsoft Windows Cluster

10. Select Run all tests and click Next.


Microsoft Windows Cluster

11. A summary of your servers that will be tested. Click Next.


Microsoft Windows Cluster

12. The test has completed successfully. Click Finish.


Microsoft Windows Cluster

13. Right click on Failover Cluster Manager and select Create a Cluster.


Microsoft Windows Cluster

14. The Create Cluster Wizard begins, click Next.


Microsoft Windows Cluster

15. I will type in sql1 and click Add followed by typeing in sql2 and clicking Add. Click Next.


Microsoft Windows Cluster

16. Type in a name for your cluster. This will be a Netbios name and registered in your Active Directory DNS. Enter in an IP address for the Windows Cluster. Click Next.


Microsoft Windows Cluster

17. All the information is gather and you are ready to create your Windows Cluster. Click Next.


Microsoft Windows Cluster

18. The Windows Cluster has been created successfully. Click Finish.


Microsoft Windows Cluster

19. You can see both sql1 and sql2 nodes in the cluster, along with the Networks.


Microsoft Windows Cluster

20. Click on Cluster Network 1, this is my Lan network.


Microsoft Windows Cluster

21. Right click on Cluster Network 1 and select properties. Change the name to Lan and make sure Allow cluster network communication on this network and Allow clients to connect through this network are ticked. Click Ok.


Microsoft Windows Cluster

22. Select Cluster Network 2. This is my Heartbeat or cluster communications network.


Microsoft Windows Cluster

23. Right click on Cluster Network 2 and select properties. Change the name to Heartbeat and make sure the only option that is selected is Allow cluster network communication on this network. Click Ok.


Microsoft Windows Cluster

24. Click on Cluster Network 3. This is my iSCSI network.


Microsoft Windows Cluster

25. Right click on Cluster Network 3 and select properties. Make sure the only option that is ticked is Do not allow cluster network communication on this network. Click Ok.


Microsoft Windows Cluster

26. Click on Storage and you can see the Cluster Quorum Disk E: listed. Your Windows Cluster is now setup and ready to go.


Microsoft Windows Cluster

Disclaimer:
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.

  • Noel Brathwaite

    Are you sure you require a dedicated heartbeat NIC in Windows 2008 ?
    I am not sure you need to do this anymore.

    • You actually don’t need a dedicated NIC but I believe it’s better to have one to isolate the traffic.