Workload Migration - Deployment and Operations Guide

LAST UPDATED: 2022.
12
SDK – WORKLOAD MIGRATION
Deployment & Operations

Guide
Workload Migration: Deployment & Operations Guide
2021.09
In preparing this document, we have made every effort to ensure the accuracy of all the information
and statements contained within it but recognize that there may be minor errors.
Please do not hesitate to contact us at any time to discuss the contents of this document.
We very much look forward to working with you on developing and delivering this solution and aim
to provide you with the very best service that our Industry has to offer.
Prepared for: <<Client POC>>
Prepared by: <<Enter Consultant Name Here>>
Organization: <<Enter Customer Name Here>>
Document Reference: Workload Migration: Deployment &

Operations Guide
Content Last Updated: 2021.09
© Copyright 2021 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 other jurisdictions. All other marks and names
mentioned herein are trademarks of their respective companies.
Template version 2021.08
P a g e |3
Tel: 1 (855) 688-2649 | Fax: 1 (408) 916-4039 | Email: info@nutanix.com
2021.09
Contents
1 EXECUTIVE SUMMARY – MIGRATION TO NUTANIX.................................5
1.1 Nutanix Move..........................................................................................................................5
1.2 VMware Shared-Nothing vMotion...........................................................................................5
1.3 Microsoft Shared-Nothing Live Migration...............................................................................6
1.4 VMware Converter...................................................................................................................6
1.5 Carbonite Migrate....................................................................................................................6
2 MIGRATION TOOLS DEPLOYMENT................................................................7

2.1 Nutanix Move..........................................................................................................................7
2.2 VMware Converter...................................................................................................................7
2.3 Carbonite Migrate....................................................................................................................7
3 MIGRATION USE CASE MATRIX......................................................................8
4 VIRTUAL TO VIRTUAL (V2) MIGRATION TO NUTANIX SCENARIOS...........9

4.1 Nutanix Move..........................................................................................................................9
4.1.1 General Prerequisites.................................................................................................................................9
4.1.2 General Limitations...................................................................................................................................9
4.1.3 General Migration Steps..........................................................................................................................10
4.2 VMware Shared-Nothing vMotion.........................................................................................15

4.2.1 Workflow................................................................................................................................................16
4.2.2 Prerequisites............................................................................................................................................16
4.2.3 How To: Shared-Nothing vMotion.........................................................................................................17
4.3 Hyper-V Shared-Nothing Live Migration..............................................................................17

4.3.1 General Prerequisites...............................................................................................................................18
4.3.2 General Limitations.................................................................................................................................18
4.4 System Center VM Manager Live Migration.........................................................................25
P a g e |4
2021.09
4.4.1 Live Migration with No Shared Infrastructure........................................................................................25

5 PHYSICAL TO VIRTUAL (P2V) MIGRATION TO NUTANIX SCENARIOS 30

5.1 VMware Converter.................................................................................................................30
5.2 Carbonite Migrate..................................................................................................................36

5.2.1 Prerequisites............................................................................................................................................36
5.2.2 Windows How-To...................................................................................................................................36
5.2.3 Linux How To.........................................................................................................................................48
5.2.4 Licensing Carbonite on a Server without an Internet Connection..........................................................59
A. GLOSSARY..........................................................................................................64
B. USE IF NEEDED..................................................................................................65
P a g e |5
2021.09
1Executive Summary – Migration to

Nutanix
1.1 NUTANIX MOVE
Nutanix Move helps streamline virtual machine (VM) migrations to a Nutanix Enterprise Cloud and
automates the migration of full database instances while applying proven Nutanix best practices.
Benefits of Nutanix Move include:
 Streamlined migrations with one-click simplicity
 Near-zero downtime with full cutover control
 Simple test migrations and roll-back capabilities
 Cost-efficient - included with all Nutanix software editions
Adopting new infrastructure platforms against tight timescales often requires organizations to migrate
pre-existing workloads. Nutanix Move for VMs simplifies this process with infrastructure-level bulk
VM migrations, removing the friction associated with onboarding new IT infrastructure. The service
also enables businesses to quickly leverage the full potential of Nutanix Enterprise Cloud, with near-
zero VM or application service outage during migrations.
Nutanix Move for VMs provides granular, project-based control with an easy-to-use user interface
(UI) for automated workload migrations in a simple three-step process.
1.2 VMWARE SHARED-NOTHING VMOTION

