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.

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

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

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

Note

When you copy a vApp or vApp template from a vCloud Director cloud, the vApp's internal network configuration is not retained in the destination cloud. The vApp is always deployed in the destination cloud in fenced mode with a direct connection to the organization network.

You can start multiple copy tasks at the same time. The copy tasks are executed in parallel. By default, vCloud Connector executes a maximum of 10 concurrent tasks per cloud, that is, per vCloud Connector node. If you specify more than 10 tasks, the first 10 tasks are executed concurrently. When a task finishes, the next one in the queue is executed.

As copy tasks involve both a source cloud and a destination cloud, the concurrent tasks limit applies to both the source and destination clouds for copy tasks.

You can choose to increase the maximum number of concurrent tasks for a vCloud Connector node. If you increase the limit, you must increase the node storage as well. The amount of extra storage you need depends upon the size of your copy tasks. Though the objects being copied are not written to the source or destination node staging area during copy, in certain cases (for example, when the transfer or import part of the copy process is slower than the export), vCloud Connector uses the staging area and might require storage equivalent to the size of the object being copied.

Note that you should add storage on both the source and destination clouds.

See Increase Maximum Concurrent Tasks 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.