Setting Up SMB3 NAS Storage for Hyper-V Cluster Shared Volu
Posted: Mon Jul 28, 2025 7:19 am
Not sure if this is possible or if I'm very wrong.
3 server configuration: 2 HyperV Hosts (almost the same)
1 storage server with an HP disk enclosure added
This is how I have it set up right now:
LAN network that all computers (10.10.200.x) can connect to
The two machines are connected by a 10.10.102.x network grouped together.
All servers can connect to the storage network (10.10.101.x).
This lets me use SMB3 Multipathing; it's pretty much the closest thing I can get to a SAN without buying one.
VMs work fine on Cluster node 1, but I can't move one from node 1 to node 2; it just doesn't show up.
Then I tried to move the VM to Node 2 by hand and saw this in the cluster event logs:
The cluster resource "Virtual Machine Configuration AZCC-EX02" failed in the job "AZCC-EX02," which is a virtual machine configuration. '0xb7' was the error code, which means "Cannot create a file when that file already exists."
I believe that because I never set up a Cluster Shared Volume, only one node can manage certain VMs, which is a problem.
Can I configure an SMB path (hosted on a storage server that acts like a NAS) as a Cluster Shared Volume for my Hyper-V cluster? If so, how do I make this storage appear as an "available disk" in Failover Cluster Manager so it can be added as a CSV?
3 server configuration: 2 HyperV Hosts (almost the same)
1 storage server with an HP disk enclosure added
This is how I have it set up right now:
LAN network that all computers (10.10.200.x) can connect to
The two machines are connected by a 10.10.102.x network grouped together.
All servers can connect to the storage network (10.10.101.x).
This lets me use SMB3 Multipathing; it's pretty much the closest thing I can get to a SAN without buying one.
VMs work fine on Cluster node 1, but I can't move one from node 1 to node 2; it just doesn't show up.
Then I tried to move the VM to Node 2 by hand and saw this in the cluster event logs:
The cluster resource "Virtual Machine Configuration AZCC-EX02" failed in the job "AZCC-EX02," which is a virtual machine configuration. '0xb7' was the error code, which means "Cannot create a file when that file already exists."
I believe that because I never set up a Cluster Shared Volume, only one node can manage certain VMs, which is a problem.
Can I configure an SMB path (hosted on a storage server that acts like a NAS) as a Cluster Shared Volume for my Hyper-V cluster? If so, how do I make this storage appear as an "available disk" in Failover Cluster Manager so it can be added as a CSV?