Migrating to Nutanix via the Nutanix Move tool

Install, configure and use the Move migration tool

Last updated 5th April 2022

Objective

Nutanix provides a tool called Nutanix Move that allows migrations from other environments to AHV.

This guide explains how to perform a migration with the Move software.

OVHcloud provides services for which you are responsible, with regard to their configuration and management. It is therefore your responsibility to ensure that they work properly.

This guide is designed to assist you as much as possible with common tasks. Nevertheless, we recommend contacting a specialist provider if you experience any difficulties or doubts when it comes to managing, using or setting up a service on a server.

Some options, such as the use of compression or deduplication, require specific licences provided by Nutanix through OVHcloud. Please contact OVHcloud Sales for more information.

Requirements

  • A Nutanix cluster in your OVHcloud account
  • Access to the OVHcloud Control Panel
  • You must be connected to the cluster via Prism Central
  • A connection to an environment other than Nutanix

Nutanix Move Overview

Nutanix Move is a tool that allows virtual machine migrations from VMware ESXI, Hyper-V, Azure and AWS to AHV.

It can also be used to migrate from Nutanix AHV to AWS.

This software works on a virtual machine whose sources are available on the Nutanix website with a customer account.

For optimal use, we recommend installing Nutanix Move as close as possible to the destination.

The Nutanix Move software is the only software that communicates between the source and the destination.

It is strongly discouraged to use Nutanix Move with virtual machines on a Windows Server running Active Directory or Microsoft Exchange. It is best to migrate as recommended by Microsoft.

For VMs that use databases in Microsoft SQL, it is best to stop the database service when completing a migration.

Ensure that the original virtual machine is compatible with the destination Nutanix environment.

Instructions

We will look at how to migrate between a remote environment on Hyper-V to an OVHcloud Nutanix environment.

The source and the destination are on two interconnected private networks through an IPSEC VPN.

Preparing the original virtual machines before migration

The virtual machine must be in the list of supported virtual machines in the compatibility matrix for the migration to work.

Log in to the site below to verify the compatibility of the source machines with the destination environment on Nutanix:

Nutanix Accounting Matrix

Specificity of virtual machines on LINUX

Some virtual machines will not start correctly after migration via Nutanix Move.
Check the compatibility list as it is likely that the SCSI driver is not supported and needs to be changed with the PCI driver.
In this case, you will need to follow this procedure to change the disk controller of a Virtual Machine after the virtual machine is migrated.

Specificity of the Microsoft environment

Microsoft does not provide the SCSI adapter and network card Virtio drivers. These drivers must be installed prior to a migration. These drivers are available on the Nutanix website with a customer account.

Microsoft Windows 2008 is no longer supported by Microsoft or Nutanix. However, you can install older Virtio drivers and attempt a migration.

Login to the Nutanix website with a customer account to download the VIRTIO drivers.

VIRTIO driver download link.

Enter your user name in Emails, your password in Password and click Log In.

Download Virtio01

Click the Download link that suits you.

For our example, we will download the driver for amd64.

Download Virtio02

From a Windows virtual machine in the Hyper-V environment, double-click Nutanix-VirtIO-1.1.7-amd64.

Installing guest driver 01

Read the licence terms and conditions, accept them by ticking the box and then click Install.

Installing guest driver 02

Click Finish to complete the installation without having to restart the virtual machine.

Installing guest driver 03

Installing Move on the Nutanix Cluster.

Downloading and importing sources.

Retrieve the file in qcow2 format from this site: Download link for Nutanix Move.

Sign in with an account registered with Nutanix.

Portal login

Click Download to the right of Move QCOW2 file for AHV.

Download Move

Import the downloaded image from Nutanix Move into the cluster. For more information on importing images, see our guide on importing images.

Installing the Move virtual machine

Create a virtual machine from the Move image.

From Prism Central, open the main menu by clicking on the button in the top left-hand corner.

Move Install 01

Click VMs in the menu.

Move Install 02

Click Create VM.

Move Install 03

Type Nutanix Move in the Name field.

Choose the 2 vCPU, 2 Cores and 8 GB options in the VM Properties fields and click Next.

Move Install 04

Click Attach Disk.

Move Install 05

Choose the Disk, Clone from Image and move-4.3.0.qcow2 options and click Save.

Move Install 06

Click on Attach to Subnet.

Move Install 07

Choose the network in Subnet, make sure it is connected in Network Connection State, and click Save.

Move Install 08

Click Next.

Move Install 09

Leave the default time zone options and click Next.

Move Install 10

Click Create VM to complete the installation of the Nutanix Move virtual machine.

Move Install 11

Select the Nutanix Move virtual machine and click the Actions menu.

Move Install 12

Click Power On in the Actions menu to start the virtual machine.

Move Install 13

The virtual machine is started and an IP address is obtained if a DHCP server is operational on that network.

Move Install 14

This installation of Nutanix Move is done on a network that has a DHCP server, but it is possible to configure the virtual machine on a network without a DHCP server.

