Validating cluster resource name
It’s where we log critical, error, and warning events.
However, it’s not the only event log location that we write to.
Here we are again, delving further into Windows Failover Clusters.
This series has been following the construction of a Windows cluster and in this installment we’re going to layer SQL Server onto the Failover Cluster that we built in Part 3.
In the screenshot below, you do not see the SQL Server Agent in the list of available resources - only the SQL Server resource is available.
Start the SQL installation and follow the steps outlined below. You might want to change the way some of the steps are performed, like using different credentials for each of the SQL services.
While the SQL Server cluster resource group was successfully brought online after the DNS issue was fixed, I noticed that the SQL Server Agent was not listed as a resource type under the Other Resources section of the cluster resource group.
How do I manually add the SQL Server Agent to the cluster resource group?
As we discussed in the blog on creating a Windows Failover Cluster, it is most desirable to select the Run all tests option in the Testing Options screen, but since the storage I am using in my lab is not supported for Windows 2012 clustering I will be selecting the Run only tests I select option. If you find yourself testing or learning and need to limit the tests you will see the Test Selection screen, where I am deselecting the Validate SCSI-3 Persistent Reservation test. Once the cluster validation is complete click Finish to complete the cluster validation.
As long as there are no failures the SQL Server software can be installed.