In Part 1 we have prepared servers and underlying network for the Failover Cluster installation. By now we are in the following state:
Failover Cluster is a Windows feature, so we just need to enable/install it:
Wizard will ask for a few configuration parameters.
First, we need to select nodes participating in a cluster:
Then we can give cluster a name and assign IP addresses that will be used by the Cluster itself.
As you can see the above IPs are the second IPs of the first interfaces configured/allowed preveously through the Amazon.
We do not need a shared storage, therefore we can just finish this wizard.
As a result we should see an operational windows failover cluster with two nodes:
When Cluster was established it also needed to create an A DNS record for the Cluster name – CLUSTER2 in my case. Cluster also modifies this A record every time resource goes from one node to another because IP address is changing. If you go to the DNS you won’t see a record for the Cluste name eather:
What I have discovered is that having a secondary DNS set to Amazon creates this issue. Making sure that there is only AD DNSes configured solved the issue. The record was automatically created and modified next time the cluster resources were moved to another node.
We need one more thing – we need a Quorum to make this two node cluster a failure awair.
File share witness will do the job. I’m gonna use my Domain Controller for that.
I’ve created a shared folder C:\Cluster and gave the “Full control” NTFS permissions to the cluster name – CLUSTER2$:
Now we can point our cluster to that share:
As a result we end up with the following configuration: