Workload Migration - Design Guide

LAST UPDATED: 2022.
12
SDK – WORKLOAD MIGRATION
Design Guide
Workload Migration: Design 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: Design 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 INTRODUCTION...................................................................................................5
1.1 Document Purpose...................................................................................................................5
1.2 Audience..................................................................................................................................5
1.3 Software Versions....................................................................................................................6
2 REQUIREMENTS, CONSTRAINTS, ASSUMPTIONS & RISKS.......................7

2.2 Constraints...............................................................................................................................8
2.3 Assumptions.............................................................................................................................8
2.4 Risks........................................................................................................................................9
3 CURRENT STATE ASSESSMENT.....................................................................11

3.1 Legacy infrastructure..............................................................................................................11
3.1.1 Logical design.........................................................................................................................................11
3.1.2 Physical Design – Virtual Infrastructure.................................................................................................11
3.1.3 Physical Design – Storage System..........................................................................................................12
3.2 Current State VM inventory...................................................................................................12

3.3 Current State Target infrastructure.........................................................................................12
4 MIGRATION DESIGN........................................................................................15
4.1 Design decisions.....................................................................................................................15
4.2 Migration methodology..........................................................................................................15
4.3 Nutanix Move details.............................................................................................................20
5 TARGET ENVIRONMENT STATE....................................................................21

5.1 Logical Cluster Design...........................................................................................................21
5.1.1 Failure Domains......................................................................................................................................21
5.2 Logical Cluster Features.........................................................................................................23

5.2.1 Workload Resource Balancing & VM Affinity......................................................................................23
5.2.2 Workload High Availability & Admission Control................................................................................23
P a g e |4
2021.09
5.2.3 Workload Live Migration & Enhanced vMotion Support......................................................................23
5.3 Platform Selection & Datacenter Infrastructure.....................................................................24

5.3.1 Physical Hardware Specifications...........................................................................................................24
5.3.2 Rack Layout............................................................................................................................................25
5.4 Resource Sizing......................................................................................................................26

5.4.1 Nutanix Cluster Sizing............................................................................................................................26
5.4.2 Nutanix CVM Sizing...............................................................................................................................26
5.4.3 Resource Sizing Design Decisions..........................................................................................................27
A. GLOSSARY..........................................................................................................28
B. USE IF NEEDED..................................................................................................29
P a g e |5
2021.09
1Introduction
<<Enter Customer Name Here>> is migrating workloads from legacy infrastructure to the Nutanix
platform.
<<Enter Customer Name Here>> desires to gain the financial, business and operational benefits of a
hyperconverged infrastructure, and have engaged Nutanix Services to develop, plan and perform
migration to a new solution. The future state Virtual Infrastructure to support both of its existing and
future workloads using VMware vSphere as the hypervisor and Nutanix solution for software-defined
storage and data protection, including disaster recovery in both on-premises and to a disaster recovery
site. The goal is to enable the establishment of a highly available and efficient next-generation
infrastructure based on Nutanix and vSphere recommended practices.
1.1 DOCUMENT PURPOSE

The purpose of this document is to provide <<Enter Customer Name Here>> staff with a migration
design blueprint for their new Hyper-Converged infrastructure (HCI) platform based on Nutanix. The
document addresses conceptual, logica, and physical design elements with design decisions
throughout the document to justify each infrastructure design choice.
1.2 AUDIENCE
This document is intended for those planning, designing, and/or implementing the components of a
Nutanix Hyperconverged infrastructure. The audience includes, but not limited to:
 Project Sponsor
 Virtualization Architects
 Project Managers
 Business Decision Makers
 Technical teams (Server, Networking, Security, Backup/Recovery)
P a g e |6
2021.09
1.3 SOFTWARE VERSIONS

The following software versions are used throughout the design and are valid as of the publication
date prior to implementation.
Component Version Install Options/ Version/ License
Nutanix AOS AOS 5.15.2 Ultimate
Prism Central pc.2020.8 Prism Pro
VMware ESXi ESXi 6.5.0.33000 – Build Enterprise Plus

