Upgrading vSphere from 6.7u3 to 7.0u2, any pitfalls with VBR10?

[cerberus]

Currently using VBR 10 to do B2D2T and also have replication jobs that leverage Veeam WAN accelerators.

Using most of the Veeam features for backups including san mode, CBT and fast-clone.

Looking to upgrade our production vSphere (ESXi and vCenter Server) from 6.7u3 to 7.0u2 due to some issues with Intel Ice Lake processors, from a Veeam perspective are there any known issues going to latest vSphere?

AFAIK the MoReF ID is preserved if we do VCSA appliance upgrade, so things should "continue" normally with CBT.

Should we be upgrading VBR 10 to 11 before or after vSphere upgrade?

Anyone done this recently? Would be interested in hearing what your experience was and if there are any pitfalls.

[Mildur]

You need V11 for vsphere 7.0u2.
So it‘s best to first upgrade veeam to the supported version, before upgrading your vsphere environment.
https://www.veeam.com/kb2443

If you wait 2-6 weeks, Veeam V11a will be GA. For the moment, it‘s in early available state:
https://www.veeam.com/kb4215

[cerberus]

Thanks for pointing that out, upgrading VBR to 11 first.

I had a read through the v11a changes and looks like they support it in production, will apply this as it also includes previous cumulative patches.