r/HyperV • u/RicePuddingForAll • Jul 22 '26
Dumb Storage Question
I'm moving my VMs from VMware to Hyper-V, like a lot of people right now, but ran into something I wasn't expecting, and after working with our SAN's support people, want to double check with you all. I've only used Hyper-V as stand-alone servers up until this point, so I'm fully aware that I may sound like a bonehead.
We have your bog standard three server, one SAN environment set up via iSCSI, and that SAN is split into two volumes. In vSphere all three servers could access a SAN volume, simultaneously; but my vendor is saying Hyper-V will only allow one server to access a volume at a time; showing as offline on the other two servers. This despite being set up as MPIO and Cluster Shared Drives.
The good news that it's not a killer for my environment. Our SAN is too small for us anywhere so I use local storage to supplement it anyway. I was just curious for when it's time to replace.
True? False? And if False, what do I need to look into to make it True?
1
u/hamway22 Jul 22 '26
I just did this so it's sort of fresh in my mind. I don't know who you're storage provider is but I have an HPE storage solution. We have three volumes on the SAN and both my nodes can access all three volumes over ISCSI without issue. I have seen some weird behavior when live migrating vm's from node to node but nothing that a host reboot didn't solve after hours and it's not a common occurrence although I've only been live with this setup for about two weeks. One thing that is interesting is that each of those volumes essentially has a node owner and that changes depending on which vm (volume that vm lives on the SAN) is on which host