Failed to enable cold migration featureERROR - [UI-########-####-####-####-############-####-##-##-##] [job-99] com.vmware.h4.jobengine.JobExecution : Task ########-####-####-####-############ (WorkflowInfo{type='configure', resourceType='h4dm', resourceId='null', isPrivate=false, resourceName='null'}) has failedcom.vmware.h4.replicator.api.exceptions.FailedToAcquireVcConnection: Unable to connect to vCenter '########-####-####-####-############'. at com.vmware.h4.replicator.vc.VcConnector.acquire(VcConnector.java:355) at com.vmware.h4.replicator.vc.VcConnector.acquireLatest(VcConnector.java:329) at com.vmware.h4.replicator.h4dm.DataMoverService.addVim(DataMoverService.java:91) at com.vmware.h4.replicator.h4dm.job.ConfigureH4dmJob.lambda$enableVcentersImpl$5VMware Cloud Director Availability 4.7
This issue occurs when the VCDA Manager does not have access to all the vCenters that back the accessible PVDCs.
To fix this issue you need to make sure that the vCenters that back the PVDCs accessible to VCDA can connect with the VCDA Manager. For this you can either ensure connectivity between all the vCenters that back the accessible PVDCs and the VCDA manager appliance or limit the accessible PVDCs in the VCDA settings.
Note: After disabling the accessible PVDCs the change can take up to 30 minutes to synchronize the accessible vCenters.
For more information on enabling Cold Migrations in VCDA, see Activate the cold Migrations