[DRAAS] Vsphere Replication synchronization fails for VRM group when HCX is configured
search cancel

[DRAAS] Vsphere Replication synchronization fails for VRM group when HCX is configured

book

Article ID: 323269

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

To explain the cause of the error and how it will be remediated.

Symptoms:

In Site Recovery Manager (SRM), after executing a recovery plan, the following error is seen:

"VR synchronization failed for VRM group <group Name>. No host can be used to access datastore path '[WorkloadDatastore] xxxx.vmdk'." 


Cause

When a re-protect is executed, a connection is made to all hosts which have access to the datastore.
If HCX is deployed within the environment and configured for vMotion, an HCX Mobility Agent is seen. This may also be referred to as the HCX Dummy Host.
The HCX Mobility Agent does not have access to the datastore and results in the connection being retried.

Resolution

This is fixed in an upcoming release of SRM.

Workaround:
If supported by your use case, you may remove the vMotion Service from your HCX Service Mesh. This will remove the Dummy Host which is used to facilitate the vMotion transfers. Other HCX services will not be impacted.
The steps can be found here: Create or Edit a Service Mesh

Additional Information

SRM: Reprotect Virtual Machines



Impact/Risks:
The re-protect action will fail.