2008 R2 Dual Node Failover Cluster Storage Access Problem

We have 2 x DL380 G7 connected to a HP P2000 in a MS Hyper-v Failover Cluster Configuration for Highly Available VMs.

Setup as follows:
MS iSCSI Initiator on each Node
MS Failover Cluster manager on each Node
SCVMM 2008 R2 on each node
Q:\ Quorum is 500MB in size
CSV is 2.3TB in size
HP P2000 has 2 controllers with 4 ports each. We are using ports A1 and A3 and B1 and B3 for the SAN traffic. Dedciated NICs on each server
Dedicated Cluster Hearbeat using a Crossover cable
Dedicated NICs for the Physical & Hyper-V traffic

This has been operational for 6 months but then a severe power cut upset the complete set-up. After power was restored the CSV on the SAN was offline to both nodes until we ran a Powershell command on Node2

"clear-clusterdiskreservation -disk3"

This brought it online but neither Nodes could access the CSV, only the Quorum was accessible.

After 4 hours of reboots and "fettling" we destroyed the cluster and rebuilt it.

The result now is that Node 1 has the Quorum and can access the CSV c:\clusterstorage\volume1 no problem. Vms are back online and running on Node1.
Node 2 CANNOT access the CSV and when you browse to c:\clusterstorage\volume1 it is empty.

Main error within cluster manager is:

Cluster Shared Volume 1Volume1" (Cluster Disk 2) is no longer accessible from this cluster node because of error "ERROR_CANT_ACCESS_DOMAIN_INFO (1351)".

Research suggests changing the cluster service to Automatic Delayed Start which has had no effect.

Lots of research and attempts to fix the issue have resulted in nought. Problem is that the servers are live and in use by one of our clients so before they have any further downtime we must be certain of a fix, gulp!

Attached are 2 grabs showing the status of disk management on each Node1.
Cluster logs are available.

Anyone got any ideas on where to start?
Node1.JPG
Node2.JPG
robtheplodAsked:
Who is Participating?
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
In my experience the disks that are shared between cluster nodes MUST be the same number.

Disk 0 = OS
Disk 1 = Quorum
Disk 2 = VHD/VHDX Storage

What the chicken is that QuikStor doing there? Get rid of it. Run your Cluster Validation Wizard again.

You will probably have to reboot both nodes to get the disks to line up. But, line up they must.

Philip
0
 
robtheplodAuthor Commented:
Thank you for the advice Philip.
We will make the changes and will let you know the result.
0
 
robtheplodAuthor Commented:
Thanks Philip, you were right on the money. The cluster shared volume is now available to both nodes after removing the Quickstor and rebooting both nodes.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Excellent. :)

Philip
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.