Shared-Nothing vMotion or storage vMotion are built-in features of VMware vSphere products.
These features can be used during migration from three-tier legacy infrastructure to Nutanix with
VMware vSphere.
 Shared-Nothing vMotion is available on vSphere 5.1 and newer. It is applicable when the customer
requires ZERO downtime for migrated applications and when no additional VM reconfiguration is
required
 Storage vMotion should be used in cases when it is impossible to leverage Shared-Nothing vMotion
or when additional VM reconfiguration is needed
P a g e |6
2021.09
NOTE: Migration using storage vMotion requires VM downtime.
1.3 MICROSOFT SHARED-NOTHING LIVE MIGRATION

Live migration is a Hyper-V feature in Windows Server. It allows you to transparently move running
VMs from one Hyper-V host to another without perceived downtime. The primary benefit of live
migration is flexibility; running Virtual Machines are not tied to a single host machine.
1.4 VMWARE CONVERTER

VMware vCenter Converter Standalone provides an easy-to-use solution that automates the process
of creating VMware virtual machines from physical machines (running Windows and Linux) and
other virtual machine formats.
1.5 CARBONITE MIGRATE

Carbonite Migrate allows you to easily migrate physical, virtual, and cloud workloads to and from
any environment with minimal risk and near-zero downtime. Options for finely tuned automation
help orchestrate every stage of the process.
P a g e |7
2021.09
2Migration Tools Deployment

2.1 NUTANIX MOVE
Details on deploying the Nutanix Move appliance for use with migrations are available on the
Nutanix Support Portal. Note that the documentation links are version dependent, always verify that
the correct version of the document is used for reference:
 Nutanix Move 4.1 User Guide - Move Deployment

Details on deploying VMware Converter for use with migrations are available from the VMware
documentation web site:
 Installing and Uninstalling Converter Standalone

Details on the installation and licensing of Carbonite Migrate can be found at the following location:
 Carbonite Migrate Installation Guide
 Carbonite Migrate Windows User's Guide
P a g e |8
2021.09
3Migration Use Case Matrix

The table below provides an overview of the use cases addressed in the document:
Source/Target Nutanix Nutanix Nutanix Nutanix AWS AWS EC2

AHV ESXi Hyper-V
Legacy ESXi YES YES NO YES NO
Nutanix ESXi YES YES NO YES YES
Legacy Hyper-V YES YES YES YES NO
Nutanix AWS YES YES NO NO NO
AWS EC2 YES YES NO YES N/A
Azure YES YES NO NO NO
Nutanix AHV NO YES NO NO YES
Physical Server YES YES YES YES NO
P a g e |9
2021.09
4Virtual to Virtual (V2) Migration to

Nutanix Scenarios
4.1 NUTANIX MOVE
Nutanix Move supports the following migration scenarios:
 ESXi to Nutanix Clusters on AWS and AHV VM Migration
 ESXi to ESXi VM Migration
 Hyper-V to Nutanix Clusters on AWS and AHV VM Migration
 AWS to Nutanix Clusters on AWS and AHV VM Migration
 AWS to ESXi VM Migration
 AHV to AWS VM Migration
 Azure to AHV VM Migration
 Azure to ESXi VM Migration
4.1.1 General Prerequisites
Move has many prerequisites that are dependent on the specific migration source and destination
hypervisors, as well as the VM guest OS. Refer to the Move user guide for the list of all pre-
requisites.
4.1.2 General Limitations
Move has many limitations that are dependent on the specific migration source and destination
hypervisors, as well as the VM guest OS. Refer to the Move User Guide for the list of all limitations.
4.1.3 General Migration Steps
In general, follow the steps below to perform a VM migration to Nutanix AHV using Nutanix Move.
P a g e | 10
2021.09
1. From the Move home screen, click Create a Migration Plan

2. Give the migration plan a name, then click Proceed:
3. On the Source and Target page, select the appropriate migration source, target and target storage
container, then click Next:
4. On the Select VMs page, click the blue plus icon beside each VM to be added to the migration
plan, then click Next
5. On the Network Configuration page, select the target VM network and the desired Test network
(if necessary), then click Next:
P a g e | 11
2021.09
6. On the VM Preparation page, select either Automatic or Manual preparation, provide

