Unable to configure enhanced replication with an error "A Generic error occurred in the vSphere replication management server. Exception Details "HBR not found for the selected cluster : Domain-C###"

Products

• VMware Live Recovery

Issue/Introduction

Symptom: 

• After upgrading vSphere Replication (VR) and Site Recovery Manager (SRM) from version 8.8 to 9.0.2, Enhanced Replication Mapping fails in Site Recovery UI. 

• Enhanced Replication Mappings show error for the Cluster mapped across DC and DR site : : Fault occurred while performing health check. Details: "A Generic error occurred in the vSphere replication management server. Exception Details: HBR not found for the selected cluster : Domain-C###"
  
  Steps: vSphere Client > Site Recovery Plugin > Open Site Recovery > View Details > Enhanced Replication Mappings > select DC or DR site, then "Run Test"
  


• "No target datastores are accessible from hosts that support enhanced replication." error seen while trying to add the VM for enhanced replication or while reconfiguring the existing VM using legacy replication to use enhanced replication.
  
  

  

Validation: 

• Hosts part of the Cluster which are mapped for replication are not registered on the "Replication Servers" tab.
  
  

Environment

VMware Live Recovery

VMware vSphere Replication

Cause

Note:  Enhanced replication requires vSphere Replication 9.0.x, vCenter Server 8.0 U2, and ESXi host 8.0 U2 or later.

• Hosts are unable to connect to the HBR broker endpoint therefore are not accessible to hms.

In "/opt/vmware/hms/logs/hms.log", we found below log entries -

2025-06-20 16:41:15.283 WARN  com.vmware.hms.hbrsrvuw.healthmonitor.HealthChecksWorkflow [tcweb-38] (..hbrsrvuw.healthmonitor.HealthChecksWorkflow) [operationID=a892bcd0-4144-4426-ab51-b721f6e139ae-HMS-4705044,sessionID=197F777F] | Throughput test is not supported with the current build.
2025-06-20 16:41:18.422 DEBUG com.vmware.hms.hbrsrvuw.healthmonitor.HealthChecksWorkflow [hms-main-thread-35018] (..hbrsrvuw.healthmonitor.HealthChecksWorkflow) [operationID=a892bcd0-4144-4426-ab51-b721f6e139ae-HMS-4705044,sessionID=197F777F, operationID=a892bcd0-4144-4426-ab51-b721f6e139ae-HMS-4705044,sessionID=197F777F] | Executing ping test for peer site '80de32cd-35ed-45db-8a85-50d9b4eed71d' and replication mapping '(hms.ReplicationMapping) {
   dynamicType = null,
   dynamicProperty = null,
   localClusterMoId = domain-c58,
   peerClusterMoId = domain-c34
}'.
2025-06-20 16:41:18.541 DEBUG com.vmware.hms.net.HbrAgentHealthMonitorService [hms-main-thread-35020] (..hms.net.HbrAgentHealthMonitorService) [operationID=a892bcd0-4144-4426-ab51-b721f6e139ae-HMS-4705044,sessionID=197F777F, operationID=a892bcd0-4144-4426-ab51-b721f6e139ae-HMS-4705044,sessionID=197F777F] | Ping test group configuration failed '(hms.PingGroupSpec) {
   dynamicType = null,
   dynamicProperty = null,
   groupId = PING-GID-FAILED,
   hbrBrokerEndpoints = (hms.HbrBrokerEndpoint) [
      (hms.HbrBrokerEndpoint) {
         dynamicType = null,
         dynamicProperty = null,
         ipAddress = 10.##.##.249,
         lwdPort = 31031,
         lwdsPort = 32032,

   targetHostId = NA,
   targetHostName = NA,
   groupConfigurationFault = (hms.fault.HmsMethodFault) {
      faultCause = null,
      faultMessage = null,
      originalMessage = HBR not found for the selected cluster: domain-c34
   }
}'.

Resolution

• Reconfigure VR appliance from both the sites and validate if the hosts are now registered on the "Replications Servers" tab under SRM UI.

Additional Information

Related Document : vmware-vsphere-replication-9-0.pdf