Create a migration
Configure a new migration to replicate the workload from one site to another. After a successful replication, you can migrate the workload to a remote site for running it in the destination site.
- Verify thatVMware Cloud Director Availability4.7 or later is deployed in both the source and in the destination sites.
- Verify that you can accessVMware Cloud Director Availabilityas atenantor as aprovider. For more information, see VMware Cloud Director Availability へのアクセス.
With
VMware Cloud Director Availability
4.7.2 and later, you can create a replication for
a virtual machine (VM) with enabled virtual Trusted Platform Module (vTPM), and
with full, partial, or no encryption of the attached storage disks. You can also
create a replication for a non-encrypted VM and encypt the VM as a part of the
replication process. For more information, see Create a replication for encrypted virtual machines.The target recovery point objective (RPO) for a migration always is 24 hours. For information about the RPO, see Replicating workloads.
- In the left pane, choose a replication direction by clickingIncoming ReplicationsorOutgoing Replications.
- Alternatively, from the on-premisesvSphere Clienteither under theHosts and Clustersor under theVMs and Templatesinventories, right-click the virtual machine or from theActionsmenu select:
- Configure Protection
- Configure Migration
- Fast Migration
- After selecting the replication direction, initiate creating a new migration.
- To configure the migration with all migration settings, click.
- Alternatively, for one-click migration while skipping the settings, click.vSphereDR and migration betweenvCenter Serversites do not allow one-click migration.
One-click migration requires only selecting the source workloads for migration, skipping the migration settings configuration and allowing finishing the replication wizard or navigating back for configuring the settings. - To create the migration, depending on the source and destination sites complete theNew Migrationwizard.
- For an on-premises site as a source and a Cloud Director site as a destination:
- On theSource VMspage, select the source virtual machines, then clickNext.To unite the selected virtual machines in one vApp, activate theGroup VMs to a single vApptoggle.
- On thevApp Settingspage, that shows after activatingGroup VMs to a single vApp, you must enter a vApp name for the group. By entering the vApp name of an already existing vApp replication the selected virtual machines become part of that replication. Optionally, when protecting multiple virtual machines change their order of boot by dragging each row and set optional boot delay between each replicated virtual machine in the resulting vApp. Then, clickNext.
- On theDestination VDC and Storage policypage, select the destination virtual data center. Then, either select the storage policy for placing the recovered workloads and clickNext, or to configure seed and flexible storage profile assignment, activate theAdvanced Datastore Settingstoggle.
- For a Cloud Director site as a source:
- On theSource VMs and vAppspage, select the source workloads, then clickNext.
- For an on-premises site as a destination:to configure seed and flexible storage profile assignment on the next page, activate theAdvanced Datastore Settingstoggle. Then, clickNext.
- For a Cloud Director site as a destination:on theDestination VDC and Storage policypage, select the destination virtual data center. Then, either select the storage policy for placing the recovered workloads, or to configure seed and flexible storage profile assignment, activate theAdvanced Datastore Settingstoggle.
- ForvSphereDR and migration to avCenter Serversite as a destination:
- On theSource VMspage, select the source virtual machines, then clickNext.
- On theDatastorepage, either select the VM storage policy and destination datastore for placing the recovered workloads, or to configure seed and flexible storage profile assignment, activate theAdvanced Datastore Settingstoggle.
- UnderAdvanced Datastore Settings, when activated, configure the following settings for the destination datastore of each virtual machine in the replication:
- In the left pane underVM name, click on a virtual machine to configure its advanced datastore settings.
- In the right pane underUse a seed VM, to lower the network data traffic and the required time for the initial synchronization by copying only the different data blocks from the source workload and reuse the seed data as a basis for replicating, activate theConfigure with seed VMtoggle.
- UnderUse flexible storage profile assignment, you can replicate one virtual machine to multiple datastores. For example, place one of its disks on a separate datastore, or split some disks from the .vmx file.
- Configuration files
- This section does not show for replications from a Cloud Director site as a source to an on-premises site as a destination as it already uses the on-premises placement.
- From theVM Storage Policydrop-down menu, select the storage policy for the replicated workload configuration files in the destination site.
- For vSphere DR and migration, from theVM Placement Datastoredrop-down menu, select the destination datastore for the replicated workload configuration files.
- To apply the same to all disks, clickApply,
From theDisk inclusiondrop-down menu, optionally select either toInclude Allor toExclude Alldisks from the VM in the destination. Without any disks selected for replication, you cannot continue.- DiskX
- For each disk in the selected VM, underDisk, to include this disk in the replicated virtual machine, activate theXReplicatetoggle.
- From theStorage policydrop-down menu, select a storage policy for this disk. For a Cloud Director site as a destination, this option requires RTVM placement. For more information, see Replication tracking placement solution. This menu does not show for replications from a Cloud Director site as a source to an on-premises site as a destination as it already uses the on-premises placement.
- For vSphere DR and migration, from thePlacement Datastoredrop-down menu select a placement datastore for this disk.
- After configuring the advanced datastore settings for all needed virtual machines in the replication, clickNext.
- On theSettingspage, configure the following migration settings depending on the source and destination sites, then clickNext.One-clickFast migrationskips theSettingspage directly to theReady to completepage. To configure the migration settings, click theSettingspage, or alternatively, clickBack.
Compress replication trafficTo apply compression on the replication data traffic and reduce the network data traffic at the expense of CPU, activate this toggle.Disk ProvisioningForvSphereDR and migration betweenvCenter Serversites, select one of the following provisioning formats for the destination disk:- Thin Provision
- Thick Provision Lazy Zeroed
- Thick Provision Eager Zeroed
Delay start synchronization- To start the initial synchronization when the wizard finishes, leave this toggle deactivated.
- Alternatively, to schedule the start of the first synchronization, activate this toggle, then enter the local date and time.
VDC policy settingsFor a Cloud Director site as a destination:When a VDC policy with the same name already applies on the source workload, it is pre-selected for you. You can choose to either keep it and continue, or select another VDC policy.- Select the organization placement policy to apply on the recovered workloads from theVM placement policydrop-down menu.
- Select the organization sizing policy from theVM sizing policydrop-down menu. With no sizing policy selected for the replication,VMware Cloud Directorautomatically applies the system default sizing policy on the destination virtual machine.
- On theReady to completepage, verify the selected settings, then clickFinish.One-click migration, once used, skips the migration settings configuration. You can still configure the migration settings, by clicking theSettingspage, or alternatively, by clickingBack.
After completing the wizard, in the Replication type column for this replication, you see a
Migration
state. You can migrate, or test, or fail over the workload to the destination site. For more information, see Migrate a replication or レプリケーションのフェイルオーバーのテスト or Failover of a replication.