1.0
Table Of Contents
- About this Guide
- Introducing Hybrid Cloud Manager™
- Understanding the Hybrid Cloud Manager Installation Process
- Choosing a Deployment Architecture
- Preparing Your Installation Environment
- Installing and Configuring Hybrid Cloud Manager
- Install the Hybrid Cloud Manager Appliance
- Register the Hybrid Cloud Manager with the vCenter
- Configuring the Hybrid Cloud Manager for vCenters with an External Lookup Service
- Register the Hybrid Cloud Manager with a vCloud Air Endpoint
- Installing and Configuring Hybrid Services
- Configuration Overview
- Start Appliance Installation and Configuration
- Configure the Hybrid Cloud Gateway
- Configure the Network Extension Service
- Stretching an L2 Network to vCloud Air
- Migrating a Virtual Machine to vCloud Air
- Administration
- Troubleshooting
vCloud Air® Hybrid Cloud Manager™ Installation and Administration Guide
Page 31
5. Following the switchover, the source virtual is powered-off, and the migrated replica is powered on.
6. Hybrid Cloud Manager renames the powered-off replica to avoid a naming conflict with the live VM. A binary
timestamp is appended to the replica name.
The migration is complete, and conceptually, this is where replication stops.
• Powered off replicas are stored in your on-premises vCenter in folders named “VMs migrated from the cloud,”
and “VMs migrated to the cloud.”
• In this release, you must manually delete any unwanted replicas.
Checking Your VM before Migration
Before you migrate a VM, be sure that it meets these conditions.
• VM size must not exceed 62 TB.
• vSphere Replication can replicate virtual machines greater than 2TB with the following limitations:
• vSphere Replication tracks changed blocks, so the amount of data written to disk determines how much
memory is consumed.
• vSphere Replication tracks larger blocks on disks over 2TB. Replication performance on a disk over 2TB might be
different than replication performance on a disk under 2TB for the same workload depending on how much of
the disk goes over the network for a particular set of changed blocks.
• Replication bandwidth consumption varies depending on the workload and how it changes blocks on the disk
during the RPO interval.
• Hybrid Cloud Manager cannot migrate virtual machines that share VMDK files in this release.
• The VM must be powered on.
Migrating a Sample VM from an On-premises vCenter to the Cloud
The following procedure demonstrates how to migrate a workload VM from an on-premises datacenter to the vCloud
Air endpoint associated with the VM’s network. This sample migration uses two virtual machines in the vCenter where
Hybrid Cloud Manager resides. The sample VMs are:
• WordPress_App (192.168.200.200): Virtual Machine to be migrated to vCloud Air.
• eCommerce_App (192.168.200.201): Start a ping from this VM to the VM to be migrated.
If you want to follow along in your own environment, choose two VMs in the vCenter where the Hybrid Cloud Manager
resides. Migrate one VM, and use the other to track connectivity to the VM, as well as the overall progress of the
migration.