With VMWare do the VMDK files (virtual disks) have the ability to create multiple paths the the SAN controller? Allow me to provide context and background as to why I am asking.
I was recently on a project with Hyper-V and we were migrating SQL Server to a Hyper-V cluster. The customer had purchased a more powerful set of hardware for the hyper-V environment and the thought was, we are giving 2x the amount of hardware to our new SQL Servers, so we will get 2x the performance.
We fought issues for weeks upon weeks, and we finally found out that when using Hyper-V virtual disks (VHDX) files, the VHDX files have a limitation as to the amount of SCSI channels they can establish to the SAN controller. (I am not a SAN guy, so I am paraphrasing) We determined this to be true by adding a second data file to the SQL Server database and moving that data file to a new VHDX drive and the performed the backup in half the time. After speaking with Nutanix, they stated that Windows Hyper-V should directly attach to the LUNs therefore bypassing the hypervisor for the storage layer. The OS and C drive remain on the hypervisor with a VHDX file.
The VM architect stated that this was a problem with only Hyper V and the VMware does not have this problem of creating multiple IO paths from the VMDK files to the SAN controller. I am no SAN admin, but this is hard for me to understand as I think if all my SQL data files (*.MDFs) are inside a virtual container, there must be limitations on this container limiting the amount of IO my SQL data files get.
I am now in another project where the VMware architect has presented virtual disk to the SQL Server, so before I go down this same road, I just want to know if VMware does this better than Hyper-V and will actually allow multiple IO paths from the VMDK files to the SAN controller allowing my SQL data files to leverage parallel IO.
Thanks in advance experts!