Download MAT4SHIFT - Build Guide - Microsoft Server and Cloud Partner

MAT4SHIFT - Build Guide
Datacenter & Cloud Consolidation and Migration
i
Table of Contents
1
Overview .................................................................................................................................................. 4
2
Solution Architecture ........................................................................................................................... 5
3
MAT4Shift Requirements ................................................................................................................... 7
4
5
3.1
NetApp Storage Data System ................................................................................................................. 7
3.2
Hyper-V ........................................................................................................................................................... 7
3.3
VMware ........................................................................................................................................................... 7
3.4
MAT/Conversion Server ............................................................................................................................ 8
Supported Configurations ................................................................................................................. 9
4.1
VMware sources ........................................................................................................................................... 9
4.2
Destination Host Server ............................................................................................................................ 9
4.3
Guest operating systems supported for conversion ...................................................................... 9
4.4
Supported Configurations for Disk Conversion ............................................................................ 10
4.5
Assumptions ............................................................................................................................................... 10
4.6
Permission Requirements ...................................................................................................................... 11
Install Instructions............................................................................................................................... 12
5.1
MAT Server Configuration..................................................................................................................... 12
5.1.1
Installing .Net Framework ................................................................................................. 12
5.1.2
Installing SQL Express ........................................................................................................ 14
5.1.3
Install Data ONTAP PowerShell Toolkit version 3.3.1 ................................................. 23
5.1.4
Installing VMware PowerCLI ............................................................................................. 25
5.1.5
Configuring MAT Database .............................................................................................. 29
5.1.6
Configuring Variable.XML ................................................................................................. 32
5.2
Configuring Constrained Delegation ................................................................................................ 36
5.3
Configure the NetApp Controller ....................................................................................................... 37
5.4
Perform storage vMotion for VMs ..................................................................................................... 38
5.5
Configure Network Map relationship ............................................................................................... 38
ii
iii
1
Overview
The purpose of this document is to provide guidance on how to build the environment that
supports the On Premise Migration of Workloads from VMware to Hyper-V, using Migration
Automation Toolkit (Powered by Project Shift), also called MAT4Shift.
This document assumes familiarity with the installation and configuration of Windows Server
2012 R2 Hyper-V, VMware vSphere and PowerShell. It does not contain an exhaustive step-bystep guidance for installation or configuration of these components. This document also does
not cover the installation and Configuration of NetApp Data Storage System.
This document assumes that the discovery and assessment of customer environment has been
completed and following aspects have been identified:


Source VMware Environment
o
ESX Servers
o
vCenter Servers
Target Hyper-V Environment
o






Hyper-V Servers (Clustered or Standalone)
Virtual Machines in-Scope for conversion
VMware Tools Versions
Guest Operating Systems
Credentials to connect to Hyper-V and VMware Environment.
Credentials to connect to VMware Guest VMs
NetApp Equipment is procured and configured. Equipment must have:
o
NetApp Controller (FAS2240 or higher required)
o
Data ONTAP 8.2 or later
o
Running clustered Data ONTAP model (C-Mode)
o
The aggregates and volumes created on NetApp Storage
o
The ability to instantiate an NFS and CIFS/SMB connections
4
2
Solution Architecture
The Migration Automation Toolkit (Powered by Project Shift) or MAT4Shift is a collection
of PowerShell scripts that automate VM conversions. MAT4Shift is powered by NetApp's Project
Shift (which are PowerShell cmdlets found in NetApp's Data ONTAP PowerShell Toolkit version
3.1.1). MAT is back-ended by a SQL instance (SQL Express works). MAT4Shift can convert VMs at
incredible speeds. Most VMs can be fully converted within five mins so that even customers with
very small service windows can use the toolkit.
MAT4Shift needs the VMware VMs to be running on NetApp Storage before conversion. During
conversion process the VMDK file, stays on the NetApp controller. NetApp ONTAP PowerShell
cmdlets use NetApp FlexClone technology to create a virtual copy of the VMDK that consists of
a minimal amount of metadata (pointers to existing data blocks). The NetApp cmdlet simply
Clone the Data from the VMDK into a VHD/VHDX writing the appropriate metadata as it goes.
The resulting file is a VHD or VHDx file that takes up practically no extra space on disk.
In terms of a full conversion, the NetApp cmdlet just converts the disk format from VMware
(VMDK) to Hyper-V (VHD or VHDX). It does not actually create a new VM. For a complete
conversion, the MAT4Shift scripts collect details about the Source VM, remove VMware Tools
and creates a Hyper-V VM with new VHD(x) file. Below is the architectural representation of
MAT4Shift
5
•VMware PowerCli
•.Net Framework 4.5
•Data ONTAP PowerShell
Toolkit version 3.1 or higher
•MAT Scripts
•SQL Express
•Windows Server 2012/ R2
•Windows Server 2008 R2
Sp1
•VMware ESX 4.x or 5.x
•VCenter Server 5.1 or above
•VMware Tools
MAT/Conversion
Server
VMWare
VSphere
Hyper-V
NetApp Storage
Equipment
•NetApp Controller
(FAS2240 or higher
required)
•Data ONTAP 8.2 or later
•clustered Data ONTAP
model (C-Mode)
•NFS and CIFS/SMB
6
3
MAT4Shift Requirements
3.1
NetApp Storage Data System
A storage system running Data ONTAP has a main unit, which is the hardware device that
receives and sends data. Depending on the platform, a storage system uses storage on disk
shelves, third-party storage, or both.
The storage system consists of the following components:

The storage controller, which is the component of a storage system that runs the Data
ONTAP operating system and controls its disk subsystem.

The disk shelves, which contain disk drives and are attached to a storage system.
The NetApp Equipment must have:





NetApp Controller (FAS2240 or higher required)
Data ONTAP 8.2 or later
Running clustered Data ONTAP model (C-Mode)
The aggregates and volumes created on NetApp Storage
The ability to instantiate an NFS and CIFS/SMB connections
3.2
Hyper-V
You will need at least one Hyper-V host to accommodate the converted workloads. Right-sizing
the Hyper-V environment is something that should be done by <Partner> Services or a certified
partner before starting migrations. Generally speaking, you will need at least one Hyper-V host
for each ESX server, but this may vary depending on the level of consolidation you have
targeted.
The destination host server should be one of the following:


3.3
Hyper-V on Windows Server 2012
Hyper-V on Windows Server 2012 R2
VMware
Following are VMware Infrastructure requirements for MAT4SHIFT:
7

VMWare VMs must be running on NetApp Storage System. Storage VMotion must be
used for migration of VMDK files from Local Storage to NetApp Storage equipment
3.4
MAT/Conversion Server
MAT Server, also called Conversion Server, controls the overall migration process in terms for
inventory, scheduling, queuing and monitoring. Following is the minimum configuration for
MAT Server or Conversion Server.



4 vCPU
8 GB RAM
Application: 250 MB Disk Space
As shown in the architecture diagram, the MAT Server must have following components
installed:






Windows Server 2012 or Windows Server 2012 R2
.Net Framework 4.5
NetApp’s Data ONTAP PowerShell Toolkit version 3.1 or higher
VMWare PowerCLI 5.1 or later
SQL Server 2008+ Express Edition
MAT4Shift PowerShell Scripts
Note: You can use any SQL 2008+ instance in Customer Environment instead of Using SQL
express
Note: You can combine the MAT/Conversion Server and the destination Hyper-V Server. This
means you would install all Conversion Server Components (MAT Scripts, VMWare PowerCLI,
NetApp DataOnTap PowerShell Toolkit, etc.) on destination Hyper-V Server
8
4
Supported Configurations
Any combination of the following is supported for conversion using MAT4SHIFT:
4.1


