Last week my colleagues and I tried to install a failover cluster on Server 2012. It wasn’t the first time, but this time we did it for an upcoming production SQL Server Installation. Here are some hint’s you should consider and steps you must go trough when setting up a cluster.
Naming Convention for this Article
Nodes: SRV01c1, SRV01c2
Cluster Name: SRV01Win
SQL Cluster Name: SRV01
Computer Accounts for the Cluster, on…
- DO NOT PREPARE accounts for the cluster
- just move them to the right OU afterwards
- Prepare AD Accounts like SRV01, SRV01win, SRV01dtc, SRV01c1, SRV01c2
- disable the prepared accounts in AD
- logged on user must have full rights on accounts to join domain
- get IP addresses, one for each hostname
- Install Windows 2012 on SRV01C1 and SRV01c2
- connect DTC & Quorum disks to c1 & c2
- Validate Cluster, check things and details like Network Adapter bindings and order
- create Cluster SRV01win using Failover Management GUI
- set Quorum to Node & Disk majority (make sure you’re using the right disk for that)
- if necessary, install DTC (you only need that for active/active clustering)
- check Eventlog for errors and solve them
ISSUE: DNS FQDN missing / could not register
After setting up the Windows Failover Cluster using the Failover Clustering Feature GUI, the Installation ended successfully but we weren’t able to ping the Host SERVER-WIN. Everythin seemed to be okay, but Eventlog listed this errors:
*** ERROR1: Eventid 1228 ***
Cluster network name resource ‘Cluster Name’ encountered an error enabling the network name on this node. The reason for the failure was: ‘Unable to obtain a logon token’. The error code was ‘1326’.
You may take the network name resource offline and online again to retry.
*** ERROR2: Eventid 1196 ***
Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. .
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
*** ERROR3: Eventid 1205 ***
The Cluster service failed to bring clustered service or application ‘SQL Server (MSSQLSERVER)’ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
After troubleshooting a while and asking Google various questions, we tried to solved that using ipconfig /registerdns on the active node. This didn’t help, but some minutes later we found that there’s a quick and easy way to let Windows re-try the IP registration by just telling the Cluster GUI “repair” on the Host’s name:
Set up SQL Server
- start SQL Setup from installation media / ISO file
- do not install SQL as usual, choose the cluster installation option
- Provide setup neccessary information like Clustername “SRV01”, IP and the Features you want to install
- if everything is successful, repeat the installation on node 2; setup will now detect the installed features and repeat the installation the same way as on node 1
Setup Test Cluster using VM’s
If you’re planning to setup a Cluster, you maybe like to test everything first. There’s a VMware setup guide on Windows Clustering using VM’s in vSphere  and their limitations . If you decide to prepare a test environment with two VM’s, consider the following advantages and disadvantages.
- no additional SAN Storage / LUN needed
- no extra SCSI connection must be built up
- works the same way like real
- VM’s using physical SCSI are not able to be vMotion’ed to another Host