Hybrid Cloud Manager enables bidirectional migration: from on-premises to the cloud, or from the cloud to the on-premises data center. Hybrid Cloud Manager uses replication technology during the migration process.

Replication technology is integrated in the Hybrid Cloud Gateway virtual appliance. You do not need to install any additional replication software.

Low-downtime migration uses host-based replication to move a live virtual machine from a vCenter to a virtual data center (or the opposite direction). To reduce downtime, the source VM remains online during the replication and is bootstrapped on the destination ESX host after replication completes.

1

A Hybrid Cloud Manager migration request triggers the following actions:

Replication begins a full synchronization transfer into a vCloud® Air™ virtual data center. The time it takes to replicate is a function of the size of the VM and available bandwidth.

Replication bandwidth consumption varies depending on how the workload changes blocks on the disk.

2

When full synchronization finishes, a delta synchronization occurs.

3

When the delta synchronization finishes, Hybrid Cloud Manager triggers a switchover. You can start immediately or delay the switchover until a specific time.

4

Following the switchover, the source VM is powered-off, and the migrated replica is powered-on. If for some reason the VM cannot power on, the new VM is powered off (or remains powered off) and the original is powered on. You must have sufficient resources to power on the VM.

5

Hybrid Cloud Manager renames the powered off original VM to avoid a naming conflict with the migrated VM. Hybrid Cloud Manager appends a binary timestamp to the original VM name.

If you have not enabled “Retain MAC,” the migrated VM obtains a new MAC address. See MAC Address Retention.

The migration is done. Hybrid Cloud Manager copies the original VM to the “Migrated VMs” folder in the vSphere Templates view. You can recover a saved VM.

Cross-cloud vMotion transfers a live virtual machine from a vSphere vCenter to a vCloud Air virtual data center. Cross-cloud vMotion requires a stretched network, formed with a High Throughput Layer 2 Concentrator and 250 Mbps or above throughput capability. The vMotion transfer captures the virtual machine's active memory, its execution state, its IP address, and its MAC address.

Note

The virtual machine hardware version must be at least version 9, or cross-cloud vMotion might fail.

You can speed up the migration if you use a direct connection. You can also use a combination of Hybrid Networking Premium (which supplies up to 1 Gbps), and WAN Optimization (which provides data deduplication and compression).

Cold migration uses the same data plane as cross-cloud vMotion to transfer a powered-off virtual machine over an extended network. Its IP address and MAC address are preserved. The virtual machine requirements and restrictions are the same as for vMotion.

Using the vSphere Web Client, you can access the bidirectional migration wizard from the Hybrid Cloud Manager Getting Started tab. This wizard handles all migration details, including multiple virtual machines.

To migrate a virtual machine, you must have a secure connection maintained by the Hybrid Cloud Gateway, and the VM must meet the requirements in this topic.

You can monitor the progress of a replication-based migration from the user interface, or from the command line.

When Hybrid Cloud Manager powers on a successfully migrated virtual machine, it powers off the original virtual machine and stores it in a folder in the vCenter. The stored virtual machines remain until you manually delete them.