Team Leader - Nutanix Technology Champion - Nutanix NTC Storyteller

Julien DUMUR
Infrastructure in a Nutshell

It’s finally complete! After about fifty hours spent installing, configuring, testing a lab environment and writing each article, my ultimate Nutanix Move guide on migrating to Nutanix AHV is finally finished.

In total, this represents:

  • 6500+ words
  • 160+ screenshots
  • 50+ hours of work

This is clearly one of the most ambitious projects on my blog! To make it easier to find all of my current or future guides, I have created a dedicated link in the menu.

On the program:

Nutanix Move – Part 1: solution overview

Nutanix Move – Part 2: My migration environments

Nutanix Move – Part 3: Prerequisites

Nutanix Move – Part 4: Deployment

Nutanix Move – Part 5: Initial Setup

Nutanix Move – Part 6: Adding the VMware ESXi Cluster to Migrate

Nutanix Move – Part 7: Adding the cluster to migrate Microsoft Hyper-V

Nutanix Move – Part 8: Adding the Nutanix AHV Target Cluster

Nutanix Move – Part 9: ESXi to AHV Migration Plan

Nutanix Move – Part 10: Hyper-V to AHV Migration Plan

Nutanix Move – Part 11: Final Tips and Best Practices

Nutanix Move – Part 12 : VMs Migration

Nutanix Move – Part 13 : Post-migration network issues

Nutanix Move – Part 14 : Post-Migration Boot issues

The guide will probably evolve if I come across new interesting cases to share to expand my feedback.

Don’t forget that the success of your migration to Nutanix AHV will depend greatly on the preparation you do in advance.

You now have the keys to successfully migrating from Microsoft Hyper-V or VMware ESXi to Nutanix AHV.

And if you are still hesitant to take the plunge, do not hesitate to come and share your questions, your fears or even ask other people who have already been there to give you their feedback.

Other guides are coming soon… Stay tuned!

Read More
nutanix move

Now that everything is ready, it is time to migrate the virtual machines from the old Hyper-V and ESXi clusters to the new Nutanix AHV cluster using the migration plans previously created.

The different states

A migration plan can be in different distinct states depending on the stage of the migration:

  • Not Started: You have created the migration plans but have not yet started them
  • In Progress: The migration plan is launched, the data is starting to be replicated.
  • Ready to Cutover: The data migration is complete, Nutanix Move continues to synchronize the changes, the virtual machines are waiting to be switched to the target cluster.
  • Paused: You have paused the process for some reason. The data migration is suspended.
  • Failed: Error during the process of preparing the machines in general. The anomaly must be corrected in order to resume the operations.
  • Completed: The virtual machines that have been successfully migrated.

Starting migrations

If you have planned to start one of your migration plans like me, you should already have virtual machines in “Ready to Cutover” status.

This means that they are ready to complete their migration.

For other pending migration plans, you need to start them manually. To do this, check the box in front of the migration plans you want to start, click on the “Action” menu at the top of the list and click on “Start”:

The migration plan starts to execute:

If you followed all the steps correctly, the migration plan should go smoothly. You can track the progress of the plan on the corresponding line, and of the virtual machines in the boxes at the very top:

By clicking on the “2 VMs” in the banner, you will have a step by step guide for each virtual machine:

You can get more details on the operations carried out in the “Events” menu at the top right of the interface:

Synchronizing the data with the new cluster is the longest step of the process and will depend on the volume of your virtual machines.

The cutover

The cutover is the operation that will allow you to finalize the migration from the old cluster to the new one.

You can only perform a Cutover on virtual machines that are in the “Ready to Cutover” state:

To check the status of the virtual machines and proceed with the cutover, click on the “2 VMs” in the “Ready to cutover” frame:

You will then have the list of VMs ready to switch to the new cluster. You can do them all at once, or one by one, it doesn’t matter. It’s up to you. I will migrate Ubuntu_4 by checking the box at the beginning of the line and then clicking on “cutover”:

Validation is required to start the process:

The failover process only takes a few minutes during which Nutanix Move will:

  • Power off the VM
  • Create a final snapshot
  • Synchronize it with the target cluster
  • Create the target VM
  • Clean up the source VM (disconnect network cards)
  • Delete all snapshots created by Move
  • Consolidate the virtual machine disks
  • Clean up the target VM

The migration status for this virtual machine then changes to “Completed” and I find it on my Nutanix AHV, started and functional:

The virtual machine is successfully migrated, I just have to do all the others.

