Nutanix Technology Champion - Nutanix Solution Architect

Julien DUMUR
Infrastructure in a Nutshell
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:

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:

Nutanix Move Create a Migration Plan button

Hyper-V to AHV migration plan name

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

Choosing the source Hyper-V cluster, target cluster and 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. Here I will only pick one virtual machine that I know is not supported, to show the manual method:

Selecting the VMs to migrate from Hyper-V

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:

Hyper-V to AHV network mapping

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.

Automatic VM preparation

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:

Windows and Linux VM credentials for preparation

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”:

Override individual VM Preparation option

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:

Manual preparation with the Windows and Linux scripts

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:

VM settings and data transfer scheduling

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:

Hyper-V to AHV migration plan summary

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

Hyper-V migration plan on the Nutanix Move home page

Other migration plans can be created in the same way.

Read More
nutanix move

Our Nutanix Move appliance is deployed, and the source clusters running VMware ESXi and Microsoft Hyper-V and the target cluster running Nutanix AHV have been added. The next step is to create the migration plans for our virtual machines.

Prerequisites

For everything to go well, some prerequisites must be taken into account, but the main ones are as follows:

  • VMware Tools deployed and up to date on all virtual machines
  • Supported operating systems

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

Creation of the migration plan from VMware ESXi to Nutanix AHV

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

Nutanix Move Create a Migration Plan button

ESXi to AHV migration plan name

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

Choosing the source cluster, target cluster and storage container

In our case, this gives:

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

Obviously, you will have to adapt the selected information to your environment. Depending on the type of server to migrate, you will have to choose the destination Storage Container wisely to adapt the data optimization mechanisms to the workloads you are migrating.

On the next screen, it is time to choose the virtual machines you want to migrate by clicking the “+” buttons at the start of each line:

Selecting the VMs to migrate from ESXi

In my case, I chose to select the Ubuntu_4 and Windows_4 virtual machines. A small Warning appears on the Windows machine because UEFI is only supported from AOS 5.16. My cluster being in 6.8.1, this will not be a problem.

On the next screen, it is the network mapping that must be done. For each network available on your ESXi cluster, you will have to assign a network from your Nutanix cluster:

ESXi to AHV network mapping

Here, I have only one network in my demo environment. If you have multiple networks on the ESXi side, 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.

Automatic VM preparation

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

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

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

Windows and Linux VM credentials for preparation

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”:

Override individual VM Preparation option

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:

Manual preparation with the Windows and Linux scripts

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:

VM settings and data transfer scheduling

Don’t panic, 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:

ESXi to AHV migration plan summary

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

ESXi migration plan on the Nutanix Move home page

Other migration plans can be created in the same way.

Read More
nutanix move

After the source cluster under VMware ESXi, we must now add the target cluster which run Nutanix AHV.

The process is similar to the one used previously for WMware ESXi and Microsoft Hyper-V clusters and I will start by adding an account dedicated to Move on my cluster.

Adding a Move service account

To add the service account dedicated to Nutanix Move on your Nutanix AHV cluster, connect to Prism Element then go to “Settings > Local User Management” and click on “New User”:

Local User Management in Prism Element

Fill in the fields with the necessary information and check the “Cluster Admin” role. Your service account is ready, now let’s add the Nutanix AHV cluster on Nutanix Move.

Adding the AHV cluster on Nutanix Move

In the “Environments” section of Nutanix Move, click on “+ Add Environment”:

Nutanix Move Environments section

Next, fill in the fields with the information corresponding to the Nutanix AHV cluster to which you want to migrate the VMs from the ESXi and Hyper-V clusters:

Adding the target Nutanix AHV cluster in Nutanix Move

The required information is as follows:

  • 1 – Environment type, select Nutanix AHV
  • 2 – Name the added cluster
  • 3 – Enter the IP address of the cluster (Prism Element or Prism Central of your choice)
  • 4 – Enter the logins and password of the service account previously created

Wait for a few minutes and your cluster will then be available in NutanixMove :

AHV cluster available in Nutanix Move

Your source and destination clusters are now all configured on Nutanix Move, the next step will be to create the migration plans.

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:

