Hyper-V Live Migration and Live Storage Migration Benjamin Armstrong Senior Program Manager Lead...

Hyper-V Live Migration and Live Storage MigrationBenjamin ArmstrongSenior Program Manager Lead

VIR314

Mobility Core to Private Cloud

Virtualization is the basis of a Microsoft private cloudVirtual machine mobility is key an efficient and responsive private cloud deployment

Agenda

Live Migration

Live Migration without Infrastructure

You can even live migrate virtual machines between two Hyper-V servers with no shared infrastructure

Need to be in the same domainEntire virtual machine moved (VHDs + running state) with no downtime

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

Negotiation

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

LM Connection

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

LM Connection

Storage Migration

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

LM Connection

Virtual Hard DisksStorage Mirror

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

LM Connection

Virtual Hard DisksStorage Mirror

Live Migration

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

LM Connection

Virtual Hard DisksStorage Mirror

Live Migration

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

LM Connection

Virtual Hard Disks

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

LM Connection

Virtual Hard Disks

Hyper-V Server 1 Hyper-V Server 2

VMMS VMMS

Virtual Machine

Virtual Hard Disks

Demo

Live Migration

PowerShell

Move-VM "File Server 1" "benarm-epsilon" ` -IncludeStorage –DestinationStoragePath ` "J:\File Server 1"

Agenda

Live Migration using SMB

Live Migration with SMB

Storage is not moved, just the running virtual machine

Like live migration in a cluster, without high availabilityRequires SMB 3.0

Setting up SMB for Live Migration

There are a couple of steps involved in getting this rightBoth users and computers need access to the share

Setting up the share – Share Permissions

Setting up the share – Share Permissions

Setting up the share – Share Permissions

Setting up the share – File Permissions

Setting up the share – File Permissions

Setting up the share

Setting up the share

PowerShell

MD X:\VMSICACLS.EXE X:\VMS --% /Grant benjamin:(CI)(OI)FICACLS.EXE X:\VMS --% /Grant epsilon$:(CI)(OI)FICACLS.EXE X:\VMS --% /Grant zeta$:(CI)(OI)FICACLS.EXE X:\VMS /Inheritance:RNew-SmbShare -Name VMS -Path X:\VMS –FullAccess ` benjamin, epsilon$, zeta$

Demo

Live Migration - SMB

PowerShell

Move-VM "File Server 2" "benarm-epsilon"

Agenda

Live Migration and Clusters

Live Migration Improvements

Live Migration in Windows Server 2008 R2 is greatbut how to make it better?

Live Migration Improvements

Live Migration in Windows Server 2008 R2 is greatbut how to make it better?

FasterConcurrent live migrationDeeper integration into clusteringEtc…

Live Migration between clusters

You can move a virtual machine between two clusters

Follow these steps:Remove the virtual machine from the source clusterUse Hyper-V Manager to live migrate the virtual machine to a node in the destination clusterJoin the virtual machine to the destination cluster

Or just use SCVMM 2012 SP1Virtual machine never needs to be turned off

However, it is not protected from hardware failure during the course of the migration.

Demo

Live Migration between Clusters

Agenda

Live Migration Security

Configuring Live Migration

Ensure Live Migration Networks are Secure

Physically SecureIPSec / other encryption options

Managing security and authentication

This gets very complicated once more than two computers are involved

And sometimes even when there are only two computers involved

Credentials

Understanding credential security

Credentials

Understanding credential security

Credentials

Understanding credential security

Credentials

How this affects Hyper-V

Live Migrate

Live Migrate

How this affects Hyper-V

Live

Migrate

How this affects Hyper-V

Live Migrate a VM to me

Live Migrate

How to make this work?

Two options:Allow user credentials to be shared between the Hyper-V servers – just for the purposes of live migration

Enable “Constrained Delegation” in Active Directory

Make it look like we are actually logged into the Hyper-V server that starts the live migration

PowerShell RemotingRemote DesktopSCVMM with RunAs Accounts

Enabling Constrained Delegation

On the domain controller, open Active Directory Users and Computers.In the console tree, under DomainName, click Computers.Right-click the computer running Hyper-V, and then click Properties.On the Delegation tab, click Trust this computer for delegation to specified services only.Click either Use any authentication protocol or Use Kerberos only.Click Add, and then click Users and Computers.Type the name of the other computer running Hyper-V, and then click OK.From the list of available services, select Microsoft Virtual System Migration Service and CIFS and then click OK.

More Resources

Taylor Brown’s Blog:http://blogs.msdn.com/b/taylorb/

Official Documentation:http://technet.microsoft.com/en-us/library/jj134199

PowerShell Remoting with CredSSPOn the server:

Enable-WSManCredSSP Server

On the clientEnable-WSManCredSSP Client –DelegateComputer <FQDN of the server>

Establish the session: New-PSSession <FQDN of the Server> -Authentication CredSSP -Credential <User> | Enter-PSSession

Or just run a command:ICM <FQDN of the Server> {<command to run>} -Authentication CredSSP -Credential <User>

Remote Desktop

Hopefully I do not need to tell you how to use this

Agenda

Storage Migration

Storage Migration

Move any part of a running virtual machine with no need to turn it off

VHDsConfig filesSnapshotsEtc…

Perform storage upgrades with no downtimeRespond to I/O bottlenecks with no downtime

Hyper-V

VHD Software

Storage Migration Architecture

Virtual Machine

Source Device Destination DeviceVHD

Hyper-V

VHD Software

Storage Migration Architecture

Virtual Machine

Source Device Destination DeviceVHD VHD

Hyper-V

VHD Software

Storage Migration Architecture

Virtual Machine

Source Device Destination DeviceVHD VHD

Hyper-V

VHD Software

Storage Migration Architecture

Virtual Machine

Source Device Destination DeviceVHD VHD

Hyper-V

VHD Software

Storage Migration Architecture

Virtual Machine

Source Device Destination DeviceVHD

Demo

Storage Migration

PowerShell

Move-VMStorage "File Server 3" ` -DestinationStoragePath ` "K:\File Server 3"

Storage Migration – Performance

Data is moved with an un-buffered file copy operation

XCOPY /JCauses a lot of I/O churn

Configuring Storage Migration

Agenda

Importing virtual machines

Improvements to VM Import

Basic building block of mobilityImprovements:

1. Allow you to import a raw XML file2. Provide ability to “fix up” virtual machine during

import

Demo

Importing a VM

PowerShell

PS C:\> Import-VM "J:\Import\76F5DA48-5181-4E75-83ED-FB2F65B56C8F.xml" -Copy -VhdSourcePath "J:\Import"Import-VM : Unable to import virtual machine due to configuration errors. Please use Compare-VM to repair the virtual machine.At line:1 char:1+ import-vm "C:\Users\benarm\Desktop\Import\76F5DA48-5181-4E75-83ED-FB2F65B56C8F.x ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Import-VM], VirtualizationOperationFailedException + FullyQualifiedErrorId : Microsoft.HyperV.PowerShell.Commands.ImportVMCommand

PowerShell

PS C:\> $VMCompatReport = Compare-vm "J:\Import\76F5DA48-5181-4E75-83ED-FB2F65B56C8F.xml" -Copy -VhdSourcePath "J:\Import"PS C:\> $VMCompatReport

VM : Microsoft.HyperV.PowerShell.VirtualMachineOperationType : ImportVirtualMachineDestination : ZetaPath : J:\Import\76F5DA48-5181-4E75-83ED-FB2F65B56C8F.xmlSnapshotPath :VhdDestinationPath : G:\Users\Public\Documents\Hyper-V\Virtual Hard DisksVhdSourcePath : J:\ImportIncompatibilities : {33012, 14420}

PowerShell

PS C:\> $VMCompatReport.Incompatibilities | ft message

Message-------Could not find Ethernet switch 'Public'.Cannot assign the specified number of processors for virtual machine 'A random virtual machine' is out of range. The range is 1 through 12. (Virtual machine ID 76F5DA48-5181-4E75-83ED-FB2F65B56C8F)

PowerShell

PS C:\> Set-VMProcessor -VM $VMCompatReport.VM -count 2PS C:\> get-vmnetworkadapter -VM $VMCompatReport.VM | disconnect-vmnetworkadapterPS C:\> import-vm $VMCompatReport

Name State CPUUsage(%) MemoryAssigned(M) ---- ----- ----------- ----------------- Virtual machine to import Off 0 0

Agenda

Comparing Technologies

Zero Downtime

Protects against hardware failure

Protects against site failure

Protects against data corruption

Automatic response to failure

Workgroup compatible

Live Migration J L L L L LStorage Migration J L L L L JImport / Export L L L L L JClustering K J K L J LHyper-V Replica L J J K L JBackup L J K J L J

Related Content

VIR312: What's New in Windows Server 2012 Hyper-V, Part 1

VIR315: What's New in Windows Server 2012 Hyper-V, Part 2

VIR321: Enabling Disaster Recovery using Hyper-V Replica

VIR413: Hyper-V Performance, Scale & Architecture Changes

Find Me Later At @VirtualPCGuy

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS

PRESENTATION.