credentials, if necessary, set the VM time zone and MAC address preservation settings and then
click Next.
P a g e | 12
2021.09
7. On the Summary page, verify the details are correct and then click Save and Start
P a g e | 13
2021.09
8. Monitor the migration plan validation and initial data seeding from the Move main screen:
9. Once the initial data seeding for the VM has completed, the VM appears in Ready to Cutover
status, click the In Progress link in the Migration Plan’s status column to see the status of
individual VMs within the Plan:
10. Check the box next to the name of the VM to be migrated and then click the Cutover button:
P a g e | 14
2021.09
11. On the confirmation dialog box, click Continue
12. Monitor the progress of the cutover in the Migration Plan’s information screen:
P a g e | 15
2021.09
13. The migrated VM is now visible in Prism:
14. At this time, perform any post-migration validations required.
4.2 VMWARE SHARED-NOTHING VMOTION

VMware Shared-Nothing vMotion is the easiest method to move VMs from a legacy VMware
vSphere cluster to a Nutanix vSphere cluster.
P a g e | 16
2021.09
4.2.1 Workflow
VMware Shared-Nothing vMotion
4.2.2 Prerequisites
 vSphere 5.5 - Requirements and Limitations for vMotion Without Shared Storage
P a g e | 17
2021.09
4.2.3 How To: Shared-Nothing vMotion
To ensure no downtime for VMs when using vMotion, both clusters must have the same EVC
baseline or belong to the same CPU family.
1. Make sure you change disk format to THIN PROVISIONED
2. Choose target datastore (Nutanix container)

3. Click Next à Finish
4. Wait for storage vMotion to complete
4.3 HYPER-V SHARED-NOTHING LIVE MIGRATION

Microsoft Hyper-V Shared-Nothing live migration helps you move VMs from legacy Hyper-V
clusters to Nutanix clusters with Hyper-V.
Windows Server 2012 TO/FROM Windows Server 2012
Windows Server 2012 TO Windows Server 2012 R2
Windows Server 2012 R2 TO/FROM Windows Server 2012 R2
Windows Server 2012 R2 TO Windows Server 2016
Windows Server 2016 TO/FROM Windows Server 2016
P a g e | 18
2021.09
These are the general prerequisites for performing a shared-nothing live migration between Hyper-V
hosts. Always reference the official documentation for any new or changed requirements.
 A user account with administrative privileges on both source and destination Hyper-V servers
o The account will need to be a member of the Domain Administrators group if using
constrained delegation
 A minimum of VM version 5 to enable migrations from Windows Server 2012 R2 and Windows
Server 2016
 Source and destination Hyper-V servers must be members of the same Active Directory domain or
belong to domains that trust each other
 The source and destination VM hosts must be running on CPUs from the same vendor; for example,
you can’t live migrate a VM between Intel and AMD servers
 The destination VM host must be running the same or newer CPU generation than the host and have a
superset of all available CPU instruction sets; otherwise, the Live Migration fails due to CPU
incompatibility. This can be worked around by enabling CPU compatibility on the VM; however, this
requires a VM shutdown to enable.
 The source VM host IP addresses must be added to the Nutanix cluster’s filesystem white list so that
they can perform the storage portion of the Live Migration
 Use Live Migration Without Failover Clustering to Move a Virtual Machine
General limitations for performing a shared-nothing live migration between Hyper-V hosts are listed
below. Always reference the official documentation for any new or changed requirements.
 You can’t Live Migrate VMs that are using shared virtual disks (i.e., guest clusters)
 You can’t Live Migrate VMs being replicated by Hyper-V replica
 The VM configuration version must be compatible with the destination host (i.e., if you upgrade the
VM configuration version beyond version 5, you can’t migrate that VM back to a Windows Server
2012 R2 host server)
 VMs must be removed from the Microsoft Windows failover cluster before performing the Live
Migration
The steps below generally describe the process of performing a Shared-Nothing Live Migration
between two Hyper-V hosts:
P a g e | 19
2021.09
1. Remove the VM from the failover cluster by right-clicking the VMs resource group in Failover
Cluster Manager and choosing Remove
2. Open the Hyper-V Manager on the VMs host server

3. Right-click the VM in the VMs list and choose Move…
4. On the Before you Begin page, click Next

