The case was specific to NFC connections, and my understanding is that based on the feedback from VMware that Veeam have been checking their NFC client settings. Obviously we cannot discuss the particulars of another customers case with you, but we can confirm that SR 18797316305 has been closed since December and there is no action pending on the VMware side. Specifically SR 18797316305 was referenced in this forum as "an open ticket on vmware side for this issue". Reviewing the Veeam Support Forums I see that an incorrect message is being given to Veeam customers, that this is a single 'known issue' which is being actively worked on by Veeam and VMware. It would perhaps be better to say that "Veeam client connections to the vSphere API are failing for reasons that Veeam have been unable to determine, when stress testing ESXi 6.5 U2 with high load." I have no indication that the statement "there is a major regression in ESXi 6.5 U2 code that makes the vSphere API fail randomly during high host CPU load periods" is factually correct. VMware is currently troubleshooting this bug, and fixing one will most likely require the new ESXi 6.5 U2 build issued."
However, there is a major regression in ESXi 6.5 U2 code that makes the vSphere API fail randomly during high host CPU load periods, consequently impacting a variety of Veeam Backup & Replication functionality.
#VSPHERE CLIENT 6.5 SUPPORT UPDATE#
This update introduces preliminary support by addressing all outstanding U2-specific compatibility issues that can be managed from the Veeam side.
0 kommentar(er)
