Issue with Replication Post VMWare 7.0 on DR Site

[stfconsulting]

Veeam Support - Case # 05674725

Hello I am wondering if anyone has encountered this before. We are have a client that we updated a single VMWare Host in DR Site from VMWare 6.7 to VMWare 7.0 U3. We are running Veeam 11.0.1.1261 P20220302. After the VMWare host update some of the jobs are failing with the error. Cannot replicate disk SERVERNAME_1.vmdk because its capacity was reduced (System.Exception). We attempted to remove the snapshots on the remote VM and still failing. Some of the VMs in various jobs are working without issue so we are baffled by what is happening.

[stfconsulting]

We figured out what happened. Somehow when the VMs got migrated back to the host that was upgraded to VMWare 7.0 the identifier that Veeam uses for replica seeding got completed mismatched. So Veeam thought that it was replicating to the correct VM however it was trying to replicate to a completely different VM.

To fix this we removed the replica mapping in the seeding configuration and re-added it with the correct VM.

This is either a bug in VMWare’s registration of the machine after it came back to the host after the upgrade.

OR a bug in Veeam’s mechanism for how it determines the identity of a VM in the replica seeding configuration.