17.03.2021 · this post. Hi, after upgrading vCenter to 7.0 U2 I am having problems with linux hot add proxies. I am receiving "vmdk has been skipped due to an unsupported type (independent disk). All of the servers above only have dependent disks. Then the disk get stuck on the hot add proxy and I have to remove the mapping manually.
12.02.2018 · The vSphere versions indicated include related patches (e.g., 7.0 U1a, U1c, etc.). More information A list of Veeam Backup & Replication version and build numbers can be found on Veeam KB 2680
17.03.2021 · Just got the first warning after upgrading the VCSA to 7.0U2 last night: "Your vCenter Server API version is higher than the version this product build has been tested against, which may cause issues with some functionality. Please refer to Veeam KB2443 for vSphere version support information. This warning will not be logged again."
09.03.2021 · With the release of vSphere 7.0 U2, we have enabled NFS array snapshots of full, non-cloned VMs to not use redo logs but instead, use the snapshot technology of the NFS array in order to provide better snapshot performance.
09.06.2021 · It is just, if you do update vCenter to version 7.0.2.00200, you get a warning in Veeam B&R: Your vCenter Server API version is higher than the version this product build has been tested against, which may cause issues with some functionality. Please refer to Veeam KB2443 for vSphere version support information.
07.05.2021 · The long-awaited patch for Veeam Backup&Replication v11, which brings support for vSphere 7.0 U2, has been released. https://www.veeam.com/kb4126 It's important to note that CDP won't work with 7.0 U2 as there's a driver signing issue. So if you're working with Veeam CDP then you still should wait before updating.
Below are the information of lab environment. Lab Environment HQ Site VMware vCenter 7.0 U2 Appliance VMware vSphere 7.0 U2 Veeam Backup and Replication v11a DR ...