This document discusses new features and enhancements in Hyper-V virtualization in Windows Server 2012. It addresses industry trends driving changes in IT including new apps, device proliferation, data explosion, and cloud computing. Windows Server 2012 Hyper-V aims to scale workloads cost effectively, build private clouds, and securely connect to cloud services. New features allow for improved scalability and performance including support for 64 virtual processors and 1TB RAM per VM. It also improves connectivity through features like shared nothing live migration, network virtualization, and identity federation across clouds. These enhancements help organizations respond quickly to business needs, control costs, and connect datacenters securely.

1. Hyper-V’s Virtualization Enhancements

2.  Industry trends and challenges
 Windows Server 2012: Beyond virtualization
 Complete virtualization platform
 Improved scalability and performance
 Connecting to cloud services
 Summary
 Get started

3. New
apps
Device
proliferation
Data
explosion
Cloud
computing

4. Beyond virtualization
Scale and secure workloads, cost-effectively build a private
cloud, and securely connect to cloud services
The power of many
servers, the simplicity
of one
Efficiently manage infrastructure while maximizing uptime
and minimizing failures and downtime
Every app, any cloud
Build on an open and scalable web platform that supports
applications across premises
Modern workstyle,
enabled
Support a mobile and flexible work style

5. Respond with agility to
changing business needs
Control costs and improve
efficiency
Connect datacenters to
remote sites and clouds

6. COMPLETE VIRTUALIZATION
PLATFORM
Fully isolated, multitenant
environment
IMPROVED SCALABILITY
AND PERFORMANCE
High-density, scalable
environment
CONNECTING TO
CLOUD SERVICES
Common identity and
management framework

7. Increase VM
mobility
Ensure resource
availability
Simultaneous live
migrations
Provide a fully isolated,
multitenant environment that
includes tools to help
guarantee SLAs, enable
chargebacks, and support selfservice delivery
Create and isolate
virtual networks
Hyper-V Network
Virtualization
Resource Metering
Shared-nothing live
migration
Hyper-V Extensible
Switch
Storage live migration
Easier-to-use
administrative tools
Quality of Service
(QoS) features

8. Shared Nothing - Live Migration

9. Shared Nothing Live Migration
• The ability to move a virtual machine while it is running
from one host to another without requiring shared
storage
• Faster and simultaneous migration
• Entire VM moved with no downtime
• VHD, configuration files, snapshots, etc.
• Improved performance and flexibility
• No longer requires a clustered environment or shared
storage*
• * Live Migration can be done with shared storage and
clustered VMs, but ―Shared Nothing‖ does not require
either

10. Why Should You Care?
The challenge…
• In Windows Server 2008 R2, migration of Hyper-V data required a shared
infrastructure
• Implementing shared storage and failover clustering can be expensive
• In order to migrate data from one host to another, both had to have a
simultaneous connection to a shared storage device that could buffer data
The Windows Server 2012 solution…
• Shared nothing means the hosts needs to share nothing but a simple Ethernet
connection to each other
• Data is migrated without the need for a costly infrastructure
• No devices are required to assist with buffering

11. Live Migration – Moving a Running VM
without Shared Storage
Standard Ethernet connection
1. Live Migration setup occurs
2. Memory pages are
transferred from the source
server to the destination
server
3. Modified pages are
transferred to destination
server
4. State is transferred to
destination server
5. VM brought online on
destination server
6. Network cleanup occurs

12. Configuring Live Migration

13. Performing Live Migration

14. Performing Live Migration, (Cont.)

15. Performing Live Migration, (Cont.)

16. Performing Live Migration, (Cont.)

17. Hyper-V Replica

