SQL cluster group error

On a SQL 2005 cluster, drive D was deleted then restored on Node A but not on Node B--aka, the server cannot see drive D on Node B. Node A works great and SQL is running, but Node B is still looking for drive D in the cluster group and shows a fat read X for the group. There are no binaries or SQL files on drive D.

Will deleting the SQL group with drive D on Node 2 cause a problem for the Node 1 and for the SQL cluster in general?

Thanks
barnescoAsked:
Who is Participating?
 
DBAduck - Ben MillerConnect With a Mentor Principal ConsultantCommented:
When dealing with a Cluster Group it is there in the Cluster regardless of Nodes. Nodes participate in the cluster, so you cannot delete the Cluster Group on Node B because the Cluster Group is not ON Node B it is in a Cluster and Node B is a Node in the cluster.

When dealing with Drives in Clusters, you have to make the drive available to the Cluster which means that whichever Node the Group that contains that Drive can move to must have ability to bring that drive online.  If it cannot, you should remove the drive from the cluster group not remove the cluster group from a node.
0
 
x-menIT super heroCommented:
can you move the cluster group to node B?
0
 
barnescoAuthor Commented:
I can, but it doesn't automatically failover. I have start SQL server manually.
0
 
x-menIT super heroCommented:
so SQL does not depend on drive D?
0
 
barnescoAuthor Commented:
X-men, SQL does not depend on drive D.

Dbaduck, that makes sense and thanks for clarifying.
0
All Courses

From novice to tech pro — start learning today.