The requested resource was not found error encountered when reviewing a replication in VMware Cloud Director Availability
search cancel

The requested resource was not found error encountered when reviewing a replication in VMware Cloud Director Availability

book

Article ID: 408874

calendar_today

Updated On:

Products

VMware Cloud Director Availability - Disaster Recovery 4.x VMware Cloud Director Availability - Migration 4.x

Issue/Introduction

  • When reviewing a replication in VMware Cloud Director Availability, an error similar to the following occurs:

    The requested resource was not found

  • Warnings similar to the following are found in the replicator.log (/opt/vmware/h4/replicator/log) that reference the replication group ID for the replication:

    2025-08-27 15:24:54.253  WARN - [########-####-####-####-############] [hbr-poller1] c.v.h.r.m.hbr.HbrGroupCollector          : The following replications in our internal state are unknown to hbrsrv: [Hbr.Replica.Group.H4-########-####-####-####-############, ...

Environment

VMware Cloud Director Availability 4.7.3

Cause

The underlying vSphere Replication information is missing from the replicator even though the VMware Cloud Director Availability replicator service believes that it owns the replication. One potential cause for this is a failure to switch a replication from one replicator to another, as can be performed when placing a replicator into maintenance mode. Any errors that occur during the process can prevent the replication from being reconstructed correctly on the new replicator, as in the following example:

2025-08-20 03:49:04.366  WARN - [UI-########-####-####-####-############-####-##] [task-poller-1] c.v.h.m.r.RebalanceReplicationsJob       : Destination move failure for replication H4-########-####-####-####-############ to replicator ########-####-####-####-############
com.vmware.h4.manager.api.exceptions.FailedToSwitchDestinationReplicatorException: Failed to to switch the destination replicator of replication 'H4-########-####-####-####-############' from '########-####-####-####-############' to '########-####-####-####-############' because of 'Operation aborted due to an unexpected error.'.

Resolution

VMware Cloud Director Availability no longer has adequate information to manage the replication in the underlying infrastructure and this information cannot be reconstructed. In order to remediate this issue, the replication will need to be removed and recreated.

Additional Information

Depending on whether the issue occurs at the source or the destination, VMware Cloud Director Availability may be unable to remove the replication files at the destination, which would require manual removal. Otherwise, the replication configuration on the source virtual machine may not be deleted, which would prevent the creation of the new replication and require manual correction, as in the following articles:

Configuring a replication for a VM fails stating an active replication is already enabled in Cloud Director Availability

Disabling VMware vSphere Replication on a virtual machine