18. What is Hyper-V Replica?
A virtual machine level replication solution which efficiently replicates data over a
LAN/WAN to a remote (Replica) site without relying on software or hardware
technologies outside of the Windows Server 2012 operating system
• New in Windows Server 2012 Hyper-V Role
• Storage and Workload agnostic, Replica Servers can be standalone or a Failover Cluster
• Servers can be members of a workgroup or a domain (same or different); Primary and Replica
servers do not need to be in the same domain unless part of a Failover Cluster
• Managed locally (Hyper-V Manager) or remotely (Hyper-V Remote Server Administration Tools
(RSAT) or System Center Virtual Machine Manager (SCVMM)
• 4 Deployment Scenarios
•Head Office and Branch Office (HO-BO)
•Enterprise Datacenter
•Hosting Provider Datacenter
•Customer Office and Hosting Provider Datacenter (Cross-Premise)

19. Why Should You Care?
The challenge…
• Provide business continuity and minimal downtime of virtualized servers during times
of disruption
Hyper-V Replica provides an efficient, cost-effective solutions…
• Allows a Hyper-V administrator to execute a failover of production workloads to replica
servers at a secondary location within minutes (in the event of fire, power outage, server
failure, etc.)
• Provides the necessary management APIs to enable IT management vendors to build an
enterprise class Disaster Recovery solution for customers
• Enables Infrastructure as a Service (IaaS) for hosting providers that host dedicated/virtual
servers for customers
• Seamlessly integrates with Clustering and Volume Shadow Services (VSS)
• Supports heterogeneous storage between primary and recovery
• Previously multi-site clustering required a 3rd party replication solution

20. Installation Requirements
• Hardware that supports the Hyper-V Role on Windows Server 2012
• Sufficient storage on both Primary and Replica servers to host the files used
by virtualized workloads
• Network connectivity between the locations hosting the Primary and Replica
servers
• Properly configured firewall rules to permit replication between the Primary
and Replica sites
• An X.509v3 certificate to support Mutual Authentication with certificates (if
desired or needed)

21. Installation and Configuration
1. Add Hyper-V role on Primary and Replica servers
• Add Role and Feature Wizard (ARFW) in Server Manager
• Deployment Image and Service Management (DISM)
dism /online /enable-feature /featurename:Microsoft-Hyper-V
• Server Manager Powershell cmdlet
Install-WindowsFeature –Name Hyper-V –IncludeManagementTools
2. Run Best Practices Analyzer to confirm
installation and verify functionality
3. Configure Replication
•
•
Standalone
Failover Cluster
4. Enable each Virtual Machine for replication
(Enable Replication Wizard)
5. Or use PowerShell
Set-VMReplicationServer -ReplicationEnabled $true AllowedAuthenticationType Integrated -IntegratedAuthenticationPort
$RecoveryPort -DefaultStorageLocation $ReplicaStorageLocation ReplicationAllowedFromAnyServer $true

22. Architectural Components

23. Hyper-V Replica & Failover Clustering
• Failover Clusters can participate in replication, but only as a single replication server.
• Failover Clusters have a new clustered role, the Hyper-V Replica Broker
• Highly-Available role that moves between nodes
• One instance per cluster
• Changes traditional Hyper-V multi-site (disaster recovery) Failover Clustering.
Previously replication across sites was done between nodes within a single cluster.
• Primary and Replica servers do not need to be in the same domain unless part of a
Failover Cluster
• Replication Scenarios
• Cluster to Cluster
• Cluster to Standalone
• Standalone to Cluster
• Standalone to Standalone

24. Hyper-V Over SMB

25. Hyper-V over SMB
Server Message Block (SMB) protocol…
• Is a network file sharing protocol that allows applications on a computer to read
and write to files and to request services from server programs in a computer
network
• Windows Server 2012 introduces the new 3.0 version of the SMB protocol
With Windows Server 2012, Hyper-V…
• Can store virtual machine files (configuration, VHD, snapshots) in files shares
over the SMB 3.0 protocol
• Is supported for both stand-alone and clustered servers that use Hyper-V with
shared file storage for the cluster
• Can support scale-out file shares and clusters
• Can leverage SMB Multi-Channel

26. Why Should You Care?
• Ease of storage provisioning and management
• You can manage file shares instead of storage fabric and logical unit numbers (LUNs).
• Previously all Hyper-V clusters required shared storage using Fibre Channel, Fibre
Channel over Ethernet, iSCSI or Serial-Attached SCSI.
• Increased flexibility
• You can dynamically migrate virtual machines or databases in the data center.
• Ability to take advantage of existing investment in a converged network
• You can use your existing converged network with no specialized storage networking
hardware.
• Reduced capital expenditures
• Capital expenses (acquisition costs) are reduced.
• Reduced operating expenditures
• You can reduce operating costs because there is no need for specialized storage
expertise.

27. Requirements
• One or more computers running Windows Server 2012 with the File Services
role installed
• One or more computers running Windows Server 2012 with the Hyper-V role
installed (separate from the file server)
• A common Active Directory infrastructure
• The servers running Active Directory Domain Services (AD DS) do not need
to run Windows Server 2012
• Supported configurations
• Standalone Hyper-V servers (no a high-availability solution)
• Hyper-V servers configured in a Failover Cluster
Although not required, Failover Clustering is supported
on the Hyper-V side, the File Services side, or both.
They must be separate clusters.

28. Common Configurations

29. Hyper-V Over SMB Workflow
1. Install the Hyper-V role on a Windows Server 2012 machine
2. Install the File Services role on a Windows Server 2012 machine
3. Create an SMB file share
4. Create a virtual machine and virtual machine hard disk on the file share
5. Migrate existing virtual machine storage to the file share

30. Creating an SMB Share
From Server Manager:
1. Log on or connect to a
Windows Server 2012
computer on which the
File and Storage role is
installed. Open Server
Manager and navigate
to File and Storage
Services
2. In Server Manager, start
the New Share Wizard
With PowerShell:
# Create folder MD X:VMS # Create file share New-SmbShare -Name VMS1
-Path X:VMS -FullAccess DomainHVAdmin, DomainHV1$, DomainHV2$,
DomainHVC$ # Set NTFS permissions from the file share permissions (Get-SmbShare
VMS1).PresetPathAcl | Set-Acl

