Creating a Windows Failover Cluster in Server 2016

Creating a Windows Failover Cluster in Server 2016

Creating a Windows Failover Cluster in Server 2016

((SQL Failover Cluster in VMware using VMDK’s Part 1) Other Parts:

Creating Shared VMDK’s in vSphere 6.5 for Windows Clustering

If you did the first exercise, you should have your VMDK’s ready to add to your Failover Cluster. Before we set up a Windows Failover Cluster, lets configure the disks in the Guest Operating System. In most circumstances you are going to Initialize the disk using MBR (Unless your volumes are larger than 4TB) and create a New Simple Volume for each disk. Since these disks must be thick provisioned due to sharing limitations with VMDK’s, don’t go nuts with the disk size.

Now that the disks are set up, it’s time to set up your Failover Cluster. You should have an IP address and a cluster name picked out. Consistency in your environment is the important part.

Cluster Name: vBob.chickenwings.com 10.1.1.100

Vms: vBob01.chickwings.com 10.1.1.101, vBob02.chickenwings.com 10.1.1.102

INSTALLING Windows Failover Cluster

Open Server Manager, Select Manager

Select Role-based or feature-based installation

Select your server from the server pool

Skip Server Roles by hitting Next to get you to Features

Under Features, check Failover Clustering

-Add Features

Now open Failover Cluster Manager (Under Windows Administrative Tools)

Validate the Cluster repeatedly while fixing errors until it passes with no errors.  It will look like this if you scroll to the bottom (leave a comment if you need help with this):

Now we will click Create Cluster. Now enter your server, it’s o.k. to create a one node cluster to start, we can add another node later.

Name your cluster and set the IP. I’m using 10.1.1.100 as well as the cluster name I discussed before “vBob”.

Mission complete. It might complain about witnesses and shared disks, but that’s o.k. I don’t mind.

Now I’m going to take a trip into the cluster storage and add my shared disks. I’m building a SQL server here, so I have a few.

Next you can configure your quorum settings if you don’t know what this is, here is information on what it is, and how to set it up. This is a fantastic document. https://docs.microsoft.com/en-us/windows-server/failover-clustering/manage-cluster-quorum

You now have a one node fail over cluster!! You Can add a second node at any time. I’m choosing to personally do this later. Next up, I’m going to install a one node SQL failover cluster to get started with SQL Clustering, using SQL 2016sp1 on Windows 2016. Part 3 coming up shortly!

EDIT NOTE: If you are going to create a SQL Cluster, you may want to give the computer object for the cluster permission to create computer objects on your Computer-OU or the installation may have issues.

 

 

Leave a Comment