Windows Server Computer Management menu

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

Creating the local move user on Hyper-V

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

Adding the move 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\4.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:

Nutanix Move Add Environment button

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
Adding a Microsoft Hyper-V environment in Nutanix Move

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:

Hyper-V cluster added in Nutanix Move

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

Read More
nutanix move

Now that our Nutanix Move virtual machine is deployed, it is time to configure our first cluster to migrate: VMware ESXi.

Creating a Move account on ESXi

In order not to use the “root” account of my ESXi cluster and to respect good security practices, I preferred to create a user dedicated to Nutanix Move on my ESXi cluster.

Once connected to my cluster, on the host in “Manage”, go to “Security and users > Users”:

ESXi host Security and users menu

Click on “Add a user” and fill in the necessary fields:

Creating the move user on ESXi

Then, right-click on the host and click on “Permissions” then on “Add a user”:

ESXi host Permissions menu

Enter the name of the user previously created (in my case “move”) and assign him administration rights. Click on “Add a user”:

Assigning the administrator role to the move user

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

Adding the ESXi cluster on Nutanix Move

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

Nutanix Move Add Environment button

In the window that appears, you must:

  • 1 – select the type of VMware ESXi environment
  • 2 – name the environment that you are adding
  • 3 – enter the IP address of the vCenter or the ESXi host if there is only one node
  • 4 – enter the username and password of the service account created on ESXi
Adding a VMware ESXi environment in Nutanix Move

Click “Add” and wait while the cluster is added. If you followed all the steps, your cluster will appear in the list on the left of the Nutanix Move interface:

ESXi cluster added with a warning in Nutanix Move

In my case, small Warning on the ESXi cluster since a library is missing (if you have followed the previous articles, this is linked to the acquisition of VMware by Broadcom which no longer makes these files freely accessible, use an earlier version of Nutanix Move to avoid this problem). If you are in the same case as me, click on “Upload VDDK”:

Nutanix Move Upload VDDK button

Then click on “Upload” at the end of the line corresponding to the version of the clusters you wish to migrate (you can upload several if you have several cluster versions) to transfer the file(s):

Uploading VDDK files per cluster version

ATTENTION: you must have the VDDK files that you can find here (an active Broadcom customer account is required): https://developer.broadcom.com/sdks/vmware-virtual-disk-development-kit-vddk/latest

Once the addition of the VDDKs is complete, your ESXi source cluster is now operational:

ESXi source cluster operational in Nutanix Move

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

Read More
nutanix move

Once the deployment of the Nutanix Move appliance is complete, it remains to carry out its initial configuration in order to begin setting up future migration plans.

Network setup

To configure the network and switch to fixed IP, you must connect to the Move VM in SSH with the account “admin” and the password “nutanix/4u”. As this is the first connection, you will be asked to change the password.

Once the new password is configured, the network configuration tool launches automatically and you just have to follow the instructions:

Alpine Linux v3.16 (3.16.2) - Nutanix Move

Welcome to Nutanix Move. Please refer to the Move documentation
to know more about the console usage and troubleshooting.

https://www.nutanix.com/products/move/

Do you want to configure static IPv4 address? (y/N)
y
Enter Static IPv4 Address (e.g. 192.168.1.3)
192.168.2.240
Enter Netmask (e.g. 255.255.255.0)
255.255.255.0
Enter Gateway IP Address (e.g. 192.168.1.254)
192.168.2.254
Enter DNS Server 1 IP Address (e.g. 128.91.2.13)
8.8.8.8
Enter DNS Server 2 IP Address (e.g. 128.91.2.14)
8.8.4.4
Enter Domain (e.g. my.dc.domain)
homelab.local

Static IPv4 configuration provided:
ipaddress * 192.168.2.240
netmask * 255.255.255.0
gateway * 192.168.2.254
dns1 * 8.8.8.8
dns2 * 8.8.4.4
domain * homelab.local

Configuring static IPv4 …

WARNING: you are stopping a boot service
WARNING: you are stopping a boot service