31. Migrating Storage to an SMB Share
You can migrate from…
• Direct-Attached Storage to SMB file share
• SMB file share to another SMB file share
1. To determine the current storage being used by a virtual machine:
Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path
2. To migrate the virtual machine storage to an SMB file share:
Move-VMStorage –VMName VM1 –DestinationStoragePath FSTVMS
3. To confirm migration:
Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path

32. Network Virtualization
Run multiple virtual networks
on a physical network
WHAT’S REALLY HAPPENING
Abstract network
configuration for virtual
machines
Remove virtual LAN (VLAN)
constraints
Allow flexible placement of
virtual machines—even
offsite
Enable datacenters without
boundaries
Deliver multitenant security
and isolation
Support infrastructure as a
service (IaaS) scenarios
SQL Server
SQL Server
Blue sees
Web
Storage
Web
Storage
Orange sees
SQL Server
Web
Storage
SQL Server
Web
Storage

33. Scale up VMs
64-node Hyper-V
clusters
Deliver a high-density,
scalable environment that can
adapt to perform optimally
based on changing needs
Increase VM density
Dynamic Memory and
smart paging
64 virtual processors
and 1 TB memory per
virtual machine
8,000 virtual machines
per cluster
New 64 TB VHDX
format
Improve VM
performance
Non-Uniform Memory
Access (NUMA) support
Virtual Fibre Channel
support
Hardware offloading

34. Dynamic Memory
Increase virtual machine
density
Increase virtual machine
memory resources,
as needed, without reboot
downtime
Reclaim unused virtual
machine memory resources
for reallocation
Maximum
memory
Maximum
memory
Maximum
memory
Minimum
memory
Minimum
memory
Minimum
memory
Virtual machine
Virtual machine
Virtual machine
Startup

35. Federate identities for
consistent security and ease of
use
Use a common identity and
management framework for
security-enhanced and reliable
cross-premises connectivity
Enable secure cross-premises
connectivity
Federate identity across private, public,
and hybrid clouds
Enable secure connectivity among
geographically separate locations
Support claims-aware identity solutions
Use existing networking equipment
and technology standards
Provide seamless security with a single
sign-on experience
Easily integrate with other federation
platforms
Connect securely to hosting providers
Move virtual machines to other sites
or hosting providers without network
reconfiguration

36. Secure cross-premises connectivity
SQL Server
Virtual Machine
SQL Server
Virtual Machine
HOSTED CLOUD
Windows Server 2012
remote access
site-to-site VPN servers
SQL Server
Web
Storage
Web
Storage

37. How do I embrace the
cloud?
Complete
virtualization
platform
How do I increase the
efficiency in my datacenter?
Improved
scalability and
performance
How do I deliver nextgeneration applications?
How do I enable modern
work styles?
Connecting to
cloud services
IT challenges
Respond with agility to
changing business needs
Control costs and
improve efficiency
Connect datacenters to
remote sites and clouds

38. 1. Download Windows Server 2012
2. Learn more about Windows Server 2012, Microsoft Private Cloud solutions, and
Microsoft System Center 2012
3. Work with a EPC Group for the proof of concept, roadmap, and overall architectural design