You can use vCloud Connector to copy virtual machines, vApps, and templates between clouds that have been added to your vCloud Connector instance.

You can copy objects between two vSphere clouds, between two vCloud Director-based clouds, and between vSphere and vCloud Director-based clouds. These can also include public clouds such as service provider vClouds or vCloud Air cloud instances.

The following table shows how virtual machines, vApps, and templates are copied from a vSphere cloud to different destinations.

Copying From vSphere

Type of Object

Destination: vSphere

Destination: vCloud Director-based Clouds

Virtual machine

Virtual machine

vApp template

vApp

vApp

vApp template

VM template

VM template

vApp template

The following table shows how objects are copied from a vCloud Director-based cloud to different destinations.

Copying From vCloud Director-based Clouds

Type of Object

Destination: vSphere

Destination: vCloud Director-based Clouds

vApp containing one VM

VM

vApp template

vApp containing multiple VMs

vApp

vApp template

vApp template containing one VM

VM

vApp template

vApp template containing multiple VMs

vApp

vApp template

You can start multiple copy tasks at the same time. The copy tasks are executed in parallel.

A maximum of 5 concurrent copy tasks are allowed for on-premise nodes. This means that you can copy from or to an on-premise cloud (private cloud) only if the node associated with the cloud has fewer than 5 copy tasks running. When you attempt to copy, vCloud Connector checks the number of copy tasks on the source and destination nodes. If either node is on-premise and has 5 copy tasks running, you cannot copy. The task is not queued.

This concurrent copy task limit applies to on-premise nodes only, it does not apply to public nodes.

For example, if you want to copy from an on-premise vSphere instance to vCloud Air, you can use the Copy command only if the on-premise node has fewer than 5 tasks running. If you want to copy from an on-premise vSphere instance to another on-premise vSphere instance, you can use the Copy command only if both the source and the destination nodes have fewer than 5 tasks running.

This concurrent copy task limit applies only to the Copy command. It does not apply to Content Sync copy tasks.

The default staging storage on vCloud Connector nodes is 40 GB. Increase the staging storage if you plan to copy large objects or copy multiple objects concurrently. See "Configure vCloud Connector Node Allocated Storage" in Installing and Configuring vCloud Connector for more information.

You can select the data transfer protocol used for copy. vCloud Connector provides two protocols: HTTP(S), which is the default, and UDT. You can also choose to encrypt data during copy.

You set these options in the vCloud Connector nodes associated with the source and destination clouds. Once the options are set, they apply to all subsequent copy commands.

See Selecting Copy Options in Installing and Configuring vCloud Connector for more information.

Copying large virtual machines or vApps can take several hours, depending on the size of the object you are copying and on network conditions.

To configure your environment for copying large workloads, see Copying Large Virtual Machines and vApps in Installing and Configuring vCloud Connector.

You cannot copy an object that has an ISO file attached.

When you copy to vSphere, the destination host must have a Standard Virtual Switch with a VM Network port group defined.