For more information about Nutanix Move, see the Go further section of this guide.

Configuring Nutanix Move

Logging in to the web interface and creating environments for migration

Connect to the IP address of the Nutanix Move virtual machine through a web browser in HTTPS, as follows: https://IPaddressNutanixMove/.

Read the licence conditions, accept them and click Continue.

MoveConfigure 01

Click OK to continue.

MoveConfigure 02

Select and confirm a password in the fields provided, then click Set Password to validate the creation of the Nutanix Move password.

MoveConfigure 03

Type the password in Password and click Log In to log into the Nutanix Move web interface.

MoveConfigure 04

Click + Add Environment.

MoveConfigure 05

Choose Nutanix AOS.

MoveConfigure 06

Enter the following information:

  • PRISM-CENTRAL-DESTINATION in the Environment Name field
  • the private IP address of Prism Central in the Nutanix Environment field
  • a Prism Central administration account in the Username field
  • the account password in the Password field

Click ADD to add the Prism Central environment.

MoveConfigure 07

Click Add Environment.

MoveConfigure 08

Choose Microsoft Hyper-V.

MoveConfigure 09

Enter the following information:

  • HyperV-SOURCE in the Environment Name field
  • the private IP address of the Hyper-V server in the Hyper-V Server/Cluster field
  • a Hyper-V administration account in the Username field
  • the password for this account in the Password field

Click ADD to add the Hyper-V environment.

MoveConfigure 10

Both migration environments appear in the top left-hand corner.

MoveConfigure 11

Creating a migration plan

We will create a migration plan from the two environments created previously.

The source will be the Hyper-V server, and the destination will be the Nutanix cluster.

Click Create a Migration Plan.

CreateMigrationPLan 01

Choose a name in the Plan Name field and click Proceed.

CreateMigrationPLan 02

Enter the following information:

  • HyperV-SOURCE in the Select a Source field
  • PRISM-CENTRAL-DESTINATION in the Hyper-V Server/Cluster field
  • the CLUSTER name in the Target Cluster field
  • the name of the destination container in the Target Container field

Then click Next to continue to the next step.

CreateMigrationPLan 03

Select the virtual machines you want to migrate from the Hyper-V environment to AOS by clicking on the + icon to the left of the VM.
Click Next to continue creating the migration plan.

CreateMigrationPLan 04

Choose the network in Target Network and click Next.

CreateMigrationPLan 05

Click Next to confirm the migration.

CreateMigrationPLan 06

Click Save to save the migration plan without running it.

CreateMigrationPLan 07

Launching the migration

After the migration plan is created, you can manually launch it.

Check the box next to the desired migration plan.

CreateMigrationPLan 08

On the Actions menu, click Start.

CreateMigrationPLan 09

The migration is in progress. The Status column gives you information on the status of the migration.

CreateMigrationPLan 10

Finalising the migration

Check the status of the migration by hovering over the In Progress status.
A window with the information Ready to Cutover N should appear, listing the number of VMs that can be migrated.

Click In Progress to start the completion process.

Cut Over 01

Select all the VMs by ticking the VM Name box and click Cutover.

Cut Over 02

Click Continue.

Cut Over 03

Wait a few moments while it completes.

Cut Over 03

The migration is complete when Completed appears in the Migration Status column.

Cut Over 03

Log into Prism Central to view the 3 migrated VMs that are present and running.

Cut Over 03

Changing the Disk Controller on a Linux Virtual Machine

If the virtual machine does not start properly after the migration, it may be due to a bad disk controller in the virtual machine configuration. In this case, it should be changed by following this procedure:

Go to the main menu of Prism Central and click on VMs.

Change Disk Controller 01

Make sure the virtual machine is turned off.

Change Disk Controller 02

Return to the main menu and click Images.

Change Disk Controller 03

Click Add Image.

Change Disk Controller 04

Select VM Disk as the Image Source. Type a name in Search by VM Name and click +.

Change Disk Controller 05

Type a name in the Image Name field and click Next.

Change Disk Controller 06

Select Place image on source VM's cluster and click Save.

Change Disk Controller 07

The image created from the virtual machine appears after a few moments.

Change Disk Controller 08

Open the main menu and click VMs.

Change Disk Controller 09

Check the box to the left of the virtual machine.

Change Disk Controller 10

Open the Actions menu and choose Update.

Change Disk Controller 11

Click on the trash can icon next to the CDROM drive.

Change Disk Controller 12

Click on the trash can icon next to the disk drive.

Change Disk Controller 13

Click Attach Disk.

Change Disk Controller 14

Select:

  • Disk In Type;
  • Select Clone from image;
  • Enter the name of the image created in Image;
  • Select PCI as the Bus type and click Save

Change Disk Controller 15

Click Next.

Change Disk Controller 16

Click Next.

Change Disk Controller 17

Click Save.

Change Disk Controller 18

The disk controller has been modified and the virtual machine boots properly.

Go further

Installation and configuration of Move

Join our community of users on https://community.ovh.com/en/.


Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.


These guides might also interest you...

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community