5. On the Choose Move Type page, select Move the Virtual Machine and then click Next
P a g e | 20
2021.09
6. On the Specify Destination Computer page, enter the name of the target VM host to which the
VM will move and then click Next
7. On the Choose Move Options page, select Move the virtual machine’s data to a single location
and then click Next
8. On the Choose a new location for the virtual machine page, enter the path to the storage location
where the VM will reside. This should be a location on the Nutanix storage container of the
destination cluster. Add the VM’s name to the end of the path and then click Next
P a g e | 21
2021.09
9. On the Completing Move Wizard page, review the migration description information for accuracy
and then click Finish
A progress bar displays showing the percentage completion of the migration. Additionally, the
Status column in the Hyper-V Manager shows the description of the current action and the
percentage complete:
P a g e | 22
2021.09
Once the migration is complete, there are no further prompts. The progress dialog window
disappears and the VM is no longer visible in the Hyper-V manager:
P a g e | 23
2021.09
10. Open the Hyper-V Manager on the target VM host to verify that the VM now exists on that host
and that the VM is running:
11. Add the VM into the failover cluster on the target by using the Failover Cluster manager’s Add
Roles wizard to select the migrated VM and make it highly available:
P a g e | 24
2021.09
12. At this point, perform any post-migration validations required
4.4 SYSTEM CENTER VM MANAGER LIVE MIGRATION
4.4.1 Live Migration with No Shared Infrastructure
System Center VM Manager can be used to perform Live Migrations between two Hyper-V
hosts/clusters:
 SCVMM 2016 - Run a Live Migration in the VMM Fabric
 SCVMM 2019 - Run a Live Migration in the VMM Fabric
The general prerequisites for performing an SCVMM Live Migration between Hyper-V hosts are
listed below. Always reference the official documentation for any new or changed requirements.
 Both the source and destination Hyper-V hosts/clusters must be managed by the same SCVMM
infrastructure
 A minimum of VM version 5 is necessary to enable migrations from Windows Server 2012 R2 and
Windows Server 2016
 Source and destination Hyper-V servers must be members of the same Active Directory domain or
belong to domains that trust each other
 The source and destination VM hosts must be running on CPUs from the same vendor; for example,
you can’t live migrate a VM between Intel and AMD servers
 The destination VM host must be running the same or newer CPU generation than the host and have a
superset of all available CPU instruction sets, otherwise the Live Migration fails due to CPU
incompatibility. This can be worked around by enabling CPU compatibility on the VM; however, this
requires a VM shutdown to enable
P a g e | 25
2021.09
 The source VM host IP addresses must be added to the Nutanix cluster’s filesystem white list so that
they can perform the storage portion of the Live Migration
 The Nutanix storage container must be configured as a registered file share on both the source and
target clusters within SCVMM
 Use Live Migration Without Failover Clustering to Move a Virtual Machine
General limitations for performing an SCVMM Live Migration between Hyper-V hosts are listed
below. Always reference the official documentation for any new or changed requirements.
 You can’t Live Migrate VMs using shared virtual disks (i.e. guest clusters)
 You can’t Live Migrate VMs being replicated by Hyper-V replica
 The VM configuration version must be compatible with the destination host (i.e., if you upgrade the
VM configuration version beyond version 5, you can’t migrate that VM back to a Windows Server
2012 R2 host server)
 VMs must be removed from the Microsoft Windows failover cluster before performing the Live
Migration
The steps below generally describe the process of performing an SCVMM Live Migration between
two Hyper-V hosts:
1. Remove the VM from the failover cluster by right-clicking the VM’s resource group in Failover
Cluster Manager and choosing Remove
P a g e | 26
2021.09
2. From the SCVMM console, right-click the VM to be migrated and select Migrate Virtual
Machine
3. On the Select Host page, choose the destination Hyper-V host, verify that the Transfer Type is
Live (VSM) and then click Next:
P a g e | 27
2021.09
4. On the Select Path page, verify that the UNC path to the Nutanix storage container is present,
then click Next:
5. On the Select Networks page, modify the Virtual Switch and VLAN ID for the target VM, if
necessary, then click Next:
6. On the Summary page, verify the migration details and then click Move:
P a g e | 28
2021.09
7. Change to the SCVMM Jobs view and monitor the migration task’s progress:
8. When the task completes, verify in the VMs and Services view that the VM is now present on the
target host:
9. At this point, perform any post-migration validations required
P a g e | 29
2021.09
5Physical to Virtual (P2V) Migration

