Windows 8 Hyper-V: Availability

• Statements about capabilities or benefits are subject to change

• Packaging and licensing have not yet been determined

• Any concepts shown are for illustration purposes only

Disclaimer:
This presentation contains preliminary information that may be changed substantially prior to final commercial release of the software described herein.
The information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of the presentation. Because Microsoft
must respond to changing market conditions, it should not interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of the information
presented after the date of the presentation. This presentation is for informational purposes only.
MICROSOFT MAKES NO WARRANTIES, EXPRESSED, IMPLIED ,OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Microsoft may have patents, patent applications, trademarks, copyrights or other intellectual property rights , covering subject matter in this presentation. Except as expressly
provided in any written license agreement from Microsoft, the furnishing of this information does not give you any license to these patents , trademarks, copyrights or other
intellectual property rights.

MISSION CRITICAL WORKLOADS

Windows Server 8 – Developer Preview

FLEXIBLE

STORAGE PROCESSOR MEMORY NETWORK

• VM Health Monitoring detection inside virtual machine
• Clustering in the host identifies app failures and takes recovery action
1. Host level HA recovery
• Failover Clustering fails over VM to another node
2. Guest level HA recovery APP
• Failover Clustering Reboots VM
3. Application level recovery
• Service Control Manager (SCM) or event triggered

• Generic health monitoring for any application
– Monitor services through Service Control Manager
– Generation of specific Event ID’s
• ISV opportunity to leverage GuestSetCriticalState() with to integrate 3rd party
application monitoring solutions in the VM

According to Gartner about 1/3 companies use outside
companies to dispose of PCs & Servers

ENCRYPTED CLUSTER VOLUMES


Hyper-V Replica
 Affordable

 Simple to configure

 Works with your current hardware

 Comes in the box in Windows 8

 Single wizard setup

 All you need is two connected servers

 No Guest dependencies


DISASTER RECOVERY FOR EVERYONE


VM1 Root Partition VM2
VM NIC Host NIC VM NIC
• Yes! NIC Teaming is supported with the
Extensible Switch
Hyper-V Extensible Switch
Extension Protocol

Capture Extensions

WFP Extensions

Filtering Extensions

Forwarding Extensions

Extension Miniport
Team NIC

Physical NIC Physical NIC Physical NIC


Configuration
VM

Host 1 Host 2

Extensible Switch Extensible Switch
Extension Protocol Extension Protocol

Runtime State
Extension A Extension A

Extension Miniport Extension Miniport


Turn On IOV Live Migration Post Migration
• Enable IOV (VM NIC Property) • Switch back to Software path • Reassign Virtual Function
• Virtual Function is “Assigned” • Remove VF from VM • Assuming resources are available
• “NIC” automatically created • Migrate as normal
• Traffic flows through VF
• Software path is not used

Virtual Machine
Network Stack

“NIC” “NIC”
Software NIC
VM has connectivity even if
• Switch not in IOV mode
Software Switch Software Switch
• IOV physical NIC not present
(IOV Mode) (IOV Mode)
• Different NIC vendor
Virtual Function Virtual Function
• Different NIC firmware
Physical NIC Physical NIC
SR-IOV SR-IOV Physical NIC


Fibre Channel from the guest

• Guest Clustering
• Cluster service runs inside a VM
Cluster

• Apps and services inside the VM are managed by the cluster
• Apps move between clustered VMs Fiber Channel

• Historically required iSCSI shared storage
• New virtual “Fiber Channel Adapter”
• Up to four virtual HBAs assigned to each guest
• WWNs assigned to each virtual HBA

DSM Guest MPIO

DSM Host MPIO

STORAGE

ARCHITECTURE

Cluster

Node 1 Node 2

Green = Storage
Blue = Networking
Shared Storage: SAS, iSCSI, FC or SMB

ARCHITECTURE

Host 1 Host 2

SMB File Server


ARCHITECTURE

Storage 1 Storage 2

Hyper-V Server


1. Reads and writes go to
VHD on Source device
Hyper-V Server 2. VHD is copied from
Source to Destination
Virtual Machine device

3. After copying, mirror
writes to Source and
Destination
VHD Stack
1 4. After Source and
Destination storage are
3 synchronized, transfer
2 access to the VHD to the
Destination device

5. VHD from Source device
VHD 5 VHD 4 is deleted

Source Device Destination Device

ARCHITECTURE

Host 1 Host 2

Blue = Networking

No Shared Storage


MOBILITY WITHOUT LIMITS
Windows Server 8
Windows Server 2008 Windows Server 2008 R2
Developer Preview
Yes, with no limits. As
No, Quick Migration one at
Live Migration Yes, one at a time many as hardware will
a time
allow
Live Migration Storage
SAN required SAN required Any Storage Solution
Requirements
Live Migration Shared iSCSI, Fiber Channel, SAS
iSCSI, Fiber Channel or SAS iSCSI, Fiber Channel or SAS
Storage or SMB
Yes, with no limits. As
No. Quick Storage Migration No. Quick Storage Migration
Live Storage Migration many as hardware will
via SCVMM via SCVMM
allow
Live Migration Between
No No Yes
Clusters


• Hyper-V Replica for Asynchronous Replication
Disaster Recovery
• Integration with Storage Arrays for Synchronous Replication

• Non-Cluster Aware Apps: Application Health detection
Application/Service
Failover • VM Guest Cluster: iSCSI, Fiber Channel, FCoE
• VM Guest Teaming of SR-IOV NICs

• Network Load Balancing & Failover via Windows NIC Teaming
I/O Redundancy • Storage Multi-Path IO (MPIO)
• Multi-Channel SMB

• Live Migration for Planned Downtime
Node Redundancy
• Failover Cluster for Unplanned Downtime

Hardware Fault • Windows Hardware Error Architecture (WHEA)/RAS

Windows 8 Hyper-V: Availability

Windows 8 Hyper-V: Availability

More Related Content

What's hot

Viewers also liked

Similar to Windows 8 Hyper-V: Availability

More from Microsoft TechNet - Belgium and Luxembourg

Recently uploaded

Windows 8 Hyper-V: Availability

Editor's Notes