Attempting to add the Veeam Proxy VM to a replication job fails with the error:
"This virtual machine is not configured for replication"
Other virtual machines can be successfully added to vSphere replication without errors.
VMware Live Site Recovery 9.x
vSphere Replication (VR) does not support virtual machines with custom disk types or non-standard file extensions (like .mvmdk or potentially Veeam's proprietary snapshot/disk format) for replication.
Cause Validation :
Log path : less /opt/vmware/support/logs/hbrsrv.log
2025-11-10T11:49:41.797+05:30 verbose hbrsrv[01203] [Originator@6876 sub=Host opID=hs-init-38074a76] Host:#####: /vmfs/volumes/3###af -> 36####-9####af (name Ve#####p_M#####M-01.c##p.m####ra.c_) accessible false 2025-11-10T11:49:41.843+05:30 verbose hbrsrv[01229] [Originator@6876 sub=Host] Host: host-26 Datastore: /vmfs/volumes/3###a4af -> 363####a4af (name V#######_M####M-01.####.######a.c_) accessible false 2025-11-10T11:49:41.874+05:30 verbose hbrsrv[01229] [Originator@6876 sub=Host] Host: host-26 Datastore: /vmfs/volumes/36#####a4af -> 36####8a4af (name Ve####kup_###-01.###.m####a.c_) accessible false
Contact Veeam Support to confirm whether the .mvmdk disk format is required for the Veeam Proxy VM.
Do not configure the Veeam Proxy VM for vSphere Replication unless the disk format is fully supported.
VMs using unsupported disk extensions (such as .mvmdk) should not be added to replication tasks, as this may lead to failed replication attempts