VMware vCloud Director Availability & VM Discovery

[FrankW86]

Hi folks,

Currently we are testing the product VMware vCloud Director Availability.

It's looking very promising and will allow us and our customers to replicate or migrate VMs pretty simple to our platform(s).

But at the moment I'm playing around with the Failover Test option and the documentation on this option clearly says it necessary or important that the Vm Discovery on the vCloud Director environment is turned off. I noticed this is the same for the Failover option in general. But I'm missing the reason as to why? Why does it needs to be turned off?

We've got the VM Discovery turned on at the moment and when I've got a replication task running for several VMs. These VMs called C4-xxx are visible in vCenter, but not in vCloud Director, which is a good thing. And when I start a Failover Test, the vApp is created and the VMs are visible in vCloud Director which, I presume, is correct as well. 

What am I missing? Hope somebody can clarify this for me.

Cheers!

[FrankW86]

Nobody?

[Sree]

The prime reason is during the failover we can end up in duplicate VM in VCD, we need  VCDA to do this job as machines are getting imported and powered on after going through the required changes. That being said in the recent release of VCD you have the option to enable/disable at three levels and you can select the best option based on the failover scenarios. 

1. Global

2. Organization

3. VDC 

https://docs.vmware.com/en/VMware-Cloud-Director/10.3/VMware-Cloud-Director-Service-Provider-Admin-Portal-Guide/GUID-068B8D3E-11B4-4B67-A653-B374AFD98303.htmlhttps://docs.vmware.com/en/VMware-Cloud-Director/10.3/VMware-Cloud-Director-Service-Provider-Admin-Portal-Guide/GUID-068B8D3E-11B4-4B67-A653-B374AFD98303.html