to Nutanix Scenarios
VMware Converter can be used to migrate a physical server to a VMware vSphere VM running on
Nutanix.
There are many prerequisites and requirements for VMware Converter that are version- and
configuration-dependent. Always review them and ensure compatibility before proceeding:
 VMware Converter System Requirements
There are many limitations of VMware Converter that are version- and configuration dependent.
Always review them and ensure compatibility before proceeding:
 VMware Converter Conversion Limitations
Follow the general steps below to perform a P2V migration to VMware vSphere on Nutanix using
VMware Converter.
1. Click the Convert Machine button to create a new P2V task
2. On the Source System page, select a Powered On Remote Windows Machine and enter the IP
address and administrator credentials of the remote machine.
3. Click the View Source Details link and VMware Converter connects to the source and deploy the
Converter Agent and then display the information about the server:
P a g e | 30
2021.09
4. Click Close and then click Next

5. On the Destination System page, choose the VMware Infrastructure Virtual Machine
destination type, enter the vCenter server address and credentials, then click Next
6. On the Destination Virtual Machine page, enter a name for the VM and choose the correct
vSphere Datacenter in which to place the VM, then click Next
P a g e | 31
2021.09
7. On the Destination Location page, select the ESXi host that should host the new VM, choose the
appropriate Datastore and VM hardware version, then click Next
8. On the Options page, make any updates that may be required to the VMs hardware, disk or
networking configuration, or any other options that may be required, then click Next
P a g e | 32
2021.09
9. On the Summary page, confirm all of the details of the migration and then click Finish
P a g e | 33
2021.09
The progress of the migration task can now be viewed in the tasks list
P a g e | 34
2021.09
10. Once the P2V migration task has completed, connect to the target vCenter Server and verify that
the VM copy of the source server now exists in the vCenter inventory
P a g e | 35
2021.09
11. At this point, start the VM and perform any post-migration validation checks that are required

Carbonite Migrate can be used to migrate a physical server.
5.2.1 Prerequisites
 Administrator credentials to the physical server

 Access to physical out-of-band interface/power button in case of failback
 Target VMs deployed on same network/subnet with matching OS of physical server
 Console server/workstation deployed that has network access to both physical and destination VM
 Carbonite Migrate license (One required per physical server)