13932383
VMware vCenter VMware vCenter 6.5 - 16613358 vCenter Server Standard – vCenter
Appliance
Nutanix Move 4.1 N/A
P a g e |7
2021.09
2Requirements, Constraints,
Assumptions & Risks
During the design workshops with <<Enter Customer Name Here>>, both business and technical
requirements were gathered and referenced to begin the first steps to creating a high-level migration
plan to the new solution.
<<Enter Customer Name Here>> specific requirements, constraints, assumptions, and risks are
contained in the tables below.
BUSINESS & TECHNICAL REQUIREMENTS

Business requirements have been sorted into different conceptual and logical design elements as
follows:
 Recoverability – How to roll back from field migration
 Availability – How the migration platform handles resiliency to meet business SLA’s
 Performance – How performant the migration platform is in meeting workload requirements
 Security – How the migration platform\methodology is secured and meets compliance (if any).
Where design decisions are called out in the design, a reference to the associated requirements is
made where applicable.
ID Area Requirement Trace
B101 Recoverability Migration methodology and tools must provide an

efficient rollback process
B102 Availability Migration methodology and tools should minimize

application or virtual machine downtime
B103 Manageability Migration tool should support automation using

RestAPI
B104 Performance Migration methodology and tools should provide

maximum performance to meet the migration project
P a g e |8
2021.09
ID Area Requirement Trace
timeline
B105 Security Migration console should support authentication to

limit unauthorized access
2.1 CONSTRAINTS
Constraints limit the logical design decisions and physical specifications for the design. During
requirement gathering workshops, specific constraints were identified.
Where design decisions are noted in the design, a reference to the associated constraint is made where
applicable.
ID Description Trace
C101 Hardware choice is pre-determined and already purchased
C102 Nutanix clusters are already build
C102 VMware ESXi\Nutanix AHV is the chosen hypervisor
C103 Networking speed is <100 Mbps
C105 Maximum of 25 VMs are supported per migration plan in Nutanix Move
C106 Legacy storage system is running out of capacity
2.2 ASSUMPTIONS
Assumptions are expectations about the implementation and use of a system that cannot be confirmed
during the design phase, and which are used to provide guidance within the design. If assumptions
aren’t met, the respective design areas are at risk. All assumptions must be accepted and signed off
by key stakeholders before the design document is accepted.
Description Assumption
Accepted
A101 Operations staff or application owners have the required technical ☐

knowledge to test and troubleshoot application
A102 Customer support team or application owners develop and provide a UAT ☐
checklist
A103 It is assumed that dependent infrastructure is fully functional. Dependent ☐
P a g e |9
2021.09
Description Assumption
Accepted
infrastructure includes:
 Active Directory
 DNS
 NTP
 SMTP
 Backup Software
 DHCP
 Firewalls
 Switches and Routing
A104 Target infrastructure is ready for new workloads ☐
A105 Target solution has enough resources (CPU/RAM/Storage) to accommodate ☐

migrated workloads
A106 Customer provides up to data virtual machine and application inventory ☐
A107 Customer provides up to date application dependency mapping ☐
A108 Customer is responsible for application UAT after migration ☐
2.3 RISKS
During design workshops, certain risks were identified. The risk, associated impact and mitigation
assessment are described in the table below along with traceability in associated design decisions.
ID Risk Description Impact Mitigation Trace
R101 Project timeline Running an unsupported Extend support

configuration
R102 Low bandwidth link Exceeding project Upgrade link between

between source and timeline data centers to meet
Nutanix project timeline
R103 Some of the virtual Running applications an Upgrade Guest OS before

machines running unsupported configuration migration or migrate VM
unsupported Guest OS manually
versions by the
hypervisor
P a g e | 10
2021.09
ID Risk Description Impact Mitigation Trace
R104 Some of the applications Extends project timeline Deploy virtual appliance
are running on virtual on Nutanix
appliances
P a g e | 11
2021.09
3Current State Assessment

To ensure all requirements can be met in the design, the current state was documented. This includes
a high-level design of existing infrastructure, networking infrastructure and VMs in scope for
migration.
3.1 LEGACY INFRASTRUCTURE
3.1.1 Logical design
The following figure shows the logical design of the existing clusters to be migrated to the Nutanix
Hyperconverged platform
<insert diagram or table here>
The key attributes of the current state are as follows:
 Primary Data Center exists in Effington, Secondary & DR reside in Reston and a VDI cluster
