Datacenter & Cloud Consolidation and Migration

MAT4MOVE - Build Guide

Table of Contents

1 Overview....................................................................................................42 Solution Architecture.................................................................................53 Double-Take Move Requirements..............................................................7

3.1 Hyper-V.........................................................................................................73.2 VMware.........................................................................................................73.3 MAT Server....................................................................................................73.4 Double Take Activation codes.......................................................................83.5 Permission Requirements..............................................................................83.6 Other Assumptions........................................................................................83.7 System Requirements...................................................................................9

3.7.1 Source Server (VMWare Virtual Machines).................................................93.7.2 Target Server...............................................................................................123.7.3 MAT Server...................................................................................................13

4 Install Instructions....................................................................................144.1 Installing Double-Take Move Software........................................................144.2 MAT Server Configuration...........................................................................20

4.2.1 Installing .Net Framework...........................................................................204.2.2 Installing VMware PowerCLI........................................................................224.2.3 Installing SQL Express.................................................................................264.2.4 Configuring MAT Database.........................................................................354.2.5 Configuring Variable.XML............................................................................39

1 OverviewThe purpose of this document is to show how to build the environment that runs the on-premises migration of workloads from VMware to Hyper-V, using the Migration Automation Toolkit for Double–Take Move, also called MAT4Move.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-by-step guidance for installation or configuration of these components.This document assumes that the discovery and assessment of customer environment has been completed and following aspects have been identified:

Source VMware Environmento ESX Serverso vCenter Servers

Target Hyper-V Environmento 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 Double Take move licensing considerations

3

2 Solution ArchitectureDouble-Take Move is a comprehensive server migration Solution. It allows you to move an entire server, known as a source, by mirroring an image of that source to another server, known as the target. The image of the source contains the server's system state (the server's configured operating system and applications) and all of the source server’s data.Double-Take Move uses patented data replication technology that allows users to continue accessing and changing data on the source during the migration. As changes are made on the source, replication keeps the image of the source, stored on the target, up-to-date. Double-Take Move replicates, in real-time, only the file changes, not the entire file, allowing you to more efficiently use resources. When you are ready to cutover to the new server, Double-Take Move applies the source system state and after a reboot, the source workload is available and running on the target server hardware.For those organizations that want to migrate VMware virtual machines, Double-Take Move makes that migration easy and affordable by reducing downtime and complexity. In addition, with the Migration Automation Toolkit for Double-Take Move, called MAT4Move, you can manage the full migration life cycle using MAT framework and PowerShell Scripts. For migrations from VMware to Hyper-V, the VMWare virtual machine is the source while Hyper-V Server is the Target.MAT4Move is a combination of PowerShell scripts that extends the functionality of Double-Take Move and provides additional capabilities like inventory, scheduling and queuing of VMs for Migration.Using MAT4Move, you can discover VMware virtual machines running in VMware VCenter Environment. Once discovered, you can schedule and migrate these Virtual Machines in appropriate batches, live and in real-time. Following is the architecture diagram for MAT4Move

4

Double-Take Move (Client Only or Both)

VMware PowerCLI MAT Scripts SQL Express

Windows Server 2012/ R2

Double-Take Move (Target)

VMware ESX 4.x or 5.x vCenter Server 5.1 or

above VMware Tools

VMWare VSphere

Hyper-VMAT Toolkit

3 Double-Take Move Requirements

3.1 Hyper-VYou 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 qualified 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:

Hyper-V on Windows Server 2012 Hyper-V on Windows Server 2012 R2

3.2 VMwareFollowing are VMware Infrastructure requirements for MAT4Move:

You must have VMware VCenter 5.1 or above in your environment for discovery of VMware Virtual machines.

VMware ESX/ESXi 4.1, 5.0 or 5.1.

3.3 MAT ServerMAT Server is the controller machine that is used to scheduled, initiate and monitoring the migration process. As shown in the architecture diagram, the MAT Server must have following components installed:

Physical or Virtual Windows Server 2012 or Windows Server 2012 R2 .Net Framework 3.5 VMware PowerCLI 5.1 SQL Server 2012 Express Edition Double-Take 7.0 Service Pack 1 (SP1) or later (Client-only or Both) MAT Scripts

The detailed instructions for installation and configuration of MAT Server are provided in Section 4.

3.4 Double Take Activation codesEach Migration using Double-Take Move requires an activation Code. The activation codes are provided by Vision Solution and must be procured by customer before starting migration process. There are two types of activation code:

Source Activation Code: This is used for each source VM that is migrated using Double-Take Move. During the migration process, MAT scripts will install double take agent on the source VM and activate it using Source Activation Code.

Target Activation Code: This is used for Activation of Double-Take agent on the destination Hyper-V Server. Each destination Hyper-V server requires a Target Activation code. The double take agent must be installed and activated on each destination Hyper-V server prior to migration process. This is not automatically done by MAT Scripts.

3.5 Permission RequirementsYou 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 MAT4Move Solution in the customer environment.

MAT Servero Local Admin rights to install and configure MAT4Move Solution

VMwareo Read Access for discovery of Virtual machines and Datacenters in

VCenter environment.o Admin access to perform additional activities like taking Snapshot of

virtual machines before migration 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 Serverso Administrator rights to create new virtual machines

3.6 Other AssumptionsThe MAT4Move scripts will successfully perform virtual machine conversions when the following conditions are met:

The virtual machine to be converted is in a running state. The virtual machine has VMware tools installed. The virtual machine is joined to the same (or trusted) Active Directory

domain as MAT Server.

7

Remote access through Windows Management Instrumentation (WMI) is enabled on the VMware-based virtual machine to be converted and

Remote access through WMI is enabled on the destination Hyper-V host. The Hyper-V host has the required disk space and resources available to host

the converted virtual Machines.

3.7 System Requirements3.7.1 Source Server (VMWare Virtual Machines)The source Server, VMWare Virtual Machines, you are migrating from must meet the following requirements:

Operating system - The source server can be a physical or virtual server running any of the following operating system editions:

o Windows Server 2003 or 2003 R2 Datacenter, Enterprise (i386, x64), Standard (i386, x64), Web Server, Small Business Server, or Storage Server Edition. Each of the Windows 2003 operating systems requires Service Pack 1 or later.

o Windows Server 2008 or 2008 R2 Datacenter, Enterprise (i386, x64), Standard (i386, x64), Essential Business Server, Web Server, Foundation Server, Small Business Server (including SBS 2011), or Storage Server Edition

o Windows 2012 or 2012 R2 Datacenter, Standard, Essentials, or Foundation Edition

File system - Double-Take supports the NTFS and ReFS file system. FAT and FAT32 are not supported.

System memory - The minimum system memory on each server should be 1 GB. The recommended amount for each server is 2 GB.

Disk space for program files - This is the amount of disk space needed for the Double-Take program files. The amount depends on your operating system version and your architecture (32-bit or 64-bit) and ranges from 350-500 MB. The program files can be installed to any volume while the Microsoft Windows Installer files are automatically installed to the operating system boot volume. Make sure you have additional disk space for Double-Take queuing, logging, and so on.

Server name - Double-Take includes Unicode file system support, but your server name must still be in ASCII format. If you have the need to use a server's fully qualified domain name, your server cannot start with a numeric character because that will be interpreted as an IP address. Additionally, all Double-Take servers and appliances must have a unique server name.

Time - The clock on the source and target servers must be within a few minutes of each other, relative to UTC. Large time skews will cause Double-Take errors.

8

Protocols and networking - Your servers must meet the following protocol and networking requirements:

o Your servers must have TCP/IP with static IP addressing. (Some job types allow you to add DHCP addresses for failover monitoring, although only after a job has already been created. Keep in mind that depending on your failover configuration, a source reboot may or may not cause a failover but having a new address assigned by DHCP may also cause a failover.)

o By default, Double-Take is configured for IPv6 and IPv4 environments, but the Double-Take service will automatically check the server at service startup and modify the appropriate setting if the server is only configured for IPv4. If you later add IPv6, you will need to manually modify the DefaultProtocol server setting.

o IPv4 and IPv6 are both supported. o IPv6 is only supported for Windows 2008 and later. o If you are using IPv6 on your servers, your clients must be run from an

IPv6 capable machine.o In order to properly resolve IPv6 addresses to a hostname, a reverse

lookup entry should be made in DNS. DNS updates — To be able to use DNS updates, your environment must meet

the following requirements. o The source and target servers must be in the same domain.o At cutover time, the target must be able to reach the DNS servers that

you want to update.o Each server's network adapter must have the DNS suffix defined, and

the primary DNS suffix must be the same on the source and target. o DNS updates are not supported for NAT environments.

Microsoft .NET Framework - Microsoft .NET Framework version 3.5 Service Pack 1 is required. This version is not included in the .NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed, you will also need version 3.5.1. For Windows 2008 and earlier, you can install this version from the Double-Take DVD, through a web connection during the Double-Take installation, or from a copy you have obtained manually from the Microsoft web site. For Windows 2008 R2 and later, you need to help it through Windows features.

Windows firewall - If you have Windows firewall enabled on your servers, the following are requirements for the Windows firewall configuration:

o The Double-Take installation program will automatically attempt to configure ports 6320, 6325, and 6326 for Double-Take. If you cancel this step, you will have to configure the ports manually.

o If you are using the Double-Take Console to push installations out to your servers, you will have to open firewall ports for WMI (Windows Management Instrumentation), which uses.

9

o RPC (Remote Procedure Call). By default, RPC will use ports at random above 1024, and these ports must be open on your firewall. RPC ports can be configured to a specific range by specific registry changes and a reboot. See the Microsoft Knowledge Base article 154596 for instructions. Additionally, you will need to open firewall ports for SMB (server message block) communications that uses ports 135-139 and port 445, and you will need to open File and Printer Sharing. As an alternative, you can disable the Windows firewall temporarily until the push installations are complete.

You cannot replicate from or to a mapped drive. If any directory or file contained in your job specifically denies permission to

the system account or the account running the Double-Take service, the attributes of the file on the target will not be updated because of the lack of access. This also includes denying permission to the Everyone group because this group contains the system account.

Recursive mount points are not supported. Only data changes cause replication to occur; changing security/ownership or

attributes does not. For encrypted files, only the data, not the attributes or security/ownership, is

replicated.

10

3.7.2 Target ServerThe target Hyper-V host must meet the following requirements:

Operating system - You must have a physical Hyper-V host machine, where Double-Take can create the new virtual server that meets the following requirements.

o Your physical Hyper-V host machine can be any of Windows Server 2012 or Windows Server 2012 R2 operating system that has the Hyper-V role enabled.

o In addition, you can use Server Core 2012 R2, or Server Core 2012 R2 with the Hyper-V role enabled. (Hyper-V Server 2008 and Server Core 2008 are not supported.)

o If you are using Hyper-V Integration Services and your source is running Windows 2003, the source must have Service Pack 2 or later.

o The virtual machines can use raw, pass-through, or differencing disks, however, they will be virtual hard disks on the replica on the target.

System memory - The minimum system memory required for installation of Double-Take software on Hyper-V server(s) is 1 GB. The recommended amount for each server is 2 GB.

Disk space for:o Program files - This is the amount of disk space needed for the Double-

Take program files to be installed on target Hyper-V server(s). The amount depends on your operating system version and your architecture (32-bit or 64-bit) and ranges from 350-500 MB. The program files can be installed to any volume while the Microsoft Windows Installer files are automatically installed to the operating system boot volume. Make sure you have additional disk space for Double-Take queuing, logging, and so on.

o Data files - This is the amount of disk space needed for the source data files. This will be dependent on the applications you are running and the amount of data files you have.

o System state image - This is the amount of disk space for the image of the source system state. The size of the system state will depend on the operating system and architecture. Windows 2003 operating systems need at a minimum 2-3 GB of available space for the system state. Windows 2008 operating systems need at a minimum 7-9 GB of available space for the system state. Windows 2008 R2 operating systems need at a minimum 10 GB of available space for the system state. These minimums are for a clean operating system installation. Operating system customizations, installed applications, and user data will increase the disk space requirement.

Server name - Double-Take includes Unicode file system support, but your server name must still be in ASCII format. If you have the need to use a

11

server's fully qualified domain name, your server cannot start with a numeric character because that will be interpreted as an IP address. Additionally, all Double-Take servers and appliances must have a unique server name.

Protocols and networking - Your target Hyper-V server(s) must meet the following protocol and networking requirements.

o Your servers must have TCP/IP with static IP addressing. (Some job types allow you to add DHCP addresses for failover monitoring, although only after a job has already been created. Keep in mind that depending on your failover configuration, a source reboot may or may not cause a failover but having a new address assigned by DHCP may also cause a failover.)

o IPv4 is the only supported version. Microsoft .NET Framework - Microsoft .NET Framework version 3.5 Service

Pack 1 is required on target Hyper-V server(s). This version is not included in the .NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed, you will also need version 3.5.1. For Windows Server 2012 or later, you need to help it through Windows features.

3.7.3 MAT Server vCenter Server must be accessible over port 80 Hyper-V Infrastructure must be accessible via WMI calls VMware Virtual Machines must be accessible via PowerShell Remoting. Destination Hyper-V IP address must be accessible from Source VM.

12

4 Install Instructions

4.1 Installing Double-Take Move SoftwareUse the following instructions to install Double-Take Move software on the target Hyper-V Server(s) and MAT Server:

1. Close all the applications.

2. Copy the Double-Take Binaries on to the target Hyper-V Server and on the MAT Server.

3. Run the Double-Take executable to extract files into C:\Double-Take directory.

4. From C:\Double-Take Directory, launch autorun.exe. It will open up Double-Take installation Wizard:

5. Select Double-Take MOVE as installation type.

6. You may or may not choose to search for latest binaries. Select appropriate option and click next:

13

7. Accept the Agreement

14

8. Review the Activation notice and click OK:

15

9. Select the installation type as Client and Server Component for Hyper-V Server. You can select Client Components only for MAT Server and click Next:

10.For installation on Hyper-V Server, provide the activation code (Target Code) and click Add. You do not need to provide any activation code for installation on the MAT Server.

16

11.The following message may appear once you add the activation code for Target Server. Click OK

12.Review and change the install location of Double Take if necessary.

13.You may also limit the amount of memory and disk space used by Double Take.

14.Click Next.

17

15.Review the security group message on the screen. Then Click Next:

16.Then click on Install:

18

17.Click Finish, once the installation is complete:

18.Repeat these steps for all destination Hyper-V Hosts.

4.2 MAT Server Configuration4.2.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. There are two methods to install .Net Framework

Method I

1. Login to server as MigrationAdmin. Make sure this ID has local administrative rights on the server. You will use this ID to install MAT4Move Scripts

2. (Optional) Run Windows Update to make sure the server is up to date on all security patches.

3. Open Server Manager.

19

4. Click on Manage and then select Add Roles and Features.

5. After clicking Next, you’ll see the Select installation type screen and select Role-based or feature-based installation and click Next

6. Here on the Select destination server screen, choose the MAT server and click Next.

7. On the next screen, you will see the Select server roles screen. Click Next

8. 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 

9. 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

20

10.Click Install to complete .Net Framework installation

Method IIYou can also install .NET framework from PowerShell Command line:Install-WindowsFeature Net-Framework-Core -source d:\sources\sxs

4.2.2 Installing VMware PowerCLIMAT4Move 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

21

2. Right-click VMWare-PowerCLI-5.1.0-1011025.exe, and select “Run as administrator”

3. You may get the following message:

4. Click OK to continue5. Click Next of first two screens

22

6. Accept the Licensing agreement

7. Choose the default configuration. You may choose to change the install path, then Click Next

23

8. Click Install to start the Installation

9. Click Finish to finish the installation

24

4.2.3 Installing SQL ExpressThe MAT4Move 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 environmentThis section provides instructions for installation of Microsoft SQL Server Express:

1. Logon to the MAT Server as MigrationAdmin account2. 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 installation4. On Feature Selection Screen, select the following features

25

5. Reporting Services is an optional feature, which allows you to create and host custom reports. It is not a required component for migrations.

6. On the next screen, leave the instance name and instance ID as SQLExpress. Click Next

26

7. Make sure that disk space requirements are met. Click Next

27

8. Provide appropriate credentials for Service Accounts. You may use MigrationAdmin Account as service account or customer provided service account

28

9. Add appropriate account including MigrationAdmin Account as SQL Server Administrator

29

10.Choose appropriate configuration from SQL Server Reporting Services

30

11.On the next screen review the configuration and click Install

31

12.Once the installation is done, make sure that all components have installed successfully

32

13.Click next and Close to complete the install process

33

4.2.4 Configuring MAT DatabaseThis sections provides information on configuration of MAT Database

1. Logon to the MAT 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

34

4. Open SQL Management Studio and Connect to .\SQLExpress Instance you installed in previous section.

5. Right-Click SetupMATDoubleTake.sql and open with SQL Management Studio

35

6. Make sure that “master” database is selected in SQL Management Studio

36

7. Click Execute to execute the SQL script

37

8. This script creates a new database called MAT and all tables necessary for migration.

4.2.5 Configuring Variable.XMLVariable.XML is the most important component of MAT4Move. It contains environment specific details and variables used in the migration processThe following table provides the information about the variables in Variable.XML and their description. Edit the Variable.XML file and modify the appropriate information.

Variable Description Default Value

LogPath Path where log files for each migration would be stored

C:\MAT

Datasource SQL Server name for default instance or Server\instance for named instances

.\SQLExpress

Showrows Total number of rows to display in table during conversion

30

38

UseSqlAuthentication

Whether or not to use SQL Server Authentication(0 = No; 1 = Yes)

0

SqlAccount SQL username if using SQL Server Authentication admin

SqlPassword SQL password if using SQL Server Authentication (leave blank to be prompted)

WinAccount Account with rights to logon as administrator on the guest

Administrator

WinPassword Password for account with rights to logon as admin on the guest (leave blank to be prompted)

TargetVmPath Path on the Hyper-V Host to store the migrated virtual machines

C:\MAT_Replicas

MigrationCode Migration source activation code (volume, node-locked)

ModulePath Path to Double-Take PowerShell modules C:\Program Files\Vision Solutions\Double-Take\Console

PackageBasePath Path to Double-Take installation packages C:\Program Files\Vision Solutions\Double-Take

DtAccount Account with Double-Take Admin rights on the target host

Administrator

DtPassword Password for the target host Double-Take Admin account (leave blank to be prompted)

MonitorInterval Number of seconds between requests made to Double-Take on target host in background monitoring job

5

ConcurrentMigrations

The number of concurrent migrations that can be running

20

TargetHost Target Hyper-V Host. FQDN or IP address

39

TargetPower Final Power Status of Target VM (0 = off, 1 = on) 1

DynMac Final MAC Address of Target VM (0 = Keep from VMware) (1 = use Hyper-V Dynamic)

0

SourceHost Source Host (ESX or vSphere) FQDN or IP address

SourceHostAccount

Account that has Admin rights on VMware vCenter or ESX Host

SourceHostPassword

Password for Source Host Admin account (leave blank to be prompted)

40