I work for an IT company that just recently signed a client that uses a clustered Hyper-V environment running on Windows Server 2008r2, and uses Shared Cluster Storage or Shared Volume. The setup seems very strange to me. They are configured in a fail over cluster, and both Hosts have their own servers running on them. They both store their VMs at C:\ClusterStorage\Volume1, which is really an iSCSI connection to a SAN.
On Host1 you can see the 7TB drive in Disk Management and it shows as online, but there are no drive letters or folder path assigned to it. In Failover Cluster Manager, you can see that Host1 is the owner. Host1 also holds the Quorum drive (I
do believe it was on Host2 before)
On Host2 you can see the 7TB drive in Disk Management but it shows as offline, and of course no drive letter or path assigned to it.
Both hosts use this volume, and somehow it is mapped to C:\ClusterStorage\Volume1. Is this how a normal Hyper-V storage cluster looks and works? We are able to move servers from one host to the other no problem, and creating a file or folder on one C drive shows up on the other. Both Hosts have been up for over 390 days, and im wondering if something was changed and removed and when we reboot the hosts if they are going to lose their mapping to the shared volume, or is this is really configured somewhere else like in either Hyper-V manager or Failover cluster manager that I am just not seeing
Thanks