Link to home
Start Free TrialLog in
Avatar of jmachado81

asked on

SQL 2012 clustering

We have a pair of 2012 R2 servers clustered together with SQL 2012.  Recently when we attempt to attach a database and associated log file we get the attached error.  We are unaware of or even if any changes were made to this cluster, and there are no current cluster errors displayed.

We have found multiple articles stating this is a dependency issue but we are unsure where this dependency is missing?  SQL Server resource, Agent resource, disk resource, or all the above.  

We are going to failover the cluster to see if the behavior persists on the other node but I was hoping others had recommendations as to what this can be.
Avatar of jmachado81


And these storage disks are all listed under the resources of our SQL Server role and the status is Online.
this error genrally occur when drive is not having dependency with the SQL Server resource. Check this,
Add the dependency at the SQL Server resource under SQL Group.
While adding dependency SQL Server resource must be offline.
Once add bring online and now this will work.

have a look here:
Avatar of Vitor Montalvão
And these storage disks are all listed under the resources of our SQL Server role and the status is Online.
Can you post a screenshot with those dependencies listed?
Well the failover last night went miserable but we may have found the issue or one of them.  It appears that even though each node had the below local drives, somehow the I:\ became a shared clustered disk.  We did not view the I:\ drive in the cluster resources, however when i viewed the disk attributes it stated it was a clustered disk and it also stated that it was reserved in the disk management.

C:\ OS
I:\ sql installation files
P:\ pagefile

After one of the nodes were evicted we were able to clear disk attributes on both nodes so the I:\ was back online.  I think we are going to try to readd this node back to the cluster later.

How can a disk become a clustered disk if not part of the cluster resources?  We don't know how this came to pass...
It appears that even though the cluster is back online we still cannot add databases to the cluster (of one).  I have attached the screenshot of our SQL Server (other resources) dependency and our storage dependency.  All of our databases and log files are stored in their own volumes on an S:\ which is called "Mount_Point" which you can view in the screenshot, and they all have the same dependency.  The top-level S:\ drive or Mount_Points has no dependencies listed...only the LUNs (sub-directories holding mdf/ldf files) mounted to this drive have dependencies.
Your disk dependency is a File Server?
Anyway, I can't see that SQL Server is depending on the MountPoint resource.
The cluster has a File Server resource installed and its not pointing to a typical file server.  Should we add that S:\ or Mount_Point drive as a dependency of the SQL Server?  Are there any other primary dependencies we should review?
Avatar of Vitor Montalvão
Vitor Montalvão
Flag of Switzerland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for your assistance.  In additional to adding that top level drive, we also added each drive in which an mdf/ldf file was located as a dependency.  These resolved the errors in attaching a database to the server.