Stopping busybox ntpd … [ ok ]
Stopping networking …
lo … [ ok ]
eth0 …

Please wait a few minutes while the reconfiguration completes.

First login

In the “My Apps” menu of the Admin Center, you can click on “Open” to access the Nutanix Move web interface:

Nutanix Move Open button in My Apps

The first thing you will be asked to do is accept the End User License Agreement:

Accepting the Nutanix Move End User License Agreement

You will then be asked to set up a password to secure access to Move:

Setting the Nutanix Move access password

And finally, choose the type of migration you want to perform. This choice has no impact on the rest of the events, you will be able to perform the 2 types of migration regardless of your choice:

Choosing the migration type in Nutanix Move

Congratulations, Nutanix Move is now deployed on your Nutanix cluster:

Nutanix Move deployed and ready

But that’s not all!

Nutanix Move Basic Configurations

There are still a few small configurations to be done to have an optimal Nutanix Move deployment. The appliance configuration is located in the gear menu at the top right, then in “Appliance Settings”:

Nutanix Move Appliance Settings menu

Among the options that can be customized, the only one that is of real interest to me is the NTP part to ensure consistent time synchronization across your entire Nutanix cluster:

Nutanix Move appliance options

For the NTPs, no problem since you just need to enter the same NTPs as those you configured on the Prism Element side:

Nutanix Move NTP server settings

The “Prism Central Registration” part is intended to override the Move authentication that you configured at the first connection by authentication via the accounts present in Prism Central that you wish to authorize to connect to the Nutanix Move appliance:

nutanix move

That’s it, your Nutanix Move is now ready to use. In the next blog posts we will see how to add ESXi, Hyper-V and AHV clusters and how to configure the first migration plan.

Read More
nutanix move

In the previous article I gave you a presentation of the infrastructure that I set up to produce my series of articles on Nutanix Move.

In this new article, we will see how to deploy the Nutanix Move virtual machine on our Nutanix AHV cluster.

Prerequisites and update of the Move image

The deployment of Nutanix Move on the latest versions of AHV with a Prism Central 2024 must be done from the marketplace, one of the new features of recent versions of Prism Central.

If you have not yet deployed Prism Central on your cluster in AOS 6.8: https://juliendumur.fr/en/nutanix-ce-2-1-deploy-prism-central-pc-2024/

Then, before deploying Nutanix Move, it is necessary to update the disk image integrated into Prism Central. To download the latest version of Move, go to the following link: https://portal.nutanix.com/page/downloads?product=move

You need to download the file “Move QCOW2 file for AHV”:

Downloading the Move QCOW2 file for AHV from the Nutanix portal

Then go to Prism Central, in “Infrastructure > Compute and Storage > Images” and click on “Add Image”:

Add Image button in the Prism Central Images menu

On the next page, click on “+ Add file”, select the image that has just been downloaded from the Nutanix website and click on “Next”:

Adding the Move image file with Add file

On the next page, leave as default and click “Save”:

Image placement options left as default

Please wait while the image is transferred and processed:

Move image upload and processing in Prism Central

Once this is done we can move on to deployment.

Nutanix Move deployment

To deploy Nutanix Move, you need to log in to Prism Central and go to the Marketplace menu in the Admin Center. In the drop-down menu at the top of the interface, select “Admin Center” and then click on “Marketplace”:

Admin Center Marketplace in Prism Central

Then, simply click on the “Get” button in the “Move” box and then on the “Deploy” button on the Move page to start the deployment process:

Deploy button of the Move application in the Marketplace

The page that is then displayed allows you to configure all the parameters that we want to assign to the Move virtual machine that we are going to deploy. The first field to modify is the “Application Name” field that must be filled in:

Application Name field of the Move deployment

In the following fields, no changes are needed to the VM name or its hardware configuration:

Move VM name and hardware configuration

For disk configuration, modify the image to select the one we transferred to the cluster previously:

Selecting the Move disk image

Select the network on which to place the Move virtual machine:

Selecting the Move VM network

Then enter the identifiers to assign to the SSH account:

Move SSH account credentials

The virtual machine deployment start:

Move application deployment completed at 100%

