running-migration-plan.adoc

Running a migration plan

You can run a migration plan and view its progress in the {ocp} web console.

Prerequisites

• Valid migration plan.

Procedure

1. In the {ocp} web console, click Migration → Plans for virtualization.

   The Plans list displays the source and target providers, the number of virtual machines (VMs) being migrated, the status, the date that the migration started, and the description of each plan.

2. Click Start beside a migration plan to start the migration.

3. Click Start in the confirmation window that opens.

   The plan’s Status changes to Running, and the migration’s progress is displayed.

   Warm migration only:

   • The precopy stage starts.

   • Click Cutover to complete the migration.

4. Optional: Click the links in the migration’s Status to see its overall status and the status of each VM:

   • The link on the left indicates whether the migration failed, succeeded, or is ongoing. It also reports the number of VMs whose migration succeeded, failed, or was canceled.

   • The link on the right opens the Virtual Machines tab of the Plan Details page. For each VM, the tab displays the following data:

     • The name of the VM

     • The start and end times of the migration

     • The amount of data copied

     • A progress pipeline for the VM’s migration

       Warning

       vMotion, including svMotion, and relocation must be disabled for VMs that are being imported to avoid data corruption.

5. Optional: To view your migration’s logs, either as it is running or after it is completed, perform the following actions:

   1. Click the Virtual Machines tab.

   2. Click the arrow (>) to the left of the virtual machine whose migration progress you want to check.

      The VM’s details are displayed.

   3. In the Pods section, in the Pod links column, click the Logs link.

      The Logs tab opens.

      Note	Logs are not always available. The following are common reasons for logs not being available: The migration is from {virt} to {virt}. In this case, virt-v2v is not involved, so no pod is required. No pod was created. The pod was deleted. The migration failed before running the pod.

   4. To see the raw logs, click the Raw link.

   5. To download the logs, click the Download link.