Unable to reverse replication for the virtual machine in DRaaS

Products

• VMware Live Recovery
• VMware vSphere ESXi
• VMware Cloud on AWS

Issue/Introduction

Symptoms:
A group of VMs, protected by vSphere Replication, have been successfully migrated to the VMware Cloud (VMC) on Amazon Web Services (AWS) SDDC using Site Recovery Manager (SRM) as Disaster Recovery as a Service (DRaaS).

Issue is seen while trying to reprotect the VMs.

User sees the error "Operation Failed
Unable to reverse replication for the virtual machine <VM-Name>. Cannot find vSphere Replication Server for replication <VM-Name>."

The site pairing for both SRM and vSphere Replication still show as connected.

The on-premises site, "Replication Servers" tab shows some VR server (HBRsrv) was disconnected from vSphere Replication Management Service (VRMS aka HMS).

/opt/vmware/hms/logs/hms.log:
2020-04-27 16:05:14.020 ERROR hms.net.hbr.ping.svr.52ae00be-dd3d-1206-693f-fe72661e80c6 [Ping Thread for server 127.0.0.1:8123] (..net.impl.VmomiPingConnectionHandler)  | Ping session on server 127.0.0.1:8123 failed: (vmodl.fault.SecurityError)

Resolution

Login to the vSphere Replication appliance command line on-premises and restart HMS process with the following command:

systemctl restart hms

Additional Information

Troubleshooting Disaster Recovery as a Service (DRaaS) KB 78941