Vmware esxi 6.7 resource pool12/28/2022 ![]() ![]() VMware vCloud Director 9.1 support is also a part of Update 3a, at what we call "compatibility" level. I will keep posting updates on VMware investigation of the API issue in the main topic about vSphere 6.5 U2 support. ![]() It's just that we are unable to support it officially, because any significant load spike will cause vSphere API to start failing randomly, consequently impacting most of the Veeam functionality. And in general, Update 3a will make U2 "safer" to use in average (not heavily overprovisioned) environments which already upgraded to one. However, Update 3a does introduce "preliminary" U2 support by fixing all outstanding U2-specific issues (such as hot add transport failing with certain proxies), so in theory the newer U2 build fixing the API issue should be supported automatically – so long as it does not break something else, of course. VMware vSphere 6.5 U2 will NOT be officially supported with Update 3a due to the previously discussed vSphere API regression introduced by U2 and impacting environments with heavy host load. But this should not come as a surprise, as it's quite traditional for VMware to release new functionality this way (remember no snapshot support for Fault Tolerant VMs originally). This is due to lack of VM snapshot support for such VMs in vSphere. But those of you who like to be on the cutting edge with new vSphere functionality, please be aware that you won't be able to backup VMs with virtual NVDIMM devices present, or with virtual disks residing on PMem datastores. VMware vSphere 6.7 will be fully supported with no known issues or limitations from Veeam perspective. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |