Architecting a vCloud Availability for vCloud Director Solution : Use Cases : 2.2 Migration
   
2.2 Migration
Description:
Customer wants to migrate a large number of workloads to the public cloud with minimum downtime.
Typical Use Case:
1. Customer requests DR option for existing or new Organization Virtual Data.
2. Customer sets up cloud networking infrastructure with Organization VDC networks that use the same subnets as the on-premises or co-located environment.
3. Customer configures the new vCloud replication endpoint in vSphere Web Client with its vCloud Director credentials.
4. Customer configures the vSphere networks in vSphere Web Client to map to the vCloud Org VDC networks for failover purposes.
5. Customer enables replication for each workload that will be migrated in the vSphere Web Client. RPO, point-in-time snapshots, and guest quiescing are not critical for the migration use case. Data compression can be optionally enabled.
6. After the initial synchronization of each protected workload has completed, the migration can be performed on each virtual machine. To secure minimal workload downtime, migration is performed in following way:
New delta sync is performed
vSphere workload is gracefully shut down.
Last data sync is performed
Workload is powered on in the cloud
 
Expected Result:
Workload is migrated to the public cloud with no data loss and with minimal downtime (minutes)
Other comments:
Metering for VMware licensing is based on number of protected virtual machines
Customer billing is based on resource usage (CPU, memory, disk space)
The service provider can optionally offer migration as a managed service