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?

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.

Featured Post

With the increasing importance of apps & networks in both business & personal interconnections, perfor. has become one of the key metrics of successful communication. This ebook is a hands-on business-case-driven guide to understanding MySQL query parameter tuning & database perf

Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables.
Make a table:
Update a specific column given a specific row using the UPDATE statement:
Remove a set of values using the DELETE s…