(consolidated to Effington)
 Clusters are currently running ESXi on Nutanix at a time of a hardware refresh.
 Three clusters currently exist, consolidating into two
 Two separate vCenter servers are deployed with internal Platform Service Controllers, not in linked
mode
 Currently on vCenter 6.5 and ESXi 6.5, the project to upgrade to 6.7 to occur during or after the
hardware refresh. If during, define the timeline. Add to assumptions/constraints…
 Networking bandwidth between datacenters <insert value here>
3.1.2 Physical Design – Virtual Infrastructure
Provide information about physical components from legacy infrastructure.
P a g e | 12
2021.09
vCenter name
Cluster name
Data volume
Networking
Storage FC
# Vms
speed
speed
ID
3.1.3 Physical Design – Storage System
Provide information about legacy storage subsystem
Storage FC\iSCSI\
Storage capacity
Storage name
Peak latency
Peak IOPS
NFS speed
Free space
ID
3.2 CURRENT STATE VM INVENTORY

The following table provides summary information about VMs number, data volume and location for
workloads in-scope for the migration project
ID Guest OS version # systems Data volume Location
1 Windows 2012R2 100 50TB DC1, AWS region 1
3.3 CURRENT STATE TARGET INFRASTRUCTURE

Sizing data was gathered and analyzed by the SE and has been provided with the suggested hardware
configuration. <<Enter Customer Name Here>>,has already purchased the new hardware for their
infrastructure. data reduction expected not required
P a g e | 13
2021.09
Usable Capacity, Production Cluster
Usable Capacity, DR Cluster
P a g e | 14
2021.09
4Migration Design
4.1 DESIGN DECISIONS
Associated Risks
Design Decision
Requirements
Justification
Constraints
Associated
Associated
Design
ID
DD01 Use Nutanix Nutanix Move is free software

Move for to support Migration to AHV
migration
DD02 Use multiple To speed up the migration

Nutanix Move project timeline multiple
Nutanix Move will be
deployed.
DD03 Use bandwidth Due to limited bandwidth

throttling between datacenter bandwidth
throttling will be used
DD04 vSphere Shared- To migrate from legacy ESXi

Nothing to Nutanix with ESXi Shared-
migration will Nothing migration is the easiest
be used and quickest way to migrate
DD05 Set EVC Leveraging Shared-Nothing

baseline to migration across two vSphere
clusters requires
4.2 MIGRATION METHODOLOGY

CONSULTANT: Define and provide detailed information about migration methodology
The below figures show the high-level architecture for the migration project.
P a g e | 15
2021.09
CONSULTANT: Editable diagrams are available in the migration kit
Logical design AWS to Nutanix AHV migration
P a g e | 16
2021.09
Migration from AWS to Nutanix Clusters
Migration from VMware to Nutanix AHV
P a g e | 17
2021.09
Hyper-V migration to Nutanix AHV
Migration from Hyper-V to Nutanix with Hyper-V
P a g e | 18
2021.09
Migration from legacy ESXi to Nutanix ESXi
Migration from Azure to Nutanix AHV
P a g e | 19
2021.09
Migration from Azure to Nutanix ESXi
4.3 NUTANIX MOVE DETAILS

The table below provides information about Nutanix Move configuration
Source environment Nutanix Move Target environment

Name IP address Hostname IP address Name IP address
vCenter name Nutanix
cluster name
Hyper-V Nutanix
hostname cluster name
P a g e | 20
2021.09
5Target Environment state

5.1 LOGICAL CLUSTER DESIGN
The following figure shows the logical cluster design of the future environment
Each Hyperconverged cluster is represented as follows
 Blue – Nutanix Clusters

 Green – Virtualization Clusters
 White – Storage Containers
