Migrating my VMware Microsoft SQL VM clusters to use vVols

saw your post there. Let me loop back with eng on this. Moving to a PM role sometimes saddens me as I dont have the time any more to dig into this myself... Let me get eng/solutions involved to take a look and figure this out

I got the answer from VMware engineering (it is possible), waiting on the specific step as a number needs converted. I will respond back when i get it

ive asked our eng to dig in a little so we can provide some english on how to do it

maybe joe or ttodd have some more up to date stuff but it should still be correct

• https://www.codyhosterman.com/2018/07/powercli-and-vvols-part-ii-finding-vvol-uuids/|PowerCLI and VVols Part II: Finding VVol UUIDs • https://www.codyhosterman.com/2018/08/powercli-and-vvols-part-iii-getting-vvol-uuids-from-the-flasharray/|PowerCLI and VVols Part III: Getting VVol UUIDs from the FlashArray • https://www.codyhosterman.com/2018/08/powercli-and-vvols-part-iv-correlating-a-windows-ntfs-to-a-vmdk/|PowerCLI and VVols Part IV: Correlating a Windows NTFS to a VMDK

Thank you codyhosterman, I'll take a look and see if I can get that to work in my environment also.

Hey sorry to piggy back off this thread, but (unless I'm mistaken) it seems like something has changed when it comes to using the UUID to script finding a drive in windows (grab serial number) -> find vmdk (match to UUID) -> find pure volume now that I'm testing out using NVME/FC vvols and NVME controllers. Is there something I'm missing when it comes to these new serial numbers with NVME controller based disks on NVME vvols?: https://www.reddit.com/r/purestorage/comments/1earfn3/dealing_with_nvme_disk_serial_numbers_on_vmware/

Interesting...(ChatGPT) ```Original String: 6000C2943f1e236d4da0b44c877cb0d9 Transformed String: 4DA0B44C877CB0D9000C29643F1E236D Steps to Analyze the Transformation Split into Segments: Let's try splitting both strings into 8-character segments for better readability. Original String: 6000C294 3f1e236d 4da0b44c 877cb0d9 Transformed String: 4DA0B44C 877CB0D9 000C2964 3F1E236D Compare Segments: Compare segment 1 of the transformed string to all segments of the original string: 4DA0B44C matches 4da0b44c in the original string (case insensitive). Compare segment 2 of the transformed string to all segments of the original string: 877CB0D9 matches 877cb0d9 in the original string (case insensitive). Compare segment 3 of the transformed string to all segments of the original string: 000C2964 doesn't directly match any segment, but we notice 2964 is part of the original string 6000C294 with some reordering. Compare segment 4 of the transformed string to all segments of the original string: 3F1E236D matches 3f1e236d in the original string (case insensitive). Observations: Segments 1, 2, and 4 in the transformed string are direct matches (ignoring case) to segments in the original string. Segment 3 in the transformed string 000C2964 seems to be a reordering of part of the original string 6000C294.```

_"In the case of SCSI , VM gets NAA ID itself in inquiry page 83h so it's a straight comparison. In the case of NVMe , NAA IDs are not supported, so it is converted to NGUID as per NVMe spec, if you apply the reverse conversion to get NAA ID, step one should still work. You can refer to section 4.3.5 of NVMe base specification."_