610 likes | 905 Vues
Hyper-V Storage. Symon Perriman Jeff Woolsey Technical Evangelist Principal Program Manager. Introduction to Hyper-V Jump Start. Agenda. Storage Considerations Creating VHDs Storage options iSCSI Virtual Fibre Channel. MultiPath I/O (MPIO) Offloaded Data Transfer (ODX)
E N D
Hyper-V Storage Symon Perriman Jeff Woolsey Technical Evangelist Principal Program Manager
Agenda • Storage Considerations • Creating VHDs • Storage options • iSCSI • Virtual Fibre Channel • MultiPath I/O (MPIO) • Offloaded Data Transfer (ODX) • Storage Virtualization with Spaces • Hyper-V over SMB
Your input on Storage Leverage storage array capabilities Native access to SANs from VMs • Maximize your investment • No tradeoffs Help reduce the cost of storage Highly Scalable Virtual Disks • For workloads that don’t require a SAN • Big data is here
Storage Considerations Storage performance is almost always the virtualization bottleneck Implement storage solutions with multiple hard drives to distribute disk I/O The faster the drives the better Consider deploying centralized storage SAN/File Server for High Availability & Live Migration
Storage Virtual machines require storage for virtual hard disk files, snapshots, failover clustering, and the application’s data files Physical DAS (SATA, eSATA, PATA, SAS, SCSI) SAN (Fibre Channel, FCoE, iSCSI, SAS) Required for failover clustering so all nodes can access a disk Host clustering: Fibre Channel, FCoE, Serial-Attached SCSI (SAS), iSCSI Guest clustering: iSCSI, FCoE, Fibre Channel, SMB Virtual adapters IDE, SCSI Boot – IDE only Fibre Channel VHD (VHDX) Fixed, dynamic, differencing Pass-through iSCSI direct (applicable to running iSCSI in guest OS)
Creating Virtual Machines Name Location Memory Network Virtual hard disk Operating system New-VM, New-VHD, New-VMSwitch
Creating VHDs Use the Virtual Disk Wizard Disk Type: Fixed, Dynamically Expanding, Differencing Name & Location Configure Disk: Size, Contents can be copied from another location Configuration can be changed using the VM settings IDE controller(s) & location SCSI controller(s) & location Media: VHD, physical hard drive Diskette drive
Virtual Disk Types Dynamic Grows to a maximum size, but will only take as much space as required. Fixed Size of the disk is defined during configuration Regardless of how much is actually stored on the virtual disk, it will take up the maximum amount on the host disk Differencing Stores the delta changes since the differencing disk was created – such as installing an operating system into the parent disk and then creating differencing disks to perform further configurations on
Hot Add/Remove Storage Overview Add and remove VHD and pass-through disks to a running VM without requiring a reboot Hot-add/remove disk applies to VHDs and pass-through disks attached to the virtual SCSI controller Benefits Enables storage growth in VMs without downtime Enables additional datacenter backup scenarios Enables new SQL/Exchange scenarios
Live VHD Merge Windows Server 2012 Hyper-V provides the ability to merge the .avhd files associated with a virtual machine without having to shut it down first In the past, after deleting a snapshot an administrator had to shut down the virtual machine first Merge-VHD
Large Sector Support – Native 4K Disks Hyper-V Host Windows Server 2012 supports native 4K disks Software read-modify-write 512b logical sector virtual disk Performance penalty for RMW 4K logical sector VHDX No performance penalty VM 512 4K 512 VHDX VHDX VHD Software RMW 4K 4K 4K Native 4K Disk
Increased Storage Efficiency – Unmap • Unmap • Storage Informed Of Unused Space • Efficiencies At Virtual Layer • Allows Reuse Of Unused Blocks • Efficiencies At Physical Layer • VMs Unmap Passed To Hardware • Supported On • VHDX & PassThru Disks • Virtual SCSI or Virtual Fibre Channel Hyper-V Host VM VHD Stack VHDX External Storage Array
VHDX The New Default Format for Virtual Hard Disks Enhanced Perf Embed Custom Metadata Up To 64 TB Internal Log MB Alignment Larger Virtual Disks Enhanced Resiliency Large Sector Support Larger Block Sizes User Defined Metadata
VHDX Performance - 32KB Random Writes IOPS Queue Depth 16
VHDX Performance - 1MB Sequential Writes MB/S +25% +25% Queue Depth 16
Over 1 Million IOPs from a Single VM Industry Leading IO Performance VM storage performance on par with native Performance scales linearly with increase in virtual processors Windows Server 2012 Hyper-V can virtualize over 99% of the world’s SQL Server.
Storage Options for Virtual Machines IDE Two IDE controllers Two devices each Methods supported Pass-through Fixed-disk Dynamic Synthetic Used for OS boot partition SCSI Four SCSI controllers 256 devices each Methods supported Pass-through Fixed-disk Dynamic Synthetic
Choosing VM Locations VM Storage VHDs: C:\Users\Public\Documents\Hyper-V\virtual hard disks VMs (configuration): C:\ProgramData\Microsoft\Windows\Hyper-V Virtual machines Snapshots Considerations Performance Hard drive space Security Shared storage for failover clustering
Microsoft iSCSI Software Target iSCSI is a cost effective SAN solution Supports failover clustering Uses the existing IP network Can be a storage array or DAS on a server Free download http://www.microsoft.com/download/en/details.aspx?id=19867
iSCSI Initiator Initiator connects to the iSCSI target Target must be configured Use a dedicated NIC Can use any iSCSI target
Configuring iSCSI Target: Create virtual disks Initiator(s): Request access to disks Target: Accept access request from initiator(s) Initiator(s): Refresh configuration to check connection Initiator(s): Log in to the target Enable automatic reconnections Servers: Initialize, format and bring disks online Now you can use these disks for your VMs or cluster
Virtual Fibre Channel Hyper-V Server Extends Fibre Channel into VMs High-performance workloads Guest clustering Exposes SAN functionality Uses NPIV functionality Support Guest: Windows Server 2008 & later Host: Windows Server 2012 Updated NPIV HBA driver Live migration just works VM VM WWN WWN vHBA vHBA NPIV HBA LUN External Storage Array
Virtual Fibre Channel and Live Migration WWPN A: C0:03:FF:78:22:A0:00:14 WWPN B: C0:03:FF:78:22:A0:00:15 WWPN A: C0:03:FF:78:22:A0:00:14 WWPN B: C0:03:FF:78:22:A0:00:15 1. Create A Temporary VM On Destination Hyper-V Server 2. Connect Temporary VM’s HBAs To FC Fabric Using WWPN B 3. Verify Temporary VM Has Connectivity To Shared Storage 4. Complete Normal VM Live Migration (copy memory etc..) Limit IO Queue Depth To 1 5. Pause Source VM 6. Change Temporary VM To Permanent VM and Start IO 7. Logout of FC Fabric and Delete Source VM Live Migrate Shared Storage
Fibre Channel Tips: Requires Windows Server 2008 and later for the guest OS Verify latest drivers & firmware for FC adapter Verify NPIV is enabled on the FC adapter Verify NPIV is enabled on the FC switch port Note: You may see NPV as a switch option, Hyper-V doesn’t use NPV.
MPIO and MCS Microsoft MPIO (Multipath IO) and MCS (Multiple Connected Sessions) work transparently with Hyper-V Two options for multi-paths with iSCSI Multiple connections per session Microsoft MPIO (multi-pathing input/output) MPIO supported with Fibre Channel, FCoE, iSCSI, SAS
Microsoft Multipath I/O (MPIO) Use more than one path for read and write functions to your storage device Provides redundant failover and load-balancing support for disks or LUNs Supports bandwidth aggregation Distribute I/O transactions across multiple adapters Windows Server feature
Offloaded Data Transfer (ODX) Hyper-V Host Traditional data copy model Server issues read request to SAN Data is read into memory Data is written from memory to SAN Issues Increased CPU & memory utilization Increased storage traffic Inefficient for SAN VHD Stack External Storage Array LUN1 LUN2
Offloaded Data Transfer (ODX) Hyper-V Host Offload-enabled data copy model Server issues offload read request to SAN SAN returns token representing request Server issues write request to san using token SAN completes data copy internally SAN confirms data was copied Reduce maintenance time Merge, mirror, VHD/VHDX creation Increased workload performance VMs are fully ODX-aware and enabled VHD Stack Token Token External Storage Array LUN1 LUN2
Hyper-V ODX Support • Secure Offload data transfer • Fixed VHD/VHDX Creation • Dynamic VHD/VHDX Expansion • VHD/VHDX Merge • Live Storage Migration • Just one example… ~3 Minutes <1 Second!
Storage Spaces Hyper-V Host Inbox storage virtualization solution provides Pooling Resiliency Simple space Mirror space Parity space Thin provisioning Space JBOD
Storage Spaces & Clusters Cluster supports spaces Simple Mirrored Mirrored space CSV redirection from non-owning nodes Use low latency network (10 G or RDMA) for cluster network Clustered Hyper-V Host Hyper-V Host CSV Space Space Shared JBOD SAS
Hyper-V over SMBFile storage for virtualization Hyper-V Cluster Hyper-V Hyper-V Hyper-V Hyper-V Hyper-V Hyper-V Hyper-V Hyper-V Hyper-V What is it? Store Hyper-V files in shares over the SMB 3.0 protocol Include VM configuration, VHD files, snapshots Works with both standalone and clustered servers File storage used as cluster shared storage SQLServer SQLServer SQLServer IIS IIS IIS VDIDesktop VDIDesktop VDIDesktop File Server Cluster File Server File Server Shared Storage
Handling Intermittent Network Failure • Resiliency: • Transparently Re-establishes Network Connection Hyper-V Host 1 Normal Operation X Temporary Disconnect X 3 1 \\FS\Share Connections & Handles Re-established Application Does Not Receive IO Error 3 File Server
Handling Permanent Network Failure • Multichannel: • Transparently Uses Alternate Network Path Hyper-V Host 1 Normal Operation X 3 1 1 X Permanent Disconnect Connections & Handles Failover, Application Does Not Receive IO Error \\FS\Share 3 File Server
Handling File Server Node Failure • Continuous Availability • Transparently Fails Over Share To Different File Server Hyper-V Host 1 Normal Operation 1 3 Failure of File Server, Share Failed Over To New Node X Clustered \\FS\Share \\FS\Share X Connections Re-established, Application Does Not Receive IO Error File Server Node B File Server Node A 3
Handling Hyper-V Node Failure • Cluster Client Failover (CCF) • VMs communicate identity • Enables Quick Recovery Clustered Hyper-V Host A Hyper-V Host B X 1 Normal Operation 1 3 Hyper-V Host Failure, VM Starts On Different Hyper-V Node X \\FS\Share Stale Handles Shot Down, New Handles Opened Without Delay 3 File Server
Host based Backup And Restore • Virtual Shadow Service For SMB • No Change in Flow For Backup Hyper-V Host VSS Service Backup Agent Remote VSS Provider \\FS\S1 \\FS\S1~ Snap File Server Remote VSS Agent VSS Service/ Provider
Hyper-V over SMBFile Storage for Virtualization Highlights Increases flexibility Eases provisioning, management and migration Leverages converged network Reduces CapEx and OpEx Supporting features SMB Transparent Failover - Continuous availability SMB Scale-Out – Active/Active file server clusters SMB Direct (SMB over RDMA) - Low latency, low CPU use SMB Multichannel – Network throughput and failover SMB Encryption - Security VSS for SMB File Shares - Backup and restore SMB PowerShell - Manageability
Windows Server 2012 File Server Disk Deduplication Use for Virtual Disk Library Store more data in less space Redundant copies of segments of VHDs are replaced by a reference to the single copy Compressed and then organized into special container files Enable-DedupVolume Disable-DedupVolume
Deduplication on a Hyper-V Library Before Deduplication: 62.3 GB of disk used After Deduplication: 1.39 GB of disk used 60.9 GB of Savings!