CloudBase Coriolis Migration Guide

This guide describes how to migrate virtual machines from such cloud platforms as VMware and OpenStack to Virtuozzo Infrastructure using the CloudBase Coriolis migration solution.

coriolis diagram

Coriolis supports two types of migration:

  • Two-step migration: replication and deferred migration
  • One-step migration: replication and migration in a single session

Prerequisites

1. Deploy Cloudbase Coriolis.

2. Before migration, you need to prepare two images for the replication and OS morphing processes.

  • For Linux/Windows VM replication and Linux OS morphing, add a QCOW2 image with Ubuntu 22.04 and cloud-init installed as the Linux Temporary Migration Worker image.
  • For Windows OS morphing (VMware migration), prepare the Windows Temporary Migration Worker image (for example, Windows Server 2022) according to the Coriolis Temporary Migration Worker instructions.

Two-step migration

To perform two-step migration, you schedule the source VM replication to the destination, and then it starts the full disk replication. Optionally, you can also set up incremental replication once a day on a running VM. When you decide to perform migration, you stop the source VM, create a short incremental replica, and perform migration from this replica.

Replication

To start replication, you need to create a replica:

1. Click New > Replica:

coriolis replication1

2. Select the source cloud that was created previously:

coriolis replication2

3. In Source options, configure the following options:

  • For VMware, enable CBT:

coriolis replication3 1

  • For OpenStack, set Replica Export Mechanism to Coriolis Backups and configure Coriolis Backups Options:

coriolis replication3 2

4. Select VMs to migrate from the source cloud:

coriolis replication4

5. Select the Openstack Virtuozzo Infrastructure target endpoint:

coriolis replication5

6. Configure the target options:

coriolis replication6

Make sure that the following options are set:

  • Hypervisor type: qemu
  • Flavor Name
  • Port reuse policy
  • Volumes are zeroed: Yes

7. Configure the temporary migration worker options:

coriolis replication7

If you replicate a Linux VM, select only the Linux cloud image. For a windows VM, you need the both Windows and Linux cloud images.

8. Configure the network mapping:

coriolis replication8

9. Configure the storage mapping:

coriolis replication9

Click Next and set the replica schedule, if needed.

10. Review the summary, and then click Finish.

coriolis replication10

You should see that the replication process has started:

coriolis replication11

Once the VM replication is complete, you can proceed to the migration stage at any convenient time.

Migration

1. Go to the created replica, and then click Actions > Create Migration.

coriolis 2step migration1

2. Select the migration options:

coriolis 2step migration2

You can choose to either clone the disk or use the replica volume directly.

OS morphing is needed for migrating from different platforms, for example, from VMware to Virtuozzo Infrastructure.

3. Click Migrate to start the migration process.

coriolis 2step migration3

When all of the tasks are finished, the VM is successfully migrated.

Migration workflow for minimal downtime

1. Create a full replica of a running VM.

2. When the migration window starts, stop the VM and run incremental VM replication.

3. Create VM migration from the last replica.

One-step migration

With this type of migration, replication and migration are performed in one step, and this implies VM service downtime as you cannot plan the migration phase time.

1. Go to Migrations and click New.

2. Configure the settings. They are similar to those of a replica mentioned above, but there are some additional options, like Replication Count and Shutdown Instances on the final incremental replication.

coriolis 1step migration1

3. Review the summary and click Finish.

coriolis 1step migration2

Coriolis will perform full replication, then optionally stop the VM, perform incremental replication, and finally perform migration:

coriolis 1step migration3