5.2.2 Windows How-To
1. Create a VM with the operating system, RAM, CPUs, hard disk layout and network that matches
the physical server
2. Disable Windows Firewall on both physical and destination VM, if possible
3. Set static IP on the VM (used temporarily for data migration)
4. Once the VM is deployed, install Carbonite Migrate on each of the physical, VM and console
workstations. In this example, all three are on the same network. Starting with the
console/workstation:
P a g e | 36
2021.09
P a g e | 37
2021.09
5. For the console/management server, install the client components only
P a g e | 38
2021.09
6. Open only the ports that aren’t in use
7. Click Install
P a g e | 39
2021.09
P a g e | 40
2021.09
8. Once Carbonite is installed on the console server, open the Carbonite Replication console and
click the Add Server button
NOTE: If remote installation from the console doesn’t work, check source and
destination server firewalls. It may be necessary to completely disable them. If this isn’t
possible, install using the installer package in a way similar to the above instructions.
You’ll need to install the server components of Carbonite.
P a g e | 41
2021.09
9. Type in the physical server information. In this example, we used the computer name but you can
use an IP as well.
P a g e | 42
2021.09
10. Highlight both servers and click the Install button
11. Enter license keys as necessary assigned to the physical server. This install used all defaults under
installation options.
P a g e | 43
2021.09
12. Both servers should have been in an ‘Idle’ Activity State after installation
13. Highlight the physical server and select ‘Create a New Job’
14. Select Full Server. Check that all drives are listed and click Next
P a g e | 44
2021.09
15. Select the target VM server and click Next
P a g e | 45
2021.09
NOTE: Under the set options, typically the only adjustment made may be changing the
compression on the transfer. This has been done in slower network environments with
success but be aware it may take additional CPU utilization on the physical.
16. Click Next.
17. Verify the summary checklist.
NOTE: The most common warnings seen are about the source server having more than
one NIC and the destination not having it. This is OK and can be ignored if the additional
NICs aren’t being utilized.
18. Under the Jobs tab in the console, the status of each job is listed. The job syncs the data from the
physical to the new VM continuously, allowing for cutover at the user’s time of choosing.
19. Highlight the job and select failover.
NOTE: In the example screenshot, the job was complete and ready for failover. The
options below are default.
20. When failover occurs, the source server shuts down and the destination server reboots with the
source server IP address. Verify all data, services, applications, etc. are usable on the destination
server after cutover.
P a g e | 46
2021.09
NOTE: A new operating system license may need to be generated depending on the
source license type. Cutover time can vary but in this example it finished in
approximately 5-10 minutes.
There are now two source servers listed under the Servers tab after a successful cutover. This is
normal as the destination VM has now transformed with the same name, IP as the original
physical.
21. After you complete a full server verification, you can uninstall Carbonite from the console on the
server
P a g e | 47
2021.09
5.2.3 Linux How To
1. Create a VM with the operating system, RAM, CPUs, hard disk layout and network that matches
the physical server
2. Disable the firewall on both physical and destination virtual machine, if possible
3. Set static IP on the VM (used temporarily for data migration)
4. Once the VM is deployed, install Carbonite Migrate on each of the physical, VM and console
workstations. In our example screenshots, all three are on the same network, starting with the
console/workstation:
P a g e | 48
2021.09
P a g e | 49
2021.09
5. For the console/management server, install the client components only
P a g e | 50
2021.09
6. Open only the ports that AREN’T in use
7. Click Next to install
P a g e | 51
2021.09
P a g e | 52
2021.09
8. SCP the Carbonite RPM files to each Linux server (/tmp in the example)
9. Run the command rpm -iv DoubleTake….rpm on each server.
NOTE: if any required packages need to be installed, install them as necessary (this can
vary from OS to OS)
10. In the directory where the rpm is installed, type DTSetup
11. Select option 2
P a g e | 53
2021.09
12. Select option 1
13. Once installed on each server, open up the console machine and click ‘Add Server’
P a g e | 54
2021.09
14. Enter the required information for each server
15. The servers should now show up in the console. If they can’t to connect, verify the firewall
settings on each server or open up the necessary ports in the guide.
16. Apply a Migrate license key to the source physical server
17. Click the Create a new job button and select Migrate
P a g e | 55
2021.09
18. Under server workloads, select Full Server. Verify all filesystems required are listed on the right.
Click Next
19. Select the target server and click Next
20. Under Job options, all defaults were selected. Review as necessary and click Next.
P a g e | 56
2021.09
21. Review the Summary page. Review and click Next.

22. Under the Jobs tab in the console, the status of each job is listed. The job syncs the data from the
physical to the new VM continuously, allowing for cutover at the user’s time of choosing.
23. In the example here, the job was complete and ready for failover. Highlight the job and select
Failover. The options below are default.
P a g e | 57
2021.09
24. When failover occurs, the source server is shut down and the destination server reboots with the
source server IP address. Verify all data, services, applications, etc. are usable on the destination
server after cutover.
NOTE: A new operating system license may need to be generated depending on the
source license type. Cutover time can vary; in this example, it finished in approximately
5-10 minutes.
P a g e | 58
2021.09
25. As seen, there are now two source servers listed under the Servers tab after a successful cutover.
This is normal, as the destination VM has now transformed with the same name/IP as the original
physical.
5.2.4 Licensing Carbonite on a Server without an Internet Connection
1. After applying the license generated from the Carbonite website, dark sites may require further
activation of the Migrate license. Below is an example.
2. Click Get an activation key from our website.
3. When the browser opens, copy the URL and paste it into a browser on a system with internet
access.
P a g e | 59
2021.09
P a g e | 60
2021.09
4. From the Carbonite console, open the Manage License Inventory page and click Export Licenses
from the toolbar.
P a g e | 61
2021.09
5. Upload the exported text file to the website. Verify the information and click Submit.
The system sends a second key via email
6. When you receive the email, paste that key into the Add License key for the server.
P a g e | 62
2021.09
The server should now be fully licensed.
P a g e | 63
2021.09
A. Glossary
Term Definition
Click or tap here to enter text. Click or tap here to enter text.
 Click or tap here to enter Click or tap here to enter text.

