The path-optimized copy mechanism, which was introduced in vCloud Connector 2.5, is compatible with earlier versions of vCloud Connector.

The following table lists which copy mechanism is used when the vCloud Connector nodes in the source and destination clouds are of different versions.

Compatibility with Earlier Versions

Node A Version

Node B Version

Copy Mechanism Used

2.5 or later

2.5 or later

Path-optimized copy

2.5 or later

2.0

Old, 2.0 copy mechanism

2.0

2.5 or later

Old, 2.0 copy mechanism

2.0

2.0

Old, 2.0 copy mechanism

In new installation or upgrade scenarios, your vCloud Connector nodes in the source and destination clouds will be of the same version.

In scenarios where a vCloud Connector node is deployed as a multitenant node, you might have different versions of the node on the source and destination clouds. For example, if you are using a service provider node on a public vCloud, the service provider node might be of a different version than the node in your private cloud.

Note

As the UDT copy protocol is only available in vCloud Connector version 2.5 and later, it can be used only if both the source and destination nodes are version 2.5 or later. If one of the nodes is an older version, the default HTTP(s) copy protocol is used regardless of whether UDT is selected.