Failover stuck at 49% in VMware Cloud Director Availability

Products

• VMware Live Recovery
• VMware Cloud Director

Issue/Introduction

When performing a test failover or migration in VMware Cloud Director Availability (VCDA), the task progress appears to stall (typically at 48% or 49%).

• The VCDA UI shows the task as "Running" but with no progress for an extended period.
• In the destination site Cloud Service cloud.log, entries similar to the following are observed:

  DEBUG - [job-67] com.vmware.h4.cloud.job.C4BaseJob : Suspending execution for task cc32ec94-####-####-####-de009baa6cfd, waiting for remote task 56cbb1a1-####-####-####-de117554c9ab to completeDEBUG - [job-67] com.vmware.h4.jobengine.JobEngine : Suspending execution for task cc32ec94-####-####-####-de009baa6cfd

• Background placement synchronization tasks may fail with IllegalStateException: Illegal state of property 'recoveryState': IN_PROGRESS because the recovery is already active.

Environment

VMware Cloud Director Availability 4.x

Cause

VCDA suspend execution while waiting for downstream operations in VMware Cloud Director or vCenter to complete. These operations can include:

• VM registration and vApp reconfiguration.
• Storage/disk operations (e.g., consolidation or placement).
• Networking updates or power-on sequencing.

Resolution

Monitor the downstream tasks to identify the source of the delay:

1. Log in to the destination VMware Cloud Director and vCenter instances.
2. Check the Tasks console for operations initiated by the VCDA service account during the failover window.
3. Correlate the Remote Task ID found in the VCDA cloud.log with the task IDs in the VMware Cloud Director activityevent.log.
4. If tasks are taking longer than expected (e.g., 30+ minutes), investigate storage latency or host performance on the destination site ESXi hosts.
5. Wait for the downstream tasks to complete; VCDA will automatically resume once it receives the completion signal from VMware Cloud Director.

If the tasks fail or remain stuck indefinitely, contact Contact Broadcom support for a deep log correlation analysis across all components.