laroberts
9 months agoNovice I
SQL within VMware
If we are setting up SQL within vmware using NVME vvols and NVME controllers on the VM, is there a reason to have your data/log/tempdb volumes on separate virtual NVME storage controllers (for reference: https://www.nocentino.com/posts/2021-09-27-sqlserver-vms-best-practices/#vm-configuration)? Or do those benefits not really translate over when doing NVME storage protocols?
- So, small update: I realized that my NVME vvol was not NVME at all. I'm on Purity v6.5.8 but NVME vvols aren't supported until v6.6.2 (I was confused because the storage endpoint is upgraded to VASA 5 but I guess it still doesnt support the NVME vvol logic until I get onto purity v6.6.2 and it auto added the NVME vvol I created to SCSI instead without me realizing). https://support.purestorage.com/bundle/m_release_notes_for_vmware_solutions/page/Solutions/VMware_Platform_Guide/Release_Notes_for_VMware_Solutions/topics/reference/r_flasharray_vasa_provider_version_by_purity_release.html|https://support.purestorage.com/bundle/m_release_notes_for_vmware_solutions/page/Solutio[…]r_flasharray_vasa_provider_version_by_purity_release.html But I still have the interesting performance difference of using PVSCSI controllers vs the vmware NVME controller (even though they are going over the same SCSI-FC vvol)