Replications get paused automatically in VMware Cloud Director Availability
search cancel

Replications get paused automatically in VMware Cloud Director Availability

book

Article ID: 393183

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • You can press resume on the VMs under “All Actions” and briefly have the option to press “Sync”. However, this fails immediately and then jumps back to the “Pause” state.

  • In /opt/vmware/h4/replicator/replicator.log on the destination site replicator you can see errors like:

    2025-02-27 22:02:44.391  WARN - [04955f6a-####-####-####-###########] [hbr-poller1] c.v.h.c.e.ExceptionConversionService     : Unable to convert exception. Using fallback exception instead.

    com.vmware.vim.binding.hbr.replica.fault.GroupDiskMismatch: Error for (groupId: "H4-f3a5238e-####-####-####-############"): The set of disks doesn't match.; Disk set check invoked with 0 disks, server has 2 disks; Querying server state for group H4-f3a5238e-####-####-####-############

  • In /var/log/hostd.log on the ESXi host where the source VM resides you can see errors like:

    2025-04-03T09:18:36.079Z error hostd[2100105] [Originator@6876 sub=Hbrsvc] ReplicationGroup get-server-state request failed, will retry (groupID=H4-f3a5238e-####-####-####-############) : The set of disks on the replication server doesn't match
    ...
    2025-04-03T09:18:23.471Z info hostd[2100839] [Originator@6876 sub=Hbrsvc opID=UI-c545f0f0-####-####-############-#####-##-##-##-##-##-####-####] ReplicatedDisk destroyed (diskID=H4D-4b46d324-############-####-####-############) (vmID=353)
    2025-04-03T09:18:23.471Z error hostd[2100839]: groupExist GroupID H4-f3a5238e-####-####-####-############ already owned by VM 001, deferring VM 002

 

Environment

VMware Cloud Director Availability 4.x

Cause

This issue occurs because there are two VMs in the source site with the same replication ID.

Resolution

To resolve this issue, contact Broadcom Support and note this Article ID (393183) in the problem description. For more information, see Creating and managing Broadcom support cases.