For the SAN part, I used the iSCSI target that is built-in to Windows Server.Ī feature enhancement in Failover Clustering for Windows Server 2012 and Windows Server 2012 R2 is that it supports an Asymmetric Storage Configuration. I used Hyper-V Virtual Machines to reproduce this issue in a lab environment. Note: The 20 GB drive is presented from the SAN and is not added to the cluster at this stage. All the other drives required for SQL are shared drives presented from the SAN.D drive for SQL binaries – each of the nodes has a dedicated “local” drive, presented from a Storage Area Network (SAN).C drive for the Operating System – each of the nodes has a direct attached disk.ContextĬonsider a 2 node SQL Server Failover Cluster Instance running on a Windows Server 2012 R2 Failover Cluster with the following disk configuration: Before that however, I would like to provide a bit of context relating to cluster disks, especially on Asymmetric Storage Configuration.
Now that we have all this information, let’s look at how you would resolve this specific issue we were facing.
Server 2012 run disk health code#
Additionally, this is what was in the cluster log – “failed to start service with error 2”:Įrror code 2 means that the system cannot find the file specified:Ī little bit of digging around reveals that this is the image path we are failing to get to: Would you suspect that storage is involved at this stage? In cluster events, there was the standard Event ID 1069 confirming that the cluster resource ‘SQL Server’ of type ‘SQL Server’ in clustered role ‘SQL Server (MSSQLSERVER)’ failed. This is what they observed:įrom the image above, it can be seen that all disk resources are online. discuss how the issue was resolved by removing the disks from clusterĪn attempt to move the SQL Server role/group from one node to another in a 2-node Failover Cluster failed.provide a little bit of context on cluster disks and asymmetric storage configuration.explain what the issue was (adding disks meant to be local storage to the cluster).They had internally transferred the case from the SQL team to folks who look after the Windows Server platform as they could not pick up anything relating to SQL during initial troubleshooting efforts. I paid a customer a visit a while ago and was requested to assist with a SQL Server Failover Cluster issue they were experiencing.
0 kommentar(er)
