6.4.3 Cloning and Copy Operations
When designing a datastore (LUN, NFS export, vSAN), take into account layout and storage network considerations (especially bandwidth) with regard to expected cloning and copy operations:
• Importing or exporting templates to and from vCloud Director, or movement of VMs or ISO images between vCenter Server instances, always goes through vCloud Director. Cells transfer shared volume over the management network to the ESXi host’s management vmknic.
• Clone and copy operations between vSphere clusters that do not have common shared storage use the ESXi host management vmknic, or in the case of vSphere 6.x, vmknic with provisioning service enabled.
• ISO media is stored as a file on the catalog datastore. The media cannot be mounted to a VM that is running on a host that does not have access to the datastore.
• vSAN datastore is accessible only by the vSphere cluster it belongs to.
• When using port binding, iSCSI traffic cannot be routed.
• vSphere 5.5 does not support IP storage over IPv6 networks
• When an elastic Org VDC is used, the provider can migrate running VMs from one cluster / resource pool to another. This operation, however, does not support enhanced vMotion compatibility and shared storage is required between clusters.