Logical Cluster Design
5.1.1 Failure Domains
The enterprise architecture design for <<Enter Customer Name Here>>, appropriately subscribes to
the concepts of failure domains. If a technological domain is to fail, it should ideally minimize the
impact to other dependent technological domains. In this design, the following domains are
considered failure domains that can impact the normal operations to deliver IT services,
P a g e | 21
2021.09
Domain Description Failure Mitigation
Datacenter There are two disparate datacentres, Workloads are mainly run in ESO with few
ESO and Reston which are in Reston. ESO workloads are replicated to
geographically separated. each other in case of a site failure.
Each Site has an Arista-based network Every component has local redundancy to
with no common points of failure. The mitigate against failure. However, if a logical
networking team plans to adopt the failure is to occur, it may vary from rack
Leaf-Spine architecture, where each local to sitewide.
Rack hosts a pair of Top-of-Rack leaf Localized rack failure can then rely on
switches. alternatives in having availability across
racks.
Site local failure will have to rely on the
alternate site.
Rack Each rack in a DC has a dedicated pair As each rack has redundant PDUs, the loss of
of redundant power distribution unit one power source should not impact devices
(PDU) that are properly connected to both sources.
In an extreme case where a rack loses both
sources of power, we can consider a failover
of services to the other site.
Nutanix clusters are designed to Each cluster has compute and storage
withstand a single failure, and with the capacity reservations to ensure self-heal can
ability to self-heal before replacement take place.
repair as long as sufficient capacity is Further resiliency can be considered to
available in the cluster upgrade a cluster to RF3, to tolerate double
concurrent failures. However, this will have a
negative effect of losing more capacity due
to three copies of data stored instead of two
In an extreme case, if a cluster-wide failure
occurs, services can fail over to another site.
Nutanix Is not a relevant failure domain. Failure of Prism Central does not impact
Prism normal cluster operation, as clusters can be
Central individually managed via prism element
VMware Is not a relevant failure domain In the event of a vCenter failure, Virtual
vCenter machines continue to remain operational.
Individual virtual machines can be operated
by connecting directly to the ESXi host or
P a g e | 22
2021.09
Domain Description Failure Mitigation
simple power on/off operations can also be

accomplished via Nutanix Prism
5.2 LOGICAL CLUSTER FEATURES
5.2.1 Workload Resource Balancing & VM Affinity
Each ESXi hypervisor uses a built-in mechanism to control workload balancing. This ensures that
VMs move to other hosts in the case of cluster contention. Depending on the hypervisor choice, both
memory/CPU and storage metrics can be used to determine initial and ongoing VM placement in the
cluster. To ensure resources are sufficient to allow cluster maintenance and host failure, the new
cluster is sized for N+1. If VMs require affinity or anti-affinity rules to a specific host, or group of
hosts, each Hypervisor provides functionality for this purpose.
5.2.2 Workload High Availability & Admission Control
Each respective Hypervisor provides a mechanism to ensure workloads restart in the event of a host
failure. he hosts are monitored for both hardware and network failures; in the event of failure, VMs
restart on surviving hosts.
5.2.3 Workload Live Migration & Enhanced vMotion Support
Each Hypervisor also provides a mechanism to move workloads between hypervisor hosts. This can
be used to manually move workloads between hosts, online, in the case of maintenance or other
operational tasks. Depending on hypervisor choice, a dedicated network can be configured for live
migration. To ensure VMs can be migrated to hosts with different CPU versions, enhanced vMotion
support (EVC) at the latest current CPU generation can be enabled on each cluster. The method to do
this on each host is described in the cluster physical design
P a g e | 23
2021.09
5.3 PLATFORM SELECTION & DATACENTER INFRASTRUCTURE
5.3.1 Physical Hardware Specifications
<<Enter Customer Name Here>>, has selected the Nutanix NX-8035-G7 as the basis of its
virtualization platform. The following naming is used for the NX-8035 platform according to the
number of nodes per block
 NX-8035 (Single Node)

