This page provides an exhaustive list of the steps and substeps for replication cycles, test-clone and cut-over, as well as the reference information for adaptation reports generated during your migrations.
Replication cycle details
During the replication cycle, one of the following substeps is displayed along with the replication status:
| Replication status sub-step | Actions performed |
|---|---|
| Initializing replication | Initiating migration cycle, snapshotting source VM, and scanning for changes in source VM disk data. |
| Replicating | Live progress of the source VM data upload. |
| Post processing | Writing and snapshotting target disks, running OS adaptations, and deleting the source VM snapshot. |
| Idle | There is no active cycle. |
Test-clone details
While creating a test-clone of a migrated VM, you'll see one of the following substeps displayed:
| Test-clone status substeps | Actions performed | Comments |
|---|---|---|
| OS Adaptation | Running OS Adaptation | (Optional) Visible if the target license has changed since the last successful adaptation run. |
| Preparing VM Disks | Preparing VM disks for migration, making an image of the source VM. | |
| Instantiating Migrated VM | Creating the target VM with migrated workload. |
Cut-over details
When cutting your workload over, one of the following substeps will be displayed:
| Cut-over status sub-step | Actions performed | Comments |
|---|---|---|
| Previous Replication Cycle | Identical to any replication cycle (including the same substeps). | (Optional) Visible if a prior replication cycle was active when the cutover job was created. |
| Shutting down VM | Shut down the source VM. | Initiates source VM down-time. |
| Final sync | Final replication cycle, including the same substeps. | |
| Preparing VM disks | Preparing VM disks for migration, making an image of the source VM. | An identical action is performed during the test-clone phase. |
| Instantiating Migrated VM | Creating the target VM with migrated workload. | An identical action is performed during the test-clone phase. |
Adaptation report
Migrate to Virtual Machines generates adaptation reports during your replication cycle, clones, and cut-over cycle for you to use for troubleshooting, problem solving, and deeper insight into your migration process.
Here is an example of an adaptation report:
"Adaptation report: root:{type:{value:\"linux\"} osinfo:{value:\"ubuntu14.04\"} distro:{value:\"ubuntu\"} product_name:{value:\"Ubuntu 14.04.5 LTS\"} major_version:{value:14} minor_version:{value:4}} boot_type:BIOS guest_os_features:\"VIRTIO_SCSI_MULTIQUEUE\" applied_license:{type:NONE default:true}"
The fields for the Migrate to Virtual Machines adaptation report:
| Field | Description | |
|---|---|---|
| status | The status of this adaptation report. Possible values:
| |
| errors | List of errors in this adaptation report. | |
| warnings | List of warnings in this adaptation report. | |
| root | The root filesystem of the OS. | |
| boot_type | The boot type of the VM. Possible values:
|
|
| guest_os_features | Guest OS Features to attach on the boot disk. | |
| licenses | Licenses to attach on the boot disk. | |
| applied_license | License information to support user license type setting. applied_license.default
indicates whether Migrate to Virtual Machines should apply the
default license for
your migration. applied.license.type specifies the applied
license for your migration if applied_license.default is set
to FALSE.Possible values applied_license.type:
Possible values
|