This section lists some of the issues and their causes that may occur in Dedicated Disaster Recovery.

Second vCloud Director endpoint on the on-premises HCM cloud collection table causes virtual machine replications to go in to the ‘Not Active’ state

Initially you register HCM and vSphere Replication Management Server (VRMS) to one cloud endpoint and then you register both HCM and VRMS to another cloud endpoint and later remove the second registration. However, the second cloud registration still exists in the database and the Dedicated Disaster Recovery transport service receives two cloud registrations from HMS, which causes messages or events to be sent to the second (stale) cloud registration. This is not visible from the UI.

To resolve this issue, contact vCloud Air support and they will delete the second cloud registration from the database.

Cannot configure replication on virtual machines that you created in an ESXi host

If you have created a virtual machine in ESXi and not in vCenter, when you configure it for replication, that virtual machine does not Power ON after recovery, because the replicated virtual machine has a MAC address that is not recognized by vCenter.

After test recovery is complete, you can resolve this issue by resetting the MAC address and powering on the virtual machine manually.

User authentication failure

User authentication failure should not occur as OrgAdmin is directly authenticated against vCloud Director. However, if it does occur, it may be due to the role associated with the user account. Verify that the user role has the required privileges.

Cloud registration fails

It may be due to any of the following reasons:

The role associated with the user account may not have the correct privileges.

vCloud Director is not reachable from on-premises datacenter.

HCM does not retry if login credentials are incorrect. The credentials must be authenticated before HCM attempts to log in and start the cloud registration.

Virtual machine replication errors or virtual machine in ‘Not Active’ state

A replication error is displayed when the tunnel does not get created due to the HCM transport service breakdown. Review the on-premises HCM log files.

A virtual machine may be shown as 'Not Active' state due to the CGW. Ensure that the CGW status is active in the on-premises HCM UI.

Virtual machine not displayed in the Dedicated Disaster Recovery UI

Some virtual machines may not be displayed in the UI due to a lag in vCloud Director inventory updates. Also, the virtual machines created in vCloud Director or the ones that are not associated with replication groups will not be displayed in the Dedicated Disaster Recovery UI. You can view these virtual machines in the vCloud Director UI.

Cannot ping after test/recovery

If you cannot ping a virtual machine after test and recovery, verify if the pings are coming from the same subnet. In the case of recovery over a stretched network, the IP address should be preserved on the cloud side after successful recovery. You can test if the ping works in the same L2 segment before proceeding to a different segment.

For Technical Support, file a request through standard VMware process available at My VMware.