so i opened a case at vmware and got a reply, which again leave me kind of frustrated and not knowing if or when we can expect a solution...
"VMware vSphere 6.5 U2. This update introduces preliminary support by addressing all outstanding U2-specific compatibility issues that can be managed from the Veeam side. 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. VMware is currently troubleshooting this bug, and fixing one will most likely require the new ESXi 6.5 U2 build issued."
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.
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."
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.
vmware-vsphere-f24/vsphere-6-5u2-suppor ... 1-135.html
Specifically SR 18797316305 was referenced in this forum as "an open ticket on vmware side for this issue".
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.
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.
While we cannot rule out the possibility that Veeam have another ticket open, it's possible that there is some confusion internally at Veeam regarding the status of their investigation and that the people posting updates on the forums have not been correctly informed.
Note that there is a limit on the maximum number (25) of NFC connections in ESXi 6.5 Update 2 which does not apply to ESXi 6.7 so Veeam's note that "the issue is resolved if you move to 6.7" would indicate to me that they have confirmed this is an issue in their NFC client settings.
Our assumption is that Veeam will correct this in a future update on their side.