text.
P a g e | 64
2021.09
B. Use If Needed
CONSULTANT: Delete when preparing for the customer
TABLES - SIMPLE
/NUtanix SImple Table Style
/Table Heading /Table Heading
/Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text
 /Table Bullet  /Table Bullet
o /Table Bullet 2 o /Table Bullet 2
/Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text
/Table Heading /Table Heading /Table Heading
/Table Text /Table Text /Table /Table Text /Table Text /Table
Text /Table Text Text /Table Text
/Table Text /Table Text /Table /Table Text /Table Text /Table
Text /Table Text Text /Table Text
P a g e | 65
2021.09
/Table Heading /Table Heading /Table Heading /Table Heading
/Table Text /Table /Table Text /Table /Table Text /Table /Table Text /Table
Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table
Text Text Text Text
 /Table Bullet  /Table Bullet  /Table Bullet  /Table Bullet
/Table Bullet 2 /Table Bullet 2 /Table Bullet 2 /Table Bullet 2
Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table
Text Text Text Text
o /Table Bullet 2 o /Table Bullet 2 o /Table Bullet 2 o /Table Bullet 2
/Table Heading /Table Heading /Table Heading /Table Heading /Table Heading
/Table Text /Table /Table Text /Table /Table Text /Table /Table Text /Table /Table Text /Table
Text /Table Text /Table Text /Table Text /Table Text /Table
Text /Table Text Text /Table Text Text /Table Text Text /Table Text Text /Table Text
 /Table Bullet  /Table Bullet  /Table Bullet  /Table Bullet  /Table Bullet
o /Table o /Table o /Table o /Table o /Table
Bullet 2 Bullet 2 Bullet 2 Bullet 2 Bullet 2
/Table Text /Table /Table Text /Table /Table Text /Table /Table Text /Table /Table Text /Table
Text /Table Text /Table Text /Table Text /Table Text /Table
Text /Table Text Text /Table Text Text /Table Text Text /Table Text Text /Table Text
/Table /Table /Table /Table /Table /Table

Heading Heading Heading Heading Heading Heading
/Table Text /Table Text /Table Text /Table Text /Table Text /Table Text
 /Table  /Table  /Table  /Table  /Table  /Table
Bullet Bullet Bullet Bullet Bullet Bullet
P a g e | 66
2021.09
/Nutanix Complex Table Style
/Table Heading Complex /Table Heading Complex /Table Heading Complex

In-Table Header (/Table Heading + White Fill)
/Table Text /Table Text /Table /Table Text /Table Text /Table /Table Text /Table Text
Text /Table Text Text /Table Text /Table Text /Table Text
 /Table Bullet  /Table Bullet  /Table Bullet
o /Table Bullet 2 o /Table Bullet 2 /Table Bullet 2
/Table Text /Table Text /Table /Table Text /Table Text /Table /Table Text /Table Text
Text /Table Text Text /Table Text /Table Text /Table Text
 /Table Bullet  /Table Bullet  /Table Bullet
o /Table Bullet 2 o /Table Bullet 2 /Table Bullet 2

Complex Complex Complex Complex
Text /Table Text Text /Table Text Text /Table Text Text /Table Text
/Table Text /Table Text /Table Text /Table Text
o /Table Bullet 2 o /Table Bullet 2 o /Table Bullet 2 o /Table Bullet 2
P a g e | 67
2021.09

Complex Complex Complex Complex
In-Table Header (/Table Complex Heading + White Fill)
Complex Complex Complex Complex Complex
/Table Text /Table Text /Table Text /Table Text /Table Text
P a g e | 68
2021.09
Complex Complex Complex Complex Complex

Heading Heading Heading Heading Heading Heading
Complex Complex Complex Complex Complex Complex
Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table
Text Text Text Text Text Text

P a g e | 69
2021.09
LINK ICONS
Confluence
Excel
Github
Google Drive
Intranet
JIRA
LucidChart
Outlook
PDF
PowerPoint
SharePoint
Slack
VIdeo
Visio
Weblink
Word
TEMPLATE SHORTCUT KEYS
Style Applied Shortcut Key To the Paragraph or

Character Selected?
/Bulleted Text - USE THIS Style ALT +B P
/Bulleted Text 2 Styles ALT +2 P
/Bulleted Text 3 Style ALT +3 P
P a g e | 70
2021.09
Style Applied Shortcut Key To the Paragraph or