The NX-8035 consists of a 2RU form factor as per the below diagram.
NX-8035-G7 Front Hardware
Each NX-8035-G7 Node is configured with 2x 2P 10GbE Cards with RJ45 connectivity. There are
also additional x2 Onboard 10GbE ports and a dedicated 100/1000 IPMI Port.
NX-8035-G7 Rear Hardware Diagram
Each host is configured with the following specifications as per the below table.
Attribute Specification 1 (ESO & Specification 2 (2 nodes for all

Reston) Flash at ESO)
Platform Name NX-8065-G7 NX-8065-G7
Processor Type Intel 6226R 2.9GHZ Intel 6226R 2.9GHZ
Number of Sockets 2 2
Number of Cores per Socket 16 16
P a g e | 24
2021.09
Attribute Specification 1 (ESO & Specification 2 (2 nodes for all

Reston) Flash at ESO)
Total Cores per Node 32 32
Per Node Memory 1024 1024
Installed DIMM Size and Type 16x64GB 16x64GB
SSD Count 2x3.84TB 6x7.68TB
HDD Count and Capacity 4x12TB
RAW Capacity per Node 52.768TB 46.08TB
Usable Capacity per Node (RF2) 26.384TB 23.04TB
External Network Interface cards 1x 10Gbe Dual SFP 1x 10Gbe Dual SFP
Onboard Network Interface 1x Dedicated IPMI 1x Dedicated IPMI

Cards
5.3.2 Rack Layout
All the nodes for <<Enter Customer Name Here>> are installed in two racks at the ESO datacenter
and one rack at the Reston datacenter. To support the power requirements and ensure power
redundancy for Nutanix Blocks, two PDUs have been installed per rack and Nutanix blocks are to be
distributed across all PDUs. For redundancy, power supply A goes to the left PDUs and Power
Supply B to the right PDUs.
5.4 RESOURCE SIZING

To accommodate all the sizing of the applications identified in the current state assessment, the
following sizing calculations were used for <<Enter Customer Name Here>> Nutanix clusters. Since
the cluster are configured as RF2, sizing is done at N+1, with a 30% estimation for data reduction.
Sizing was done to accommodate a site failover. Hyperthreads were not considered for the vCPU to
pCPU ratio.
Each CVM used for the Nutanix platform is sized for 12 vCPUs and 32GB of RAM. This is the
recommended configuration for the applications to be migrated. Although more memory can help
with read I/O from the unified cache, due to the memory constraints of each node (512GB), 32GB of
memory provides a good balance to provide enough memory for running VMs. The vCPU and
memory overhead for the CVM is sized the same as any other VM.
P a g e | 25
2021.09
5.4.1 Nutanix Cluster Sizing
To accommodate for failure, capacity equal to a single node is reserved in the cluster. The following
table illustrates the cluster sizing used with N+1 considered.
Nutanix Cluster
Sum of Physical
Sum of Physical
Capacity (RF2)
Capacity (RF2)
Total Reserved
Total Capacity
Memory (GB)
Total Usable
Node Count
(RF2)
Cores
ESO 15 320 15360 293.75
Reston 5 160 5120 85.82
5.4.2 Nutanix CVM Sizing
To accommodate for CVM overhead, the following CVM sizing calculations were used in the cluster.
Nutanix Cluster Per CVM CVM Sizing Cluster CVM Cluster CVM
Sizing vCPU vRAM Overhead vCPU Overhead vRAM
ESO 12 32 120 320
ESONXESXC01 12 32 60 160
5.4.3 Resource Sizing Design Decisions
The following design decisions were made for resource sizing.

Associated Risks
Design Decision
Requirements
Justification
Constraints
Associated
Associated
Design
ID
DD09 Space Savings assumption of Nutanix has typically seen B101, C101, R101,
30% will be made for all space savings of at least 50% B102, C102 R102
clusters with compression enabled, so
30% is a conservative
estimate.
P a g e | 26
2021.09
Associated Risks
Design Decision
Requirements
Justification
Constraints
Associated
Associated
Design
ID
DD11 CVM's will be sized with Sizing CVM's up to the B101, C101, R101,
32GB of Memory, 12 vCPU maximum vCPU size B102, C102 R102
supported by the underlying
NUMA node will ensure
maximum performance is
available for running virtual
machines which require high
I/O. 12 vCPU also helps
decrease rebuild time during
a node failure. 32GB RAM
is recommended for the
applications which are to run
on the Nutanix Platform.
P a g e | 27
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 | 28
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 | 29
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 Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table
/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 Text /Table Text /Table Text /Table Text /Table Text /Table Text /Table
/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 Text /Table /Table Text /Table /Table Text /Table /Table Text /Table
/Table Text Text /Table Text /Table Text /Table Text /Table
/Table Text Text /Table Text Text /Table Text Text /Table Text Text /Table 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 Text /Table /Table Text /Table /Table Text /Table /Table Text /Table
/Table Text Text /Table Text /Table Text /Table Text /Table
/Table Text Text /Table Text Text /Table Text Text /Table Text Text /Table 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 /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
P a g e | 30
2021.09
Bullet Bullet Bullet Bullet Bullet Bullet
/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
P a g e | 31
2021.09

