I recently transitioned from VMware to Hyper-V, and while my two DELL servers were connected to the DELL SAN using SAS cables in VMware, it seems Hyper-V doesn't support this setup. My production VMs are currently stored on the SAN, so I want to ensure everything stays intact, but I can restore from backups just in case things go wrong. I'm looking for guidance on how to change my connection from SAS to iSCSI since the SAN is directly linked to the DELL servers via SAS cables.
4 Answers
It's odd that you say Hyper-V can't use SAS since it's built to support it, especially with models like the Powervault MD series designed for that purpose. Are you certain about your SAN's configuration? Some might be SAS-only, which could explain the confusion.
Just a thought—ensure that your SAN actually includes 10Gb iSCSI ports, because if it doesn't, you'll need to rely on the SAS setup. And remember, iSCSI operates over Ethernet, while SAS allows for direct connections.
If your SAN has enough 10Gb iSCSI ports, you do have the option of setting up a direct Ethernet connection! Just make sure both servers are plugged into the same switches.
You don’t necessarily have to switch to iSCSI! Hyper-V can use SAS with the right setup. First, make sure you install the MPIO feature on all your hosts and activate the SAS settings in the MPIO configuration using Server Manager. A reboot is essential after these changes. Once everything's rebooted, you should be on track to initiate the CSV setup without switching to iSCSI.
I’m working with the DELL PowerVault ME4024, connected to DELL PowerEdge 740xd servers. I'm in the cluster verification phase, and it seems like the shared disk isn't being recognized properly. I’ve read Hyper-V typically supports SMB, Fiber Channel, and iSCSI for connections.