9. Hybrid vCloud Considerations : 9.1 vCloud Connector : 9.1.4 vCloud Connector Limitations
9.1.4 vCloud Connector Limitations
vCloud Connector has the following restrictions:
*Currently, there is no way to have predefined vCloud instances display in vCloud Connector. Each user must manually add all vCloud instances that they intend to access to vCloud Connector. There are no vCloud instances defined by default.
*Traffic to and from the vCloud Connector appliance is not WAN-optimized, so migrating workloads over WAN links is not ideal even if sufficient bandwidth exists. Avoid traversing WAN links where possible by installing vCloud Connector appliances in optimal locations. Currently, there is no way to limit which vCloud instances can be added to a vCloud Connector instance, so instruct users to use only the proper vCloud Connector instance for their needs.
*The transfer process caches virtual machines in two different storage locations. To facilitate successful transfers, size the vCloud Connector staging storage and vCloud Director transfer storage appropriately. The staging storage is 40GB by default, so the largest virtual machine vCloud Connector can transfer is around 40GB.
*vCloud Connector is designed to give a consistent view of workloads across multiple vCloud instances and migrate those workloads. vCloud Connector cannot perform all of the operations vCloud Director can handle, so use the vCloud Director web console to manage workloads.
*All workload transfers are cold migrations. Power off vApps and virtual machines prior to migration. Hot migrations are currently not available. Also, vApp networking configuration must be modified before powering on the virtual machines.
*vCloud Connector can handle up to ten concurrent transfers. Subsequent requests are queued. The maximum number of vCloud connections for a single vCloud Connector is five (vCloud Director or vSphere).
NotevCloud Connector 1.5 does not support the vCloud 5.1 Suite. vCloud Director 5.1 requires vCloud Connector 2.0 or later.