Migrating Using Lift & Shift

You can use the Lift & Shift tab on the Migrations page to complete a migration automatically. When you run an automatic migration, you cannot modify any of the elements of the system.

Note

Refer to Migrating Using Re-platform if you want to modify the machine before migration.

The automatic migration process includes the following steps:

1. Scan the source machine.
2. Generate a machine image from the scan result.
3. Publish the generated machine image to the selected target environment.

Launching an Automatic Migration

All pre-requisites listed in the section Migration Pre-requisites are also applicable to Lift & Shift migration.

In order to run a migration:

1. Go to the Lift & Shift tab on the Migrations page.
2. Click on the migrate button on the top right.

3. Enter the name of your migration.

4. From the drop-down menu select the target platform and type. Enter all other required fields, based on the target you have selected.
5. Click next.
6. Follow the instructions on the UForge AppCenter pop-up window.

7. Download binary locally by clicking Download.

   Note

   Older versions of curl command may not support a secure connection with UForge server. If you encounter a SSL connect error, you can use a web browser to download the binary or download the binary on another machine and copy it to the scanned machine.

8. Copy the binary on the source environment you want to migrate.

9. Open a terminal window and login to the source environment.

10. Launch the migrate command on the running source environment to start the migration.

    Note

    For Linux migration, you can exclude non-native files and directories using -e parameter. The -o parameter will include the overlay (this option is used by default). The overlay is all the things that are missing compared to a known state (a previous scan of a machine or the operating system native packages). This overlay is a standard tar archive.

    Note

    The uforge migrate tool self extracts in /tmp directory before execution. If the machine is configured with noexec option on /tmp partition a Permission denied error will occur. In that case, you can specify the environment variable TMPDIR to use a different directory. For example:

    TMPDIR=/root/ ./uforge-migrate.bin -U https://<uforge-ip>/api -u <username> \
            -n "Test_migration" -o
    

11. Click next to view the migration status.

12. You can return to the Lift & Shift page to view the status of your migrations.

Note

You should note that if you cancel a migration, this will stop the process of migration at the step currently being done. Therefore, for example, if the image generation is complete, it will be visible on your platform. Also, if publication has started, this may incur costs. You should check your cloud account. For more details on the constraints of publishing an image, refer to Publishing a Machine Image.

From the status page you can view more detailed information about the scanned instance. Refer to Viewing Details of an Automatic Migration.

Viewing Details of an Automatic Migration

Once your automatic migration has completed, you can view the details of the status and details of the machine migrated from the Lift & Shift tab on the Migrations page.

From the status page you can view more detailed information about the appliance scanned by clicking:

• Details for more information about the published appliance. This will include the cloud ID, cloud account used for publication, if the publication succeeded.
• View Scan Details which will bring you to the details of the scan appliance on the Re-platform page. From here you can see all the packages and files that are part of the appliance.
• View Generations Details which will bring you to the Generations page. This page lists ALL generations (not just from this migration). From here you can launch a publish.
• View Publication Details which will bring you to the Generations page.