We took a little more time with the regression testing, because we identified one other "last minute" major API change in vSphere 7 which broke our other product (Veeam Management Pack). So we came back to looking closer at the corresponding functionality, but luckily this particular change did not impact Veeam Backup & Replication at all.
At this point, we have finished the regression testing for all standard configurations, and found no other major issues except
the one I already mentioned above. We also validated the way to address this issue relatively quickly by re-using the code we already have for VMware VSAN support.
As such, our current plan is as follows:
1. We will deliver the "quick" fix for the identified issue as a part of the Cumulative Patch 2, so that we could declare official vSphere 7 support. This fix is not going to be "ideal", as it reduces performance of the impacted operations, but it does the job and can be delivered fast, since it reuses the existing already tested code, allowing us to ship the patch fast (early-mid May).
2. We will deliver the "ideal" fix as a part of v11. We already know how to do it right, but this will require significant changes and full retest of the impacted functionality.