Character Selected?
/Button Names Style ALT +9 C
/Code Small Style (full lines of text) ALT +O P
/Code Style (In-line text) ALT +C C
/Document Text - USE THIS Alt+ CTRL +B P
/Graphics & Pix ALT +G P
/Heading 1 - USE THIS Style CTRL+ ! P
/Heading 2 - USE THIS Style CTRL + @ P
/Heading 3 - USE THIS Style CTRL + # P
/Heading 4 - USE THIS Style CTRL + $ P
/Hyperlink Character Style ALT +Y C
/Numbered List Style ALT +N P
/Table Heading ALT +H P
/Table Text - USE THIS Style ALT +T P
/Table Bullet 1 Style ALT +U P
/Window Name Style ALT +W C
P a g e | 71

Workload Migration - Deployment and Operations Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Workload Migration - Deployment and Operations Guide

Uploaded by

Copyright:

Available Formats

LAST UPDATED: 2022.

SDK – WORKLOAD MIGRATION

Deployment & Operations

Prepared for: <<Client POC>>

Prepared by: <<Enter Consultant Name Here>>

Organization: <<Enter Customer Name Here>>

Document Reference: Workload Migration: Deployment &

Content Last Updated: 2021.09

© Copyright 2021 Nutanix, Inc.

2 MIGRATION TOOLS DEPLOYMENT................................................................7

3 MIGRATION USE CASE MATRIX......................................................................8

4 VIRTUAL TO VIRTUAL (V2) MIGRATION TO NUTANIX SCENARIOS...........9

4.2 VMware Shared-Nothing vMotion.........................................................................................15

4.3 Hyper-V Shared-Nothing Live Migration..............................................................................17

4.4 System Center VM Manager Live Migration.........................................................................25

4.4.1 Live Migration with No Shared Infrastructure........................................................................................25

5 PHYSICAL TO VIRTUAL (P2V) MIGRATION TO NUTANIX SCENARIOS 30

5.2 Carbonite Migrate..................................................................................................................36

1Executive Summary – Migration to

1.2 VMWARE SHARED-NOTHING VMOTION

NOTE: Migration using storage vMotion requires VM downtime.

1.3 MICROSOFT SHARED-NOTHING LIVE MIGRATION

1.4 VMWARE CONVERTER

1.5 CARBONITE MIGRATE

2Migration Tools Deployment

 Nutanix Move 4.1 User Guide - Move Deployment

2.2 VMWARE CONVERTER

 Installing and Uninstalling Converter Standalone

2.3 CARBONITE MIGRATE

 Carbonite Migrate Installation Guide

 Carbonite Migrate Windows User's Guide

3Migration Use Case Matrix

Source/Target Nutanix Nutanix Nutanix Nutanix AWS AWS EC2

Legacy ESXi YES YES NO YES NO

Nutanix ESXi YES YES NO YES YES

Legacy Hyper-V YES YES YES YES NO

Nutanix AWS YES YES NO NO NO

AWS EC2 YES YES NO YES N/A

Azure YES YES NO NO NO

Nutanix AHV NO YES NO NO YES

Physical Server YES YES YES YES NO

4Virtual to Virtual (V2) Migration to

 ESXi to Nutanix Clusters on AWS and AHV VM Migration

 ESXi to ESXi VM Migration

 Hyper-V to Nutanix Clusters on AWS and AHV VM Migration

 AWS to Nutanix Clusters on AWS and AHV VM Migration

 AWS to ESXi VM Migration

 AHV to AWS VM Migration

 Azure to AHV VM Migration

 Azure to ESXi VM Migration

4.1.1 General Prerequisites

4.1.2 General Limitations

4.1.3 General Migration Steps

1. From the Move home screen, click Create a Migration Plan

6. On the VM Preparation page, select either Automatic or Manual preparation, provide

11. On the confirmation dialog box, click Continue

13. The migrated VM is now visible in Prism:

14. At this time, perform any post-migration validations required.

4.2 VMWARE SHARED-NOTHING VMOTION

VMware Shared-Nothing vMotion

4.2.3 How To: Shared-Nothing vMotion

2. Choose target datastore (Nutanix container)

4.3 HYPER-V SHARED-NOTHING LIVE MIGRATION

Windows Server 2012 TO/FROM Windows Server 2012