4.2



4.3




















VMware sources
vCenter Server 3.5 (Update 2), 4.0. 4.1, 5.0, 5.1, 5.5
ESXi/ESX Server 3.5 (Update 2), 4.0. 4.1, 5.0, 5.1, 5.5
Destination Host Server
Hyper-V on Windows Server 2012
Microsoft Hyper-V Server 2012
Microsoft Hyper-V Server 2012 R2
Guest operating systems supported for conversion
Windows Server 2003 Standard Edition with Service Pack 2 (SP2) x86
Windows Server 2003 Standard Edition with SP2 x64
Windows Server 2003 Enterprise Edition with SP2 x86
Windows Server 2003 Enterprise Edition with SP2 x64
Windows Server 2003 R2 Enterprise Edition with SP2 x86
Windows Server 2003 R2 Enterprise Edition with SP2 x64
Windows Server 2003 R2 Standard Edition with SP2 x86
Windows Server 2003 R2 Standard Edition with SP2 x64
Windows Vista Enterprise x64
Windows Vista Enterprise x32
Windows 7 Enterprise x86
Windows 7 Enterprise x64
Windows 7 Professional x86
Windows 7 Professional x64
Windows 7 Ultimate x86
Windows 7 Ultimate x64
Windows 8
Windows 8 Pro
Windows 8 Enterprise
Windows Server 2008 Enterprise x86
9













4.4
Windows Server 2008 Enterprise x64
Windows Server 2008 Datacenter x86
Windows Server 2008 Datacenter x64
Windows Server 2008 R2 Standard
Windows Server 2008 R2 Enterprise x64
Windows Server 2008 R2 Datacenter x64
Windows Server 2012 Foundation
Windows Server 2012 Essentials
Windows Server 2012 Standard
Windows Server 2012 Datacenter
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Datacenter
Supported Configurations for Disk Conversion
The following VMware virtual disk types are supported for conversion:








monolithicSparse
vmfsSparse
monolithicFlat
vmfs
twoGbMaxExtentSparse
twoGbMaxExtentFlat
delta disk conversion
Stream optimized disks
Note: Software RAIDs and Dynamic Disk are NOT supported for conversion using
MAT4SHIFT
4.5
Assumptions
MAT4Sift will successfully perform VM conversions when the following conditions are met:




The virtual machine to be converted is in a running state.
The virtual machine is joined to an Active Directory domain.
VMware Tools must be installed and running on the Guest VM
The account used for conversion has read rights to the NFS and CIFS/SMB shares
10

The account used for connecting to the VMware-based virtual machine that needs to be
converted must be part of an Active Directory domain and also a local administrator on
that machine.

The Windows user account that you are using has write access to the path specified on
the destination Hyper-V host for copying the virtual hard disks.

The Hyper-V host has the required disk space available for the converted virtual hard
disks.

The following assumptions are valid after a successful conversion:
o
The destination virtual machine will be in a started or stopped state depending
on the settings chosen by the user.
o
Once the virtual disks attached to the virtual machine are converted, the source
virtual machine will be restored to a started or stopped state, depending on the
settings chosen by the user.
o
Product activation requires each instance of a Windows operating system
installation to be activated with Microsoft. Because conversion creates a second
instance of the virtual machine on Hyper-V, this instance needs to be activated.
4.6
Permission Requirements
You will need the following permissions in the customer’s environment. It is recommended to
create a domain account called MigrationAdmin with the needed rights. This account is used to
configure MAT4Shift Solution in the customer environment.

MAT Server
o

VMware
o

Local Admin rights to install and configure MAT4SHIFT Solution
Administrator Rights and Root access to the ESX Host.
Guest Operating System (workloads)
o
Administrator rights (local admin or a domain admin account, assuming domain
admins is in the local admins group).