You can track the VM deployment on the “My Apps” page of the Admin Center, if you click on “Manage”:

Nutanix Move application in Admin Center My Apps

Nutanix Move application being provisioned

Once the deployment is complete and Nutanix Move is functional, the status will change to “Running”:

Nutanix Move application in Running status
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:

Network flows required by Nutanix Move

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.

Since Nutanix Move 6.3.3, two additional vCenter permissions are required to migrate from ESXi, and I detail them in Nutanix Move 6.3.3: DirectPath, Migration Without VDDK.

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
nutanix move

In my previous article, I presented Move, the Nutanix software that facilitates migration to AHV or any other supported hypervisor.

In order to write this series of posts, I set up the most representative environments of what we currently find at our customers. Let me introduce them to you so that you have the migration context.

The source clusters

I set up 2 separate clusters on 2 different hypervisors. The first cluster is a VMWare ESXi cluster on which I deployed 8 virtual machines: 4 Windows Server and 4 Linux.

Windows Server and Linux VMs on the source VMware ESXi cluster

The second cluster is a Microsoft Hyper-V cluster on which I also deployed 8 virtual machines with the same distribution as the first cluster: 4 Windows Server and 4 Linux.

Windows Server and Linux VMs on the source Hyper-V cluster

For convenience, the configuration of the VMs is very succinct. I have carried out default installations of the operating systems.

The Linux VMs are Ubuntu Server 20.04 while the Microsoft ones are Windows Servers 2022.

For local accounts, the Linux VMs have logins in “nutanix” and the Windows VMs in “administrator”. The password for all VMs is “nutanix/4u”.

The only difference in configuration between the virtual machines concerns those hosted on ESXi. Indeed, I deployed the VMWare tools on the latter.

The target cluster

The target cluster will be my Nutanix cluster under AOS 6.8.1 and AHV el8.nutanix.20230302.101026.

Target Nutanix AHV cluster in Prism

All migrations will be carried out via Nutanix Move in its version 5.1.1 which we will deploy in the next article.

Read More
nutanix move

Nutanix Move is a software solution designed by Nutanix to facilitate the migration of virtual machines (VMs) from a virtualization environment to a Nutanix infrastructure in a simple, secure way and with minimal downtime.

Key features of Nutanix Move

Nutanix Move allows you to move virtual machines from traditional hypervisors, such as VMware vSphere or Hyper-V, to Nutanix AHV (Acropolis Hypervisor) or other supported hypervisors. It supports various hypervisor environments such as VMware ESXi, Hyper-V, AWS, and Nutanix AHV. It is possible to migrate workloads from public or private cloud environments to Nutanix hyperconverged infrastructures.

Nutanix Move migration matrix between ESXi, Hyper-V, AWS, Azure, AHV and NC2

Nutanix Move ensures a migration by minimizing the downtime of services and applications, thus allowing continuity of operations during the entire transition process. In addition, you will not have to reconfigure anything once the virtual machine is migrated.

Move page in the Prism Central Marketplace and its features

Thanks to an intuitive interface, Nutanix Move simplifies the migration process by automating many manual tasks, which reduces the risk of human error and improves efficiency. However, certain prerequisites must be respected for the migration to take place in the best conditions

Nutanix Move allows you to evaluate workloads before migration, identifying potential issues in order to avoid any negative impact on application performance after migration. It also allows you to simulate your scenarios before executing them.

Nutanix Move architecture with its source and target agents

Use Cases

The use case we have encountered most often in recent months is that of companies seeking to reduce costs related to the explosion in the price of VMware licenses following the acquisition by Broadcom by migrating to Nutanix AHV.

For my part, I was also able to experiment with it on a remote desktop server migration from Hyper-V to Nutanix AHV and I must say that with each migration I am amazed by the simplicity and efficiency of the solution.

Having implemented it several times in a professional context, I can affirm that Nutanix Move is an essential tool for anyone wishing to modernize their IT infrastructure and facilitate their transition to a Nutanix hyperconverged environment.

See you in the next article to discover how to deploy the solution on Nutanix AHV.

Official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-

Read More