Share via

Have a clustered Hyper-V setup and storage volumes do not seem to match across the two hosts

Anonymous
2024-02-29T20:30:19+00:00

We are using an HPE Proliant setup. Two DL360 Gen 10s and a Proliant SAN that they use for their storage. We have two LUNs carved out on the SAN and both hosts are initialized and connected to both LUNS. We have Windows Server 2019 running Hyper-V on both hosts and the data attached. We have this setup in a failover cluster so the storage presents as C:\ClusterStorage and inside that main folder you have Volume 1 and Volume 2. On host 1 these Volumes are visible and accessible and contain virtual machine disks. On server two, there is also a Vol 1 and Vol 2. The strange thing is when you get to Volume 2 on server 2. Volume 2 says it is a file folder. It contains 3 virtual machines that belong to server 2 as far as the cluster is concerned. However, when viewing Vol 2 on server 1, it also contains virtual machine drives that belong to server 01, but you cannot see the ones from Vol 2 on server 02. However, in volume 1 on both servers it matches, the same virtual machine files on server 1 vol 1 exist when you look at the cluster storage volume 1 on server 2. I've also noticed vol 1 on both, and vol 2 on server 1 all say mounted storage. Vol 2 on server two says file folder. Can someone help me understand what would cause this? I am fairly certain I'm supposed to see the same thing in both volumes since they are clustered and use the same storage. I am assuming I should see the same list of virtual machine files on both servers for both volumes. It should match across. Or am I assuming incorrectly? The screenshots below are side by side shots of both servers.

Windows for business | Windows Server | Storage high availability | Clustering and high availability

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-01T02:52:04+00:00

    Hi Justin,

    Hope you're doing well.

    In a properly configured Hyper-V failover cluster with shared storage, you should indeed see consistent views of the shared storage across all nodes in the cluster. Each node in the cluster should have the same access and visibility to the virtual machine files on the shared volumes.

    Here are some things to check and consider troubleshooting the inconsistency you're experiencing:

    1. Run the Failover Cluster Validation tool to check for any configuration issues.
    2. Check the Storage configuration.
    3. If Cluster-Aware Updating is in use, ensure it's not causing disruption during updates.
    4. Ensure that the file systems on the shared volumes are consistent. Run a file system check if needed.
    5. Ensure that both nodes are running the same version of Windows Server 2019 with the latest updates and patches.

    Best Regards

    0 comments