Hyper-V Servers
o
Administrator rights to create new virtual machines
11
5
Install Instructions
The following steps must be performed on the Conversion Server. Your Conversion Server could
be same of destination Hyper-V server or it could be a dedicated machine.
5.1 MAT Server Configuration
5.1.1
Installing .Net Framework
Microsoft .Net Framework is a prerequisite for SQL Express and VMware PowerCLI
This section provides information on installation of .Net Framework on MAT Server.
1. Create a new Account in Active Directory (AD) called MigrationAdmin in Active
Directory. Make sure that it has all necessary privileges as per Section 4.5
2. Login to server as MigrationAdmin. Make sure this ID has local administrative rights on
the server. You will use this ID to install MAT4SHIFT Scripts
3. (Optional) Run Windows Update to make sure server is up to date on all security patches.
4. Open Server Manager.
5. Click on Manage and then select Add Roles and Features.
6. After clicking Next, you’ll see the Select installation type screen and select Role-based
or feature-based installation and click Next
7. Here on the Select destination server screen, choose the MAT server and click Next.
8. On the next screen, you will see the Select server roles screen. Click Next
9. On the Select features screen, you will find the option to install .NET framework in
Windows Server 2012. Check the box for .NET Framework 3.5 Features
10. Click on “Specify an alternate source path” and enter the location of SXS folder on
Windows Server 2012 media - “<CD drive>:\sources\sxs” or on network share
\\networkshare\Sources\sxs
12
13
11. Click Install to complete .Net Framework installation
5.1.2
Installing SQL Express
The MAT4SHIFT uses SQL Database to store the information about VMWare and Hyper-V
Environment. The MAT database contains information like Operating System, IP Address,
VMWare Tools version, etc. about each Virtual machine in VMware environment
Note: You can use any SQL 2008 or SQL 2012 instance in Customer Environment instead of
Using SQL express
This section provides instructions for installation of Microsoft SQL Server Express:
1. Logon to the MAT Server as MigrationAdmin account
2. Download SQL Server Express with Advanced Services from:
http://www.microsoft.com/en-us/download/details.aspx?id=1842
3. Run the Setup to start the installation
14
4. On Feature Selection Screen, select the following features
5. On the next screen, leave the instance name and instance ID as SQLExpress. Click
Next
15
6. Make sure that disk space requirements are met. Click Next
16
7. Provide appropriate credentials for Service Accounts. You may use MigrationAdmin
Account as service account or customer provided service account
17
8. Add appropriate account including MigrationAdmin Account as SQL Server
Administrator
18
9. Choose appropriate configuration from SQL Server Reporting Services
19
10. On the next screen review the configuration and click Install
20
11. Once the installation is done, make sure that all components have installed
successfully
21
12. Click next and Close to complete the install process
22
5.1.3
Install Data ONTAP PowerShell Toolkit version 3.3.1
1. Download the Data ONTAP PowerShell Toolkit version 3.3.1 (free to Data ONTAP
customers and partners). You can download the Data ONTAP PowerShell Toolkit here:
http://support.netapp.com/NOW/download/tools/powershell_toolkit
2. Run DataOnTap.msi and Click Next
23
3. Accept the License Agreement and Click Next
4. Choose appropriate Install Path and Click on Next
24
5. Click Install to Complete the Installation of Data ONTAP PowerShell Toolkit
5.1.4
Installing VMware PowerCLI
MAT4SHIFT uses VMWare PowerCLI to connect to VMware Environment. The PowerCLI
commands are used to gather inventory information and perform tasks like taking snapshot,
start or stop VMs, etc.
Use the following instructions to install VMware PowerCLI
1. Download PowerCLI binaries from:
https://developercenter.vmware.com/web/dp/sdk/55/vsphere-powercli
2. Right-click VMWare-PowerCLI-5.1.0-1011025.exe, and select “Run as
administrator”
3. You may get the following message:
25
4. Click OK to continue
5. Click Next of first two screens
26
6. Accept the Licensing agreement and Click Next
7. Choose the default configuration. You may choose to change the install path, then
Click Next
27
8. Click Install to start the Installation
9. Click Finish to finish the installation
28
5.1.5
Configuring MAT Database
This sections provides information on configuration of MAT Database
1. Logon to the MAT/Conversion Server as MigrationAdmin
2. Create a new folder called “MAT” on the root of C:\ drive on the MAT Server
3. Extract the MAT script in C:\MAT directory. It should unpack following files in C:\MAT
directory:
ConvertVM.ps1
ConvertVM-Functions.ps1
Variable.XML
Setup MAT.sql
MAT.Readme.1.6.txt
MAT_1_6_Installation_Guide (this document)
29
4. Open SQL Management Studio and Connect to .\SQLExpress Instance you installed in
previous section.
5. Rt. Click Setup MAT.sql and open with SQL Management Studio
6. Make sure that “master” database is selected in SQL Management Studio
30
7. Click Execute to execute the SQL script. The script should produce the following output:
Creating the MAT Database v1.5.0
MAT Database created.
(1 row(s) affected) Version Table created.
VMQueue Table created.
GlobalSettings Table created.
Populating GlobalSettings Table...
(1 row(s) affected)
VMConversionData_PS
Stored Procedure sp_TransferVMConversionData_PS created.
MAT Database Setup Complete.
31
NOTE: This script only needs to be run once. The script is destructive and will drop any
tables that exist and recreate them, thereby removing all conversion related data. This will
reset your environment to a clean install state
8. This script creates a new database called MAT and all tables necessary for migration.
5.1.6
Configuring Variable.XML
Variable.XML is the most important component of MAT4SHIFT. It contains environment specific
details and variables used in the migration process
NOTE: Take great care when editing the XML file that you do not alter the XML formatting.
Ideally use an XML editor.
5.1.6.1
General
1. Set the value Logpath to the location where conversion logs would be created. Default Value
is C:\MAT.
32
2. Set the value Datasource to the name of the SQL Server (MAT server) or the name of the
<Servername>\<InstanceName, if you are using names instances. For EG: if you are using
SQLExpress instance, Datasource should be: <MAT Server Name>\SQLExpress
3. Set the MigrateNICs value to either 1 or 0.
a. 1 = Migrate NICs to Hyper-V, If you help this option, you must set sPower = 0.
b. 0 = do not migrate nics.
4. If you wish to alter the behavior of the actions Show-Status or Show-StatusLoop you can
change the value of Showrows. This value limits how many rows are returned by these two
actions.
<General>
<Variable Name="XMLVersion" Value="1.5.0" />
<Variable Name="Logpath" Value="C:\Users\(username)\AppData\Local\Temp\" />
<Variable Name="Datasource" Value="SERVER1"/>
<Variable Name="MigrateNICs" Value="1"/>
<Variable Name="Showrows " Value="30"/>
</General>
5.1.6.2 GuestCreds
1. Set the value WinAccount to an account that has the rights to execute tasks on Guest
Operating System as an admin. Preferably use the local Admin Account for the machine.
2. Set the value WinPassword to the password of the account used in WinAccount.
3. Set the value WinDomain to the domain for the account used in WinAccount. If you
have specified local admin account use “.”
<GuestCreds>
<Variable Name="WinAccount" Value="administrator" />
<Variable Name="WinPassword" Value="passsword" />
<Variable Name="WinDomain" Value="contoso" />
</SchedCreds>
5.1.6.3 NetApp
1. Set the value NTAP to the FQDN or IP of the NetApp controller.
2. Set the value NTAPUser to the username with access to the NetApp Controller.
3. Set the value NTAPPassword to the password used by NTAPUser.
4. Set the value vServerName to the name of the Storage Virtual Name (SVM) to be used
for the transition. This is the name you would use to access Netapp Storage through
SMB or NFS.
5. Set the value aggrName to the name of the Aggregate where the data will be stored.
This aggregate should already exist on the NetApp Controller. This is Case-Sensitive
6. Set the value volume to the name of the volume to be created in the aggregate. The
Volume should already exist on the NetApp Controller. This is Case-Sensitive
33
7. Set the value CifsShare to the name of the SMB share where Hyper-V VHDs would be
stored
8. Set the value EsxMountPoint to the name of the ESX mount point. This will also be used
to create the NFS data Store on ESX Server. All Source VMS must exist on this Datastore
before conversion.
9. Set the value CIFSIP to the IP address of the Cifs Data LIF.
Note: If CIfs and NFS have the same IP then a single joint interface will be created.
10. Set the value CIFSNetMask to the network mask of the CIFS Data LIF.
11. Set the value CIFSPort to the physical port where CIFS Data LIF should be bound. Use
the NetApp PowerShell Cmdlet Get-NCNetPort to get the port information from
NetApp controller
12. Set the value NFSNetMask to the network mask of the NFS Data LIF.
13. Set the value NFSPort to the physical port where NFD Data LIF should be bound.
14. Set the value DNSDomains to the DNS domains the SVM should search. The first FQDN
should be the domain to which the SVM belongs.
15. Set the value DNSNameServers to the IP address of the first DNS Name Server.
16. Set the value CifsServerName to the NetBIOS name of the SVM in the active directory.
17. Set the value Domain to the FQDN of the domain.
18. Set the value DomainAdmin to the AD user with permissions to add an object in active
directory
19. Set the value DomainAdminPassword to the password of the user in DomainAdmin.
20. Set the value DyMac to either 1 or 0. The value controls the whether or not Hyper-V
dynamically assigns a MAC address or if it uses the one assigned by VMware.
a. 1 = Use a dynamic address
b. 0 = use the VMware MAC address (This setting only applies if MigrateNICs = 1)
<NetApp>
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
<Variable
Name="NTAP" Value="192.168.1.120" />
Name="NTAPUser" Value="admin" />
Name="NTAPPassword" Value="password" />
Name="vServerName" Value="Shift" />
Name="aggrName" Value="aggr1_n1" />
Name="volume" Value="vmdata" />
Name="CifsShare" Value="DS2" />
Name="EsxMountPoint" Value="DS1" />
Name="CIFSIP" Value="192.168.1.119" />
Name="CIFSNetMask" Value="255.255.255.0" />
Name="CIFSPort" Value="e0a" />
Name="NFSIP" Value="192.168.1.118" />
Name="NFSNetMask" Value="255.255.255.0" />
Name="NFSPort" Value="e0a" />
Name="DNSDomains" Value='contoso.lab' />
Name="DNSNameServers" Value="192.168.1.1" />
Name="CifsServerName" Value="Shift" />
Name="Domain" Value="contoso.lab" />
Name="DomainAdmin" Value="" />
Name="DomainAdminPassword" Value='password' />
34
</NetApp>
5.1.6.4 HyperV
1. Set the value thost to name of the Hyper-V server which will accept and host (at least
Temporarily) the converted VMs.
2. Set the value esxPower to either 1 or 0. The value controls the final power state of the
Source VM.
a. 1 = on
b. 0 = off
3. Set the value hvPower to either 1 or 0. The value controls the final power state of the
Target VM.
a. 1 = on
b. 0 = off
4. Set the value DyMac to either 1 or 0. The value controls whether or not Hyper-V
dynamically assigns a MAC address or if it uses the one assigned by VMware.
a. 1 = Use a dynamic address,
b. 0 = use the VMware MAC address (This setting only applies if MigrateNICs = 1)
<HyperV>
<Variable
<Variable
<Variable
<Variable
</HyperV>
Name="thost" Value="SERVER1" />
Name="esxPower" Value="1" />
Name="hvPower" Value="0" />
Name="DynMac" Value="0" />
5.1.6.5 VMware
1. Set the value sHost to the FQDN or IP address of your VMware source host (ESX or
vSphere)
2. Set the value sDataCenter to vCenter Datacenter, set to * if targeting a single ESX host is
used.
3. Set the value shusername to an account that has admin rights to the source host.
4. Set the value shpwd to the password of the shusername account.
5. Set the value gUser to an account that has admin rights to the Guest VM. This account is
used to remove VMware Tools. This can be a domain or local account.
6. Set the value gPwd to the password of the gUser account
<VMware>
<Variable
<Variable
<Variable
<Variable
<Variable
Name="shost" Value="10.10.10.1" />
Name="shusername" Value="contoso\administrator" />
Name="shpwd" Value="passsword" />
Name="gUser" Value="contoso\administrator" />
Name="gPwd" Value="passsword" />
35
</VMware>
5.2
Configuring Constrained Delegation
If your conversion server is NOT same as destination Hyper-V server, you need to configure the
constrained delegation in Active Directory
1. Using Active Directory Users and Computers, Open the properties for Hyper-V server
object
2. Select Delegation Pane
3. Select “Trust this computer for delegation to specified services only”. Leave the “Use
Kerberos only” radio button selected
4. Click Add
5. In the Add Services dialog box, click the “Users and Computers” button
6. Enter the CIFSServerName and click OK
7. Highlight CIFS and click OK
8. Click OK and close the computer object properties dialog
36
5.3
Configure the NetApp Controller
You must carefully double-check your settings in the Variables.xml file before starting the
configuration of NetApp Controller
1. Logon to MAT Server as migrationadmin.
2. From a PowerShell prompt run .\ConvertVM.ps1 –SetONTAP
NOTE: Make sure the NetApp Cluster clock is within 5 Minutes of Domain prior to running. You
can use the NetApp PowerShell Cmdlet Invoke-NcSSH “date” to find the time on NetApp
Controller
3. Verify the results of the script. You should have:
a. CIFS (SMB 3.0) share
b. NFS Mount Point
c. New DataStore Mounted in ESX
37
5.4
Perform storage vMotion for VMs
Before you can begin the conversion of VMs using the MAT, you need to have the VMs’ storage
physically reside on the NetApp controller so that the VMs can be converted by Shift. The
reccomended method to do this is to perform a storage vMotion of the VMs’ disks and move
them to the NFS share created in the previous step. Storage vMotion will allow you to move the
VM’s storage without affecting the operation of the machine or shutting the machine down.
Any VM that will be converted by the MAT will need to reside on the NFS share created by the
previous step. You do not need to move all the VMs at once, they can be staged and converted
in groups if desired.
Depending on how many VMs you move and the conditions of your network, this step could
take a long time. Please plan appropriately and complete this step fully (if only for the group of
VMs being converted) before moving on to the next step.
5.5
Configure Network Map relationship
Since vSphere and Hyper-V use different network architectures, we must first create a
relationship map between the two. In vSphere all network configuration is contained in the
PortGroup itself.
Hyper-V uses a combination system where the network details are contained in the switch, but
an optional VLAN can be applied to the VM itself. Configure the Network Map accordingly by
specifying the source VMware vSwitch name, and the destination Hyper-V VMSwitch name, and
optional VLAN if using guest tagging.
1. From a PowerShell prompt run:
.\ConvertVM.ps1 -AddNetworkMap -VirtualPortGroup <PG name> -VMSwitch <HV Switch> VLAN <Optional VLAN>
OR
2. To start MAT run .\ConvertVM.ps1 in PowerShell. Run this as an administrator.
3. Enter the Network Map menu by using the [N] Manage Network option.
4. Enter [A] Add Network to add a new Network map.
5. Specify the vSphere Port Group name, Hyper-V vSwitch name, and optional Vlan Tag.
38
39