Windows Server 2012

Beyond Virtualization
Enabling Hyper-V over SMB
Enabling Hyper-V over SMB

Why should I care?

Technology Overview

Demo

Next Steps
Enabling Hyper-V over SMB
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
Enabling Hyper-V over SMB
Why should I care?
Why should I 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.
Enabling Hyper-V over SMB
Technical Overview
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.
Common Configurations
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

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 Domain\HVAdmin, Domain\HV1$, Domain\HV2$,
Domain\HVC$ # Set NTFS permissions from the file share permissions (Get-SmbShare
VMS1).PresetPathAcl | Set-Acl
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 \\FST\VMS

3. To confirm migration:

Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path

Enabling Hyper-V over SMB
DEMO
SMB 3.0 Overview
http://technet.microsoft.com/en-us/library/hh831795.aspx

Deploy Hyper-V over SMB 3.0

http://technet.microsoft.com/en-us/library/jj134187.aspx

Windows Server Blogs

http://blogs.technet.com/b/windowsserver/

Windows Server 2012 Home Page and Product

Download
http://www.microsoft.com/en-us/server-cloud/windows-
server/2012-default.aspx