Error "Failed to rename replication tracking VM 'XXXX'. Unexpected VMware Cloud Director error" while trying to protect the VM in VCDA

Products

• VMware Cloud Director

Issue/Introduction

• While trying to protect a VM in VCDA, the named disk fails to be created in VMware Cloud Director with an error: Failed to rename replication tracking VM 'XXXX'. Unexpected VMware Cloud Director error
• In the /opt/vmware/h4/replicator/log/replicator.log  file on the Cloud Replication Management Appliance, you see similar entry:

Failed to rename replication tracking VM 'XXXX'.
Unexpected VMware Cloud Director error. [ UI-XXXX ] java.util.concurrent.ExecutionException: (vim.fault.MethodDisabled) { faultCause = null, faultMessage = null, source = vcd1 } - (vim.fault.MethodDisabled) { faultCause = null, faultMessage = null, source = vcd1 } - The method is disabled by 'vcd1'

Environment

• VMware Cloud Director Availability 4.x
• VMware Cloud Director 10.5.x

Cause

This issue occurs when the on-premises VCDA appliance is not properly configured within the same subnet as the replication VMkernel.

Resolution

To resolve the issue, ensure that the on-premises VCDA appliance is placed in the same subnet as the replication VMkernel.

This configuration change resolves the issue and allows new protection setups to be completed successfully.

Additional Information

 For more details, refer to the VMware Cloud Director Availability documentation.