Complex Complex Complex Complex
o /Table Bullet 2 o /Table Bullet 2 o /Table Bullet 2 o /Table Bullet 2

In-Table Header (/Table Complex Heading + White Fill)
Complex Complex Complex Complex Complex
/Table Text /Table Text /Table Text /Table 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
P a g e | 32
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 | 33
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
/Button Names Style ALT +9 C
P a g e | 34
2021.09
Style Applied Shortcut Key To the Paragraph or

Character Selected?
/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 | 35

Workload Migration - Design 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 - Design Guide

Uploaded by

Copyright:

Available Formats

LAST UPDATED: 2022.

SDK – WORKLOAD MIGRATION

Prepared for: <<Client POC>>

Prepared by: <<Enter Consultant Name Here>>

Organization: <<Enter Customer Name Here>>

Document Reference: Workload Migration: Design Guide

Content Last Updated: 2021.09

© Copyright 2021 Nutanix, Inc.

2 REQUIREMENTS, CONSTRAINTS, ASSUMPTIONS & RISKS.......................7

3 CURRENT STATE ASSESSMENT.....................................................................11

3.2 Current State VM inventory...................................................................................................12

5 TARGET ENVIRONMENT STATE....................................................................21

5.2 Logical Cluster Features.........................................................................................................23

5.2.3 Workload Live Migration & Enhanced vMotion Support......................................................................23

5.3 Platform Selection & Datacenter Infrastructure.....................................................................24

5.4 Resource Sizing......................................................................................................................26

1.1 DOCUMENT PURPOSE

1.3 SOFTWARE VERSIONS

Component Version Install Options/ Version/ License

Nutanix AOS AOS 5.15.2 Ultimate

Prism Central pc.2020.8 Prism Pro

VMware ESXi ESXi 6.5.0.33000 – Build Enterprise Plus

Nutanix Move 4.1 N/A

BUSINESS & TECHNICAL REQUIREMENTS

ID Area Requirement Trace

B101 Recoverability Migration methodology and tools must provide an

B102 Availability Migration methodology and tools should minimize

B103 Manageability Migration tool should support automation using

B104 Performance Migration methodology and tools should provide

ID Area Requirement Trace

B105 Security Migration console should support authentication to

C101 Hardware choice is pre-determined and already purchased

C102 Nutanix clusters are already build

C102 VMware ESXi\Nutanix AHV is the chosen hypervisor

C103 Networking speed is <100 Mbps

C106 Legacy storage system is running out of capacity

A101 Operations staff or application owners have the required technical ☐

A103 It is assumed that dependent infrastructure is fully functional. Dependent ☐

A104 Target infrastructure is ready for new workloads ☐

A105 Target solution has enough resources (CPU/RAM/Storage) to accommodate ☐

A106 Customer provides up to data virtual machine and application inventory ☐

A107 Customer provides up to date application dependency mapping ☐

A108 Customer is responsible for application UAT after migration ☐

ID Risk Description Impact Mitigation Trace

R101 Project timeline Running an unsupported Extend support

R102 Low bandwidth link Exceeding project Upgrade link between

R103 Some of the virtual Running applications an Upgrade Guest OS before

ID Risk Description Impact Mitigation Trace

3Current State Assessment

3.1 LEGACY INFRASTRUCTURE

3.1.1 Logical design

<insert diagram or table here>

The key attributes of the current state are as follows:

3.1.2 Physical Design – Virtual Infrastructure

Provide information about physical components from legacy infrastructure.

3.1.3 Physical Design – Storage System

Provide information about legacy storage subsystem

3.2 CURRENT STATE VM INVENTORY

ID Guest OS version # systems Data volume Location

1 Windows 2012R2 100 50TB DC1, AWS region 1

3.3 CURRENT STATE TARGET INFRASTRUCTURE

Usable Capacity, Production Cluster

Usable Capacity, DR Cluster

DD01 Use Nutanix Nutanix Move is free software