Nutanix TN 2072 ESXi AHV Migration Version 2.2
Nutanix TN 2072 ESXi AHV Migration Version 2.2
Nutanix TN 2072 ESXi AHV Migration Version 2.2
Nutanix AHV
Nutanix Tech Note
Copyright
Copyright 2018 Nutanix, Inc.
Nutanix, Inc.
1740 Technology Drive, Suite 150
San Jose, CA 95110
All rights reserved. This product is protected by U.S. and international copyright and intellectual
property laws.
Nutanix is a trademark of Nutanix, Inc. in the United States and/or other jurisdictions. All other
marks and names mentioned herein may be trademarks of their respective companies.
Copyright | 2
Migrating from ESXi to Nutanix AHV
Contents
1. Migration Overview................................................................................. 4
5. Conclusion............................................................................................. 19
Appendix......................................................................................................................... 20
Nutanix Enterprise Cloud Overview....................................................................................20
About Nutanix......................................................................................................................21
List of Figures................................................................................................................22
List of Tables................................................................................................................. 23
3
Migrating from ESXi to Nutanix AHV
1. Migration Overview
Methods for performing cross-hypervisor migrations can vary greatly, and administrators should
scope them based on a specific environment’s requirements. Each migration scenario includes
unique technical and business needs. Some factors to consider when planning a migration
include:
• Downtime requirements for specific applications.
• Whether the source and target for a migration are physical operating systems or virtualized
environments.
• Whether the source and target for a migration run on the same infrastructure vendor, where
you can use native replication tools.
• Whether native application-level methods exist, including integrated replication technologies
used for high availability and disaster recovery or backup and restore.
• Whether you need to make changes to an application as a part of the migration, such as
moving to a newer version or modifying the physical layout of a database.
• Whether you need to move the physical location of the environment, which could impact
existing networking configurations and data replication considerations.
• The trade-offs inherent in using third-party technologies that can simplify migrations and limit
downtime but also add to the total cost of the project.
• Ensuring that the team has the skills and experience to perform the migration with minimal
impact to the business.
The list above is certainly not exhaustive, but it outlines some of the complexities involved in
executing a successful migration project. We don’t cover all of these considerations in depth
here; instead, this guide provides high-level guidance on the recommended methods for
performing migrations between ESXi environments and Nutanix AHV. We address native Nutanix
migration methods, from third-party platforms or from Nutanix platforms, as well as third-party
migration software that can help simplify the process.
Nutanix also provides a workload migration offering through Nutanix Services. Learn about the
specific workload migration services at https://www.nutanix.com/support-services/consulting-
services/.
1. Migration Overview | 4
Migrating from ESXi to Nutanix AHV
Version
Published Notes
Number
1.0 February 2017 Original publication.
2.0 December 2017 Updated for AOS 5.5 and added product information.
Updated Nutanix overview and the AHV Migration
2.1 May 2018
Considerations section.
2.2 October 2018 Updated product information.
1. Migration Overview | 5
Migrating from ESXi to Nutanix AHV
running on the target system. Some of these third-party and application-centric options are also
outlined in the following sections.
You can also import virtual disks directly from an external HTTP or NFS source URL, or upload
them from your local machine. The import process creates a RAW virtual disk and stores it as an
image. You can then create a new VM set to reference this stored disk image.
The general migration process uses the following steps:
1. Ensure that you’ve met the VM migration prerequisites.
2. Install Nutanix VM Mobility drivers or validate that the VirtIO driver modules are installed.
3. Migrate the VM disks to the DSF.
4. Convert the VM disks by using the image service.
5. Create a new VM and attach the converted disks.
For details specific to migrating Windows-based VMs from ESXi to AHV using the above steps,
please refer to the relevant section of the Migration Guide.
For details specific to migrating Linux-based VMs from ESXi to AHV using the above steps,
please refer to the relevant section of the Migration Guide.
Xtract performs checks to ensure that the target environment has enough compute and storage
resources to support the VMs added to a migration plan. Xtract can sort VMs by whether or
not you can migrate them and provides a summary to indicate why certain VMs cannot be
migrated, such as not having VMware tools installed or not meeting virtual hardware version
level minimums, among other requirements. From a virtual guest operating system perspective,
Xtract for VMs supports all of the operating systems that AHV supports. A full list of the operating
systems supported by Xtract is available in the Xtract for VMs documentation.
Xtract uses VMware vSphere Storage APIs: Data Protection (VADP) to manage the replication
process, so you do not need to have agents installed within the VMs or the ESXi hosts. You
have the option to allow Xtract to connect to VMs directly in order to install the VirtIO drivers
compatible with AHV and to capture network settings to carry over to the target environment.
You can specify the credentials to connect to the VMs selected within a plan either for all VMs at
once, or individually as needed.
You can also specify network mappings to match the source and destination networks for the
VMs. By defining a migration schedule, you can set data seeding to start within a predetermined
window.
Once you have configured the options described above, the migration can begin, using VADP
to seed the data to the AHV cluster. This process entails creating ESXi-based snapshots for
each VM, then replicating the virtual disks to the specified AHV container. You can pause or
abort migrations in progress at any time. Xtract stores the vmdk files for the migrating VMs in
a temporary folder and incrementally uses changed block tracking (CBT) APIs and continued
snapshot operations to keep them up to date.
When it’s time to cut over and complete the migration, Xtract powers off the source VMs
and disconnects the virtual NICs. Incremental data is then synchronized over to the AHV
cluster. Once all data replication is complete, Xtract uses the AHV image service to convert
the vmdk files to the native RAW format used by AHV. Because the disk formats are the same,
conversion from vmdk to RAW is extremely fast—each disk is converted in just a few seconds,
limiting downtime. Xtract also provides an estimated cutover time, so you can determine any
maintenance window in advance.
You can choose to cut over VMs within a plan either together or separately. To complete the
migration, Xtract powers the VMs on in the target environment and removes all temporary vmdk
files and converted images within the AHV image service. Although the source VMs are now
powered off and disconnected from their networks, they persist in case you need them for any
reason.
Xtract keeps track of which VMs you’ve migrated and which ones remain to be moved, so if you
create additional migration plans, it’s easy to know what’s left to be done.
• Microsoft Exchange Server: Install newer versions in parallel with existing production
environments, then move user mailboxes from the old system to the new one.
• Microsoft SQL Server: Back up databases and restore them between systems, including
between older and newer SQL Server versions. Always On Availability Groups can also
replicate databases between SQL Server instances, not only to migrate data but also to
implement a high-availability solution at the same time.
• File shares: Copy files between a source and a target with a tool such as Robocopy to
execute a migration. In environments that use Microsoft Distributed File System (DFS), you
can add new servers to a DFS namespace and use them to host new copies of DFS replicas.
After DFS performs the replication, you can remove the replicas from the old systems.
given local or remote snapshot. Also, because a VM targeted for conversion must have VM
Mobility drivers installed, Prism gives a warning if the installation status is unknown.
For additional details, including instructions on how to use Nutanix VM Mobility, see the Nutanix
Portal.
• All uplinks must be homogenous (that is, they must have the same adapter speed—all 10 Gb
or all 1 Gb).
• LACP-based virtual switch load balancing is not supported.
• You can’t convert VMs with delta disks from ESXi to AHV.
The general conversion process is as follows:
1. Select Convert Cluster from Prism Element.
2. Select the target hypervisor and VM boot options.
a. You can choose to keep the original power state of the VMs post conversion, or power off
VMs before conversion.
3. Cluster validation determines if requirements are met or if limitations exist.
4. If there are no blocking limitations, the conversion process may proceed. Prism displays
warnings when applicable, including:
a. If an existing active-active network team would become active-passive on conversion.
b. If specific VMs do not have NGT enabled, preventing confirmation of VM Mobility driver
installation.
5. Once the conversion begins, the following high-level steps occur:
a. The Acropolis conversion process collects and saves hypervisor information. The cluster
remains manageable during the conversion process.
b. User VMs live migrate from the node targeted for conversion to other nodes in the cluster.
c. Acropolis converts the node evacuated in the previous step to the targeted hypervisor.
d. The process restores user VMs to the newly converted node one by one. Each VM is then
also converted. Running VMs experience downtime similar to the duration of one power-off
and one power-on cycle.
e. Once the targeted node and all original VMs have been converted, the process moves on
to the next node.
f. When all nodes are using the targeted hypervisor, the conversion is complete.
For additional details, including instructions for using cluster conversion, see the Nutanix Portal.
5. Conclusion
Migrations are necessary to ensure that organizations can replace aging systems while taking
advantage of stronger technologies that can add business value. A robust migration methodology
lowers risk and ensures minimal disruption. The processes we outlined in this document
represent an array of supported migration options, each with advantages for specific use cases.
Consult with Nutanix Support and Services to help you select the best migration method for your
environment. We plan to add more techniques to this document over time, including Nutanix
offerings for automating migration at both the application and VM layers.
5. Conclusion | 19
Migrating from ESXi to Nutanix AHV
Appendix
Appendix | 20
Migrating from ESXi to Nutanix AHV
About Nutanix
Nutanix makes infrastructure invisible, elevating IT to focus on the applications and services that
power their business. The Nutanix Enterprise Cloud OS leverages web-scale engineering and
consumer-grade design to natively converge compute, virtualization, and storage into a resilient,
software-defined solution with rich machine intelligence. The result is predictable performance,
cloud-like infrastructure consumption, robust security, and seamless application mobility for a
broad range of enterprise applications. Learn more at www.nutanix.com or follow us on Twitter
@nutanix.
Appendix | 21
Migrating from ESXi to Nutanix AHV
List of Figures
Figure 1: Image Creation from a Migrated Virtual Disk.....................................................9
22
Migrating from ESXi to Nutanix AHV
List of Tables
Table 1: Document Version History.................................................................................. 5
23