You can validate your copy selections and your configuration before you copy objects from one cloud to another. vCloud Connector runs checks for connectivity, storage, and latency, among others. This helps you avoid copy failures by checking for common errors before you start the copy.

Copy checks are run when you click the Validate button in the Copy wizard. Errors and warnings are displayed. Errors must be fixed before you can proceed with copy. Warnings are informational and do not prevent you from copying.

Note

Copy validation is only available if both the source and destination nodes are version 2.6 or later.

vCloud Connector checks the following.

Connectivity between the vCloud Connector server and the nodes associated with the source and destination clouds

Connectivity between the nodes associated with the source and destination clouds

Connectivity between the nodes and the clouds with which they are associated

Staging area storage in the nodes

Storage in the destination datastore or organization virtual data center

Permissions to write to catalog (for vCloud Director)

Latency between the nodes

OVF check (for vSphere)

Duplicate name in catalog

Duplicate name in virtual data center (if you are deploying the object)

Transfer mode (HTTPS or UDT) for copy

Version compatibility between source and destination clouds

VMware Tools version (if guest customization is enabled)

Warnings do not prevent you from copying. However, resolving the issues before proceeding can help you avoid copy failures.

The following are examples of warnings.

Warning

What You Should Do

Copy cannot be validated because the node associated with the cloud must have a minimum version of 2.6.

If you want to validate copy, ensure that the nodes associated with both the source and destination clouds are version 2.6 or later.

Guest customization requires a minimum VMware Tools version of 7299.

If guest customization is enabled on the object you are copying, ensure that both the object and the destination cloud have the latest version of VMware Tools installed. If you are deploying a Windows virtual machine, also ensure that the latest version of Sysprep is installed.

Destination datastore does not have enough space for the entity.

Select a different datastore or increase the capacity.

The template contains a VMDK with a .iso extension. Copy might fail.

If you are copying to vSphere, the .iso file is ignored when the object is imported. However, if you are copying to vCloud Director, vCloud Connector attempts to import the .iso file which might result in copy failing in some cases.

Unable to determine user permissions for the catalog.

Verify that you have write permissions for the catalog you select.

Note that the privileges or rights associated with the account you use to add a cloud to the vCloud Connector UI determine the actions you can perform.

Detected high latency between the nodes. If the connection has high bandwidth, UDT is recommended as the transfer protocol. Otherwise, use HTTPS.

Select the transfer mode that is appropriate for your environment. You set the transfer mode in the node Admin Web console. See Installing and Configuring vCloud Connector for information.

Staging area in node is less than the size of the template.

Increase the staging area storage to be equal to or more than the size of the object you are copying. While this storage may not be used under optimal conditions, in some cases it is required.

Unable to calculate the staging area in node.

Verify that the staging area storage is equal to or more than the size of the object you are copying. While this storage may not be used under optimal conditions, in some cases it is required.

The following issues are errors. You must fix them before you can proceed with copy.

The following are examples of errors.

Error

What You Should Do

Node associated with cloud: name is down.

Restart the node. You can check the status of all nodes in the server's Admin Web console.

An entity with the same name already exists in the target cloud.

Specify a different name for the object.

Destination Org VDC does not have enough space for the template.

Increase the storage in the destination virtual data center or select a different destination.

Destination datastore does not have enough space for the entity.

Select a different datastore or increase the storage.

Error while verifying datastore/VDC in destination cloud: name.

Check the connectivity to the destination cloud.

Unable to validate connectivity from node name associated with cloud name. Copy might fail. Check the status of the node.

Check the status of the node and verify that it is up. You can check the status of all nodes in the server's Admin Web console.

Error in validating the OVF descriptor. Could not obtain the lease.

Resolve the OVF issues.

Error while validating the OVF. There are no device files for this template. Copy cannot proceed.

Resolve the OVF issues.

Error in validating the OVF descriptor. One or more VMDK files specified in the OVF are missing.

Resolve the OVF issues.

Cannot access the entity. You do not have write permissions on the catalog.

Use a catalog for which you have write permissions.

Note that the privileges or rights associated with the account you use to add a cloud to the vCloud Connector UI determine the actions you can perform.

Cloud is not reachable from node.

Resolve connectivity issues between the node and the cloud with which it is associated.

Node name is not reachable from node name.

Resolve connectivity issues between the nodes.

This copy operation is not possible because of a virtual hardware version mismatch between the source and target.

You cannot copy objects between clouds whose virtual hardware versions are incompatible. For example, you cannot copy an object from vSphere 5.1 to vSphere 4.0.

Error while verifying entity from source cloud: name.

Check the object that you are copying and the connectivity to the source cloud.