Read More
nutanix move

In the previous blog post, we saw how to create migration plans from ESXi to AHV. Now it’s Hyper-V’s turn and you’ll see that the process is almost identical!

Prerequisites

For everything to go well, some prerequisites must be taken into account and here are the 3 most important in my opinion:

  • Supported operating systems
  • Nutanix Move Agent installed on the hypervisor
  • Linux Azure installed on Linux virtual machines

All the prerequisites in the official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-hyperv-vm-migration-c.html

Creating the migration plan from Microsoft Hyper-V to Nutanix AHV

On the Nutanix Move interface, click on the “+ New Migration Plan” button and name the migration plan:

On the next screen, you must choose the source cluster on the one hand, then the destination cluster with the associated Storage Container:

Here, this gives:

  • 1 – HyperV Cluster
  • 2 – Nutanix Cluster
  • 3 – DefaultStorangeContainer

On the next screen, it’s time to choose the virtual machines you want to migrate by clicking on the “+” buttons at the beginning of the line. Ici je vais choisir uniquement une machine virtuelle que je sais non supportée pour la méthode manuelle :

Here, I chose to select the Ubuntu_4 and Windows_4 virtual machines.

On the next screen, it is the network mapping that needs to be done. For each network available on your Hyper-V cluster, you will need to assign a network from your Nutanix cluster:

Here, I have only one network in my demo environment. If you have multiple networks on your Hyper-V cluster, you will need to create them all on the AHV side in order to achieve an identical mapping on both sides.

The next window allows you to configure the preparation of virtual machines.

Automatic preparation of virtual machines

The recommended mode is the automatic mode because Nutanix Move will take care of all the operations once the machine login credentials are configured.

Please note that automatic mode only works on operating systems fully supported by Nutanix Move.

To check if the operating systems of your VMs are supported, I advise you to look in the official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-hyperv-vm-migration-c.html

You will then need to configure the identifiers of the Windows and Linux virtual machines:

The general option is only valid if you have set the same username and password on all your virtual machines (example for Windows: the domain administrator account).

If this is not the case, you can customize all the settings per virtual machine by clicking on “Change settings” under “Override individual VM Preparation”:

Manual preparation of virtual machines

The overall configuration remains the same, but when configuring the virtual machine preparation mode if you choose Manual mode you will have a different page:

No need to provide login credentials to virtual machines. On the other hand, all the automated preparation part carried out by Nutanix Move on your virtual machines will have to be done manually on each machine.

Nutanix Move provides scripts for Linux and Windows servers that you will have to run manually. A much more time-consuming option and source of potential errors that make me systematically prefer the automatic mode.

However, this migration mode may sometimes be necessary, particularly to migrate virtual machines whose operating system is not officially supported by Nutanix Move.

Finalizing the migration plan

On the next screen, the configuration of the virtual machines allows you to prioritize or not the migration operations, to choose the time zone that you wish to assign or even to schedule the start of the data transfer:

Don’t panic though, enabling data transfer does not mean that the machines will be migrated, simply the data of these machines will start to synchronize with the target cluster. This synchronization will continue as long as you do not trigger the migration.

Once your configurations are complete, Move will display a summary of your migration plan:

Click on “Save” to validate it, your migration plan is ready and you can find it on the Nutanix Move home page:

Other migration plans can be created in the same way.

Read More
nutanix move

Now that our Nutanix Move virtual machine is deployed, it is time to configure our second cluster to migrate: Microsoft Hyper-V.

Creating a Move account on Hyper-V

In the same spirit as for ESXi, in order not to use the “administrator” account of the server or domain and to respect good security practices, I created a user dedicated to Nutanix Move on my Hyper-V cluster.

Once connected to my cluster, right-click on the “Start > Computer Management” button:

Click on “Local Users and Groups > Users” in the Action menu click on “New User” and fill in the necessary fields:

Then, in “Local Users and Groups > Groups”, add the previously created account to the “Administrators” group:

The service account dedicated to Nutanix Move is created on the Hyper-V cluster, now let’s add the cluster on the Nutanix Move side.

Installing the Move Agent

Before you can add your Hyper-V cluster to Nutanix Move, it is imperative to install the Move Agent.

To download it, go to the following URL: https://MOVE-IP/downloads/agents/move-agent-installer.exe by replacing “MOVE-IP” with the IP address you assigned to Nutanix Move.

Once the executable is downloaded, move it to the directory of your choice, for my part I put it at the root of the hard drive. You must then open a Powershell command prompt in administrator mode and run the following command:

move-agent-installer.exe -o install -ip MOVE-IP -u USER

Always replacing MOVE-IP with the IP address of your Nutanix Move and USER with the login of the service account dedicated to Move previously created:

PS C:> .\move-agent-installer.exe -o install -ip 192.168.2.240 -u move
Enter password for user [move]:

Hyper-V host pre-checks results:

OS validation successful: [Microsoft Windows Server 2022 Standard Evaluation]

Firewall: Inbound port [8087] is open

Service state: [Hyper-V Virtual Machine Management] is running

Service install successful. Please check logs at [C:\Users\move\Nutanix\Move.7.0\logs].
PS C:>

Adding the Hyper-V cluster on Nutanix Move

To add the Hyper-V environment on Nutanix Move, you need to connect to the Move interface and click on the “+ Add Environment” button on the home page:

In the window that appears, you must:

  • 1 – select the Microsoft Hyper-V environment type
  • 2 – name the environment that you are adding
  • 3 – enter the IP address of the cluster or server if there is only one node
  • 4 – enter the username and password of the service account created on Hyper-V

Click “Add” and wait while the cluster is added. You may encounter an error regarding WinRM while adding the cluster. If this is the case, connect to the Hyper_V cluster and type the following powershell command:

winrm quickconfig

If you followed all the steps, your cluster will appear in the list on the left of the Nutanix Move interface:

Official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-upload-vddk-library-t.html

Read More
nutanix move

Before starting the process that will allow you to migrate all of your virtual machines to your new Nutanix AHV environment, a quick overview of the prerequisites is required.

General prerequisites

In terms of general prerequisites, there are a few things to respect and check before starting the migration of your infrastructure.

You can migrate everything, with 2 exceptions

The first thing to know is the types of machines to migrate. You can migrate all of your virtual machines with Nutanix Move, except:

  • domain controllers
  • Exchange servers

These are the only 2 restrictions of the software. It is recommended to install a new domain controller, migrate the FSMO roles to it, promote it to a primary domain controller and depromote the old one. Regarding Exchange, you will have to reinstall a server and transfer all of the data from the old server.

Network Flows

Obviously, since we are talking about a migration via the network, it is imperative that the flows are open to allow Nutanix Move to reach the source and destination clusters:

An upcoming update of my flow matrix is ​​planned to integrate the Move part.

Administrator account with privilege

For Nutanix Move to perform the operations required for migrations on the different source and destination clusters, it is imperative to have accounts with administrator rights on these clusters.

Prerequisites specific to VMware ESXi clusters

Supported operating systems

To date, the majority of operating systems used in a professional environment on ESXi are supported by Move.

You can find the supported operating systems for a migration from ESXi directly in the official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-migration-considerations-c.html

If one of your virtual machines is not compatible for a Nutanix Move migration (I invite you to carry out tests, unsupported does not mean non-functional), you will then have to consider carrying out a complete and up-to-date reinstallation on the new cluster.

VMware Tools

It is important that VMware tools are deployed on all of your virtual machines so that Nutanix Move can manage the virtual machines hosted on the source ESXi cluster optimally. This will avoid warnings or failures when you launch the migration processes.

All ESXi prerequisites are available here: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-migration-considerations-c.html

Specific prerequisites for Microsoft Hyper-V clusters

Supported operating systems

To date, the majority of operating systems used in a professional environment on Hyper-V are supported by Move.

You can find the operating systems supported by Move for a migration from Hyper-V directly in the official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-hyperv-vm-migration-c.html

If one of your virtual machines is not compatible for a Nutanix Move migration (I invite you to carry out tests, not supported does not mean non-functional), you will then have to consider carrying out a complete and up-to-date reinstallation on the new cluster.

Nutanix Move Agent

On the Hyper-V cluster, for this to work, it will be imperative to deploy the Nutanix Move Agent. I will detail the agent installation procedure in the following articles.

It’s here in the official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-deploy-nt-service-t.html

All the Hyper-V prerequisites are here: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_4:top-migration-considerations-hyperv-ahv-c.html

Linux Azure

For Linux VMs, you also need to install an add-on on each of them using the following command:

sudo apt install linux-azure

Linux Azure is a kind of VMware tools for Hyper-V and reserved for Linux machines.

In the next blog post, we will deploy the Move machine on our Nutanix AHV cluster.

Read More