Transcript Slides

Jeff Woolsey
Mike Sterling
Principal Group Program Manager Program Manager
Windows Server, Hyper-V
Windows Server, Hyper-V
Agenda
Overview of Live Migration
Typical Live Migration customer scenarios
Technology overview (Live Migration)
Storage management during Live Migration
Walkthrough: setting up Live Migration
Best practices for setting up Live Migration
What is Live Migration?
Move a running virtual machine from one host to another host with no
perceived downtime for the VM
VM is not aware of the migration
Maintain TCP connections of the guest OS
Building block for Dynamic Data Center through business agility, cost reduction
and increase in productivity
VM is treated as a black box
How is it different from Quick Migration?
VM is saved and restored on destination
Results in downtime for applications/workloads running inside VMs
Both leverage same storage infrastructure – easy to move from QM to LM
Live Migration is a planned failover solution
Key scenario 1: Host servicing
Live Migrate VMs from
source to destination
Service Source – patching or
hardware servicing, no
downtime seen by VMs
on destination
Live Migrate VMs from back
from destination to source
No workload downtime during maintenance window
Key scenario 2: Load Balancing
R2
Key scenario 3: Green IT – Power Management
Server 2
Day1, 8:00
AM: Web
clients are
connected to
Web servers
running in
VM1 to VM4
Web clients
Network
VM1
VM2
VM3
VM4
Server 1
During business hours, both servers are in use
Key scenario 3: Green IT – Power Management
Day 1, 6:00 PM:
Number of Web
clients are
dropped, load on
Web servers is
reduced
Day1, 8:00 PM:
VM3 and VM4
are live migrated
to Server 1
Day1, 8:01 PM:
Server 2 is
turned off
Server 2
Web clients
Network
VM1
VM4
VM3
VM2
Server 1
During off-peak or non-business hours, number of
clients go down
Key scenario 3: Green IT – Power Management
Day2, 7: 00 AM:
Number of Web
clients are
increasing, load
on Web servers
is going up
Day2, 7:30 AM:
Server 2 is
turned on
Day2, 7: 45 AM:
VM3 and VM4
are live migrated
to Server 2
Server 2
Web clients
Network
VM3
VM4
VM1
VM2
Server 1
Following day as business starts, load/demand go
up, VMs are live migrated back
How Does Live Migration Work?
Prerequisites:
Source and Destination computers running WS08 R2
Source and destination nodes must be part of a Failover
Cluster
Files used by the VM must be located on shared storage
Failover Cluster
Source Node
Destination Node
.BIN
.VSV
.XML
.VHD
Storage
How Does Live Migration Work?
Phase 1: Setup
Create TCP connection between source and
destination nodes
Transfer VM configuration data to destination node
Create a new VM on the destination node
Configuration
Data
Source Node
Destination Node
.BIN
.VSV
.XML
.VHD
Network Storage
How Does Live Migration Work?
Phase 2: Memory transfer
Transfer the content of the VMs memory to the
destination node
Track pages modified by the VM, retransfer these pages
Pause the VM before the final transfer pass
Memory
Content
Source Node
Destination Node
.BIN
.VSV
.XML
.VHD
Network Storage
How Does Live Migration Work?
Phase 3: State transfer and VM restore
Save register and device state of VM on source node
Transfer running state and storage ownership to
destination node
Start running VM on destination node
Cleanup VM on source node
Running State
Source Node
Destination Node
.BIN
.VSV
.XML
.VHD
Network Storage
Storage Management During Live Migration
Live Migration requires VMs to use shared storage
SAN LUNs managed by the Failover Clustering service
Traditionally, each VM needs its own LUN
Volumes cannot be concurrently mounted on multiple nodes
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
SAN
Storage Management During Live Migration
The migration of a VM with a dedicated LUN requires that
the ownership of the LUN is moved from the source to the
destination node
Time-consuming, requires the volumes on the LUN to be offlined on
the source node and onlined on the destination node
Is part of the blackout period
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
SAN
Cluster Shared Volumes (CSV)
New feature of Failover Clustering in Windows
Server 2008 R2
Single consistent namespace for the volumes on
all nodes
%SystemDrive%\ClusterStorage\VolumeX
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
SAN
CSV and Live Migration
Moving the files of a VM during a migration becomes as simple as
closing the files on the source node and opening the files on the
destination node
Additionally, CSV significantly simplifies the administration of the SAN
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
.BIN
.VSV
.XML
.VHD
SAN
Mike Sterling
Program Manager
Virtualization
Demo Configuration
My Demo:
Cluster Nodes:
Dell Optiplex 745
Quad Core, 8 GB RAM
Storage:
Dell SC1430
3 x 160 GB Disk, RAID
Microsoft iSCSI Target
Networking:
Multiple Gigabit Interfaces on
server, single on node
Other:
All running Windows Server
2008 R2
Best Practices:
Cluster Nodes:
Hardware with Windows Logo
+ Failover Cluster
Configuration Program (FCCP)
Storage:
Storage with Windows Logo +
FCCP
Networking:
Multiple Gigabit Interfaces
CSV uses separate network
Other:
All running Windows Server
2008 R2
Storage Requirements
CSV + Live Migration
Required? No
Recommended? Yes
Other solutions include:
3rd party Clustered File System
SanBolic Melios
HP PolyServe
Demo Environment Overview
Live Migration via CSV: Step 1
Install WS08 R2 on all systems
Add Hyper-V Role
Install WS08R2 VM on Storage Server
Will act as DC for the demo
Domain required for failover clustering
Add failover clustering role on cluster nodes
Run DCPromo on VM
Join machines to domain
Optional: Add DHCP role
Live Migration via CSV: Step 2
iSCSI Target Configuration
Microsoft iSCSI Software Target
Included in Windows Storage Server – now
available for MSDN/TechNet subscribers!
Alternative iSCSI Targets
Starwind iSCSI Target
SANFly
Create Volumes
1 GB for quorum
Remainder for CSV
Ensure bindings are correct!
Live Migration via CSV: Step 3
Configure Networking on nodes
Create Hyper-V External Virtual Network
Assign Static IP to Virtual NIC
Launch iSCSI Control Panel
Start -> Administrative Tools -> iSCSI Initiator
Log in to iSCSI target
Live Migration via CSV: Step 4
Create iSCSI Target for cluster
Use IQN (iSCSI Qualified Name)
Add both cluster nodes
Assign volumes to target
From Node 1, open Disk Management and
online / format disks
Disk 1: Letter Q, Label: Quorum
Disk 2: Letter S, Label: CSV
Ensure that “Add this connection to the list of
Favorite Targets” is set!
Live Migration via CSV: Step 5
Open Failover Cluster Manager
Form Cluster
Cluster Validation Wizard
Enable CSV
Add Disk to CSV
Live Migration via CSV: Step 6
Create VM on CSV volume
(c:\clustervolume\volume1)
Add as cluster resource
Power on VM
Live Migrate!
Changes at WS08R2 RTM
Need multiple NIC’s if using iSCSI
NIC 1: Normal Network Traffic
NIC 2: iSCSI Traffic
NIC 3: CSV Traffic
A centralized, heterogeneous management solution for the virtual datacenter
Support for new WS2008 R2 features
Live migration: Includes compatibility checks
Network optimization: VMQ and Chimney
Hot add/remove of VHDs, Pass-through disks
Storage migration (migrate storage of running VM)
Rapid provisioning (templates)
Support for CFS (CSV and 3rd party solutions)
SAN-related enhancements
Migration in and out of clusters
Support for single target iSCSI with multiple LUNs
Host maintenance mode (host evaluation)
VDI (RDS integration)
RC available
end of May;
RTM within 60
days of
WS2008 R2
Maintenance Mode
Apply to all host and
host clusters
Two options
Save-state (no
migration)
Live-migrate all
running HA VMs and
save-state for non-HA
running VMs
In Maintenance Mode
When host is in maintenance mode,
Host state is not monitored;
No VM creation is allowed;
No VM can be moved into the host;
Host is excluded from any placement.
What can users do?
Request to remove host;
Request to start / stop VMs;
Request to change host properties;
Request to move VM out of the host; …
Exit Maintenance Mode
When host is taken out of maintenance mode,
The next host refresher will update host to its
current state;
No VM is auto-migrated back;
No VM is auto-restarted;
Host is now available for placement.
Microsoft Hyper-V Server V2
New Features
Live Migration
High Availability
New Processor Support
Second Level Address Translation
Core Parking
Networking Enhancements
TCP/IP Offload Support
VMQ & Jumbo Frame Support
Hot Add/Remove virtual
storage
Enhancements to SCONFIG
Enhanced scalability
Manage Remotely…
Live Migration $$ Comparison
Hyper-V Server R2
VMware vSphere
3 Node Cluster
2 Socket Servers
Free
$13,470
3 Node Cluster
4 Socket Servers
Free
$26,940
5 Node Cluster
2 Socket Servers
5 Node Cluster
4 Socket Servers
Free
$22,450
Free
$44,900
For $500 add VMM 2008 R2 (Workgroup Edition) to manage MS Hyper-V Server R2:
•Physical to Virtual Conversion (P2V); Quick Storage Migration; Library Management;
•Heterogeneous Management; PowerShell Automation; Self-Service Portal and more…
Resources
www.microsoft.com/teched
www.microsoft.com/learning
Sessions On-Demand & Community
Microsoft Certification & Training Resources
http://microsoft.com/technet
http://microsoft.com/msdn
Resources for IT Professionals
Resources for Developers
www.microsoft.com/learning
Microsoft Certification and Training Resources
Complete an
evaluation on
CommNet and
enter to win!
© 2009 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.