1. Windows Server 2016
Markus Erlacher
CEO
itnetX AG

2. Bringing the cloud to you
What if you could have the control of the datacenter and the power of the cloud?
Reduced developer chaos and shadow IT
Simplified, abstracted experience
Added consistency to modern development
One portal, one user experience
Write once, deploy anywhere

3. Nano Server

4. Voice of the Customer Reboots impact my business
Why do I have to reboot because of a patch to a component I never use?
When a reboot is required, the systems need to be back in service ASAP
Server images are too big
Large images take a long time to install and configure
Transferring images consumes too much network bandwidth
Storing images requires too much disk space
Infrastructure requires too many resources
If the OS consumes fewer resources, I can increase my VM density
Higher VM density lowers my costs and increases my efficiency & margins

5. I want just the components I need and nothing more

6. Microsoft Server Journey
Windows NT / Windows Server 2003
Windows Server 2008 Windows Server 2008 R2
Windows Server 2012 Windows Server 2012 R2

7. Why we need Nano Server Azure
Patches and reboots interrupt service delivery
(*VERY large # of servers) * (large OS resource consumption)
Provisioning large host images competes for network resources

8. Why we need Nano Server Cloud Platform System (CPS)
Cloud-in-box running on 1-4 racks using System Center & Windows Server
Setup time needs to be shortened
Patches and reboots result in service disruption
Fully loaded CPS would live migrate > 16TB for every host OS patch
Network capacity could have otherwise gone to business uses
Reboots: Compute host ~2 minutes / Storage host ~5 minutes

9. We need server configuration optimized for the cloud

10. Nano Server - Next Step in the Cloud Journey
A new headless, 64-bit only, deployment option for Windows Server
Deep refactoring focused on
CloudOS infrastructure
Born-in-the-cloud applications
Follow the Server Core pattern

11. Nano Server - Roles & Features
Zero-footprint model
Server Roles and Optional Features live outside of Nano Server
Standalone packages that install like applications
Key Roles & Features
Hyper-V, Storage (SoFS), and Clustering
Core CLR, ASP.NET 5 & PaaS
Full Windows Server driver support
Antimalware Built-in
System Center and Apps Insight agents to follow

12. Nano Server in Windows Server 2016
An installation option, like Server Core
Not listed in Setup because image must be customized with drivers
Separate folder on the Windows Server media
Available since the Windows Server Technical Preview 2 released at Ignite

13. Installing Drivers
For the leanest image, install just the drivers your hardware requires
Dism /Add-Driver /driver:<path>
Nano Server includes a package of all drivers in Server Core
Dism /Add-Package /PackagePath:.\packages\Microsoft-NanoServer-OEM-Drivers-Package.cab
To run Nano Server as a VM install
Dism /Add-Package /PackagePath:.\packagesMicrosoft-NanoServer-Guest-Package.cab

14. Deploying Nano Server Generate a VHD from NanoServer.wim
Download Convert-WindowsImage.ps1 from the Script Center:
Run Convert-WindowsImage.ps1 -Sourcepath <path to wim> -VHD <path to new VHD file> –VHDformat VHD -Edition 1.
Dism /Apply-Image

15. Installing Roles and Features
Nano Server folder has a Packages sub-folder
Dism /Add-Package /PackagePath:.\packages\<package>
Dism /Add-Package /PackagePath:.\packages\en-us\<package>

16. Installing Agents and Tools on Nano Server
No MSI support in Nano Server
Current builds of Nano Server require xcopy or custom PowerShell script
Nano Server Installer in the works, which will provide
Install
Uninstall
Inventory
Online and offline installation support

17. Installing Software on Nano Server
No MSI support in Nano Server
Current builds of Nano Server require xcopy or custom PowerShell script
Nano Server Installer in the works, which will provide
Install
Uninstall
Inventory
Online and offline installation support

18. Demo: Nano Server Deployment

19. Hyper-V

20. We are winning virtualization share
Change In Market Share
Over The Past 5+ Years
Microsoft Hyper-V Server
+30.6
% Points
x86 Server Virtualization Share For The Past 5+ Years
Windows Server 2012 Released
Q1 CY2008
Windows Server 2008
Released
Q3 CY2009
Windows Server 2008 R2
Q3 CY2012
Windows Server 2012
Q3 CY2014
CURRENT
Change
Since Hyper-V Released
Microsoft
Hyper-V Server
0.0%
11.8%
25.9%
30.6%
+30.6 Pts
ESX
40.0%
46.6%
51.4%
46.2%
+6.2 Pts
Windows Server 2008 R2 Released
ESX
+6.2
Windows Server 2008 Released
CY Q1
CY 2009 Q3
CY 2012
CY 2014
Source: IDC WW Quarterly Server Virtualization Tracker, December Hyper-V and ESX + vSphere shares based on percent market share among all x86 new hypervisor deployments (nonpaid and paid). x86 hypervisor shipments include those sold on new servers, new nonpaid hypervisor deployments aboard new servers, and new hypervisor sales and nonpaid hypervisor deployments on installed base servers. Share gains for Hyper-V and ESX + vSphere come in part from market share transfers from older products from same vendors.

21. Security

22. Challenges in protecting high-value assets
4/26/2017
Challenges in protecting high-value assets
Any seized or infected host administrators can access guest virtual machines
Fabric
Hypervisor
Customer
Storage
Host OS
Guest VM
Legitimate host?
Impossible to identify legitimate hosts without a hardware based verification
Tenants VMs are exposed to storage and network attacks while unencrypted
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

23. 4/26/2017
Confidently protect sensitive customer data: Designed for ‘zero-trust’ environments
Any seized or infected host administrators can access guest virtual machines
Hardware-rooted technologies to separate the guest operating system from host administrators
Virtual Secure Mode
Process and Memory access protection from the host
Host OS
Customer
Customer
Virtual machine OS
Data
Workload
Compute
Storage
Network
Hypervisor
Fabric
Guest VM
Guest VM
Guarded fabric to identify legitimate hosts and certify them to run shielded tenant Generation 2 VMs
Impossible to identify legitimate hosts without a hardware based verification
Host Guardian Service
Enabler to run Shielded Virtual Machines on a legitimate host in the fabric
Trust the host
Storage
Virtualized trusted platform module (vTPM) support to encrypt virtual machines
Tenants VMs are exposed to storage and network attacks while unencrypted
Shielded VM
Bitlocker enabled VM
Hypervisor
Hypervisor
Fabric
Fabric
Host Guardian Service
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

24. Shielded VMs Spotlight capabilities Storage
4/26/2017
Shielded VMs
Spotlight capabilities
Storage
HOST without TPM (generic host)
Virtual hard disk
HOST with TPM
Shielded Virtual Machines
Shielded Virtual Machines can only run in fabrics that are designated as owners of that virtual machine
Shielded Virtual Machines will need to be encrypted (by BitLocker or other means) in order to ensure that only the designated owners can run this virtual machine
You can convert a running Generation 2 virtual machine into a Shielded Virtual Machine
Host Guardian Service
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

25. Secure Boot Support for Linux
4/26/2017
Secure Boot Support for Linux
Providing kernel code integrity protections for Linux guest operating systems.
Works with:
Ubuntu and later
SUSE Linux Enterprise Server 12
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

26. Secure Boot Support for Linux
4/26/2017
Secure Boot Support for Linux
PowerShell to enable this:
Set-VMFirmware "Ubuntu" -SecureBootTemplate MicrosoftUEFICertificateAuthority
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

27. Resiliency & Availability

28. Storage and Cluster Resiliency

29. Virtual Machine Storage Resiliency
4/26/2017
Virtual Machine Storage Resiliency
Storage fabric outage no longer means that virtual machine crash
Virtual machines pause and resume automatically in response to storage fabric problems
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

30. Virtual Machine Cluster Resiliency
4/26/2017
Virtual Machine Cluster Resiliency
VMs continue to run even when a node falls out of cluster membership
Resiliency to transient failures
Repeat offenders are “quarantined”
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

31. Shared VHDX

32. Improved Shared VDHX Host Based Backup of Shared VHDX
4/26/2017
Improved Shared VDHX
Host Based Backup of Shared VHDX
Online Resize of Shared VHDX
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

33. Replica Support for Hot Add of VHDX
When you add a new virtual hard disk to a virtual machine that is being replicated – it is automatically added to the not-replicated set. This set can be updated online.
Set-VMReplication "VMName" -ReplicatedDisks (Get-VMHardDiskDrive "VMName")

34. Runtime Memory Resize Dynamic memory is great, but more can be done.
For Windows Server 2016 guests, you can now increase and decrease the memory assigned to virtual machines while they are running.

35. Hot add / remove of network adapters
Network adapters can be added and removed from Generation 2 virtual machines while they are running.

36. Servicing & Upgrades

37. Rolling Cluster Upgrade
You can now upgrade a 2012 R2 Hyper-V cluster to Windows Server 2016 with:
No new hardware
No downtime
The ability to roll-back safely if needed

38. New VM Upgrade Process Windows Server 2016:
4/26/2017
New VM Upgrade Process
Windows Server 2016:
Hyper-V will not automatically upgrade virtual machines
Upgrading a virtual machine is a manual operation that is separate from upgrading the host
Individual virtual machines can be moved back to earlier versions, until they have been manually upgraded
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

39. New VM Upgrade Process Windows Server 2016: PowerShell only:
4/26/2017
New VM Upgrade Process
Windows Server 2016:
PowerShell only:
Update-VMConfigurationVersion
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

40. Changing how we handle VM servicing
4/26/2017
Changing how we handle VM servicing
Windows Server 2016:
VM drivers (integration services) updated when needed
Require latest available VM drivers for that guest operating system
Drivers delivered directly to the guest operating system via Windows Update
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

41. Scale Improvements

42. Evolving Hyper-V Backup
New architecture to improve reliability, scale and performance.
Decoupling backing up virtual machines from backing up the underlying storage.
No longer dependent on hardware snapshots for core backup functionality, but still able to take advantage of hardware capabilities when they are present.

43. Built in change tracking for Backup
Most Hyper-V backup solutions today implement kernel level file system filters in order to gain efficiency.
Makes it hard for backup partners to update to newer versions of Windows
Increases the complexity of Hyper-V deployments
Efficient change tracking for backup is now part of the platform

44. VM Configuration Changes
New virtual machine configuration file
Binary format for efficient performance at scale
Resilient logging for changes
New file extensions
.VMCX and .VMRS

45. Operations

46. Production Checkpoints
Delivers the same Checkpoint experience that you had in Windows Server 2012 R2 – but now fully supported for Production Environments
Uses VSS instead of Saved State to create checkpoint
Restoring a checkpoint is just like restoring a system backup

47. PowerShell Direct to Guest OS
You can now script PowerShell in the Guest OS directly from the Host OS
No need to configure PowerShell Remoting
Or even have network connectivity
Still need to have guest credentials

48. Network Adapter Identification
You can name individual network adapters in the virtual machine settings – and see the same name inside the guest operating system.
PowerShell in host:
PowerShell in guest:
Add-VMNetworkAdapter -VMName “TestVM" -SwitchName "Virtual Switch" -Name "Fred" -Passthru |
Set-VMNetworkAdapter -DeviceNaming on
Get-NetAdapterAdvancedProperty | ?{$_.DisplayName -eq "Hyper-V Network Adapter Name"} | select Name, DisplayValue

49. ReFS Accelerated VHDX Operations
Taking advantage of an intelligent file system for:
Instant fixed disk creation
Instant disk merge operations

50. Isolation

51. Distributed Storage QoS
Windows Server 2016:
Leveraging Scale Out File Server to allow you to:
Define IOPs reserves for important virtual hard disks
Define a IOPs reserve and limit that is shared by a group of virtual machines / virtual hard disks

52. Host Resource Protection
Dynamically identify virtual machines that are not “playing well” and reduce their resource allocation.

53. Networking

54. Software Defined Networking
Bringing Software Defined Networking to the next level
VXLAN and NVGRE support
Virtual Firewall
Software Load Balancer
Improved Gateways
RDMA using vNICs
And much much more…

55. One more thing….

56. Containers

57. What are Containers
LXC (Linux Containers) is an operating-system-level virtualization environment for running multiple isolated Linux systems (containers) on a single Linux control host. Containers provide operating system-level virtualization through a virtual environment that has its own process and network space, instead of creating a full-fledged virtual machine.

58. Bare-Metal Image Physical Host Operating System Microsoft Ignite 2015
4/26/ :27 AM
Bare-Metal
Operating
System
Image
Physical Host
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

59. Hardware Virtualization
Microsoft Ignite 2015
4/26/ :27 AM
Virtual Machines
Operating
System
Operating
System
Image
Virtual
machine(s)
Hardware Virtualization
Operating System
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

60. Hardware Virtualization
Microsoft Ignite 2015
4/26/ :27 AM
Container Run-time
Operating System
Container(s)
Hardware Virtualization
Operating System
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

61. Container Ecosystem Container Run-Time Container Images
Microsoft Ignite 2015
4/26/ :27 AM
Container Ecosystem
Container Run-Time
Linux
Container Images
Image Repository
Applications
Application
Frameworks
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

62. Containers Windows Server Hyper-V Container(s) Container(s) Hyper-V
Microsoft Ignite 2015
4/26/ :27 AM
Containers
Hyper-V
Container(s)
Windows Server
Container(s)
Hyper-V
Virtual Machine(s)
Hyper-V Hypervisor
Physical Machine
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

63. Deploying Containers Hyper-V Container(s) Requires Hyper-V Hypervisor
Microsoft Ignite 2015
4/26/ :27 AM
Deploying Containers
Hyper-V
Container(s)
Requires Hyper-V Hypervisor
Windows Server
Container(s)
Hyper-V
Virtual Machine(s)
Hyper-V Hypervisor
Physical Machine
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

64. Deploying Containers Hyper-V Windows Server Container(s) Container(s)
Microsoft Ignite 2015
4/26/ :27 AM
Deploying Containers
Hyper-V
Container(s)
Windows Server
Container(s)
Virtual Machines
Physical Machine
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

65. Deploying Containers Hyper-V Container(s) Requires Hyper-V Hypervisor
Microsoft Ignite 2015
4/26/ :27 AM
Deploying Containers
Hyper-V Container(s)
Requires Hyper-V
Hypervisor
Windows Server
Container(s)
Hyper-V Hypervisor
Virtual Machines
Physical Machine
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

66. Demo: Containers

67. Software Defined Storage The (v)Next Level

68. Current SDS with Server 2012 R2 (1 / 2)
Scale-Out File Server
Access point for Hyper-V
Scale-out data access
Data access resiliency
Cluster Shared Volumes
Single consistent namespace
Fast failover
Storage Spaces
Storage pooling
Virtual disks
Data Resiliency
Hardware
- Standard volume hardware
- Fast and efficient networking
- Shared storage enclosures
SAS SSD
SAS HDD
SMB3.x
Scale-Out File Server \\FileServer\Share
Cluster Shared Volumes C:\ClusterStorage
Storage Space Virtual Disks
Software Defined Storage System
Storage Pool
Storage Node
Shared JBOD Storage

69. Current SDS with Server 2012 R2 (2 / 2)
Tiered Spaces leverage file system intelligence
File system measures data activity at sub-file granularity
Heat follows files
Admin-controlled file pinning is possible
Data movement
Automated promotion of hot data to SSD tier
Configurable scheduled task
Write-Back Cache (WBC)
Helps smooth effects of write bursts
Uses a small amount of SSD capacity
IO to SSD bypass WBC
Large IO bypass WBC
Complementary
Together, WBC and the SSD tier address data’s short-term and long-term performance needs
Storage Space
HDD Tier
Cold Data
SSD Tier and WBC
Hot Data
SAS SSD
SAS HDD
I/O Activity Accumulates Heat at Sub-File Granularity
Hyper-V Nodes

70. What we hear from customers…..

71. I can’t implement a Microsoft Storage Solution because…
“Replication on Storage-Level is missing”
“I wanna do Hyper-Converged”
“I don’t trust Microsoft doing Storage”

72. Storage Spaces Direct

73. Storage Spaces Direct at a glance
Non-Shared Storage (inbox or local attached)
Distributed via new Software Storage Bus
Enables easy scale out
Leverages all the benefits of SMB3.x / RDMA

74. Storage Spaces Direct logical View
Cloud design points and management
Standard servers with local storage
New device types such as SATA and NVMe SSD
Deploy/manage/monitor with SCVMM, SCOM & PowerShell
Reliability, scalability, flexibility
Fault tolerance to disk, enclosure, node failures
Scale pools to large number of drives
Simple and fine grained expansion
Use cases
Hyper-V IaaS storage
Storage for backup and replication targets
Hyper-converged (compute and storage together)
Converged (compute and storage separate)

75. Scenarios Hyper-converged Converged (Disaggregated)
- Compute and Storage resources together
- Compute and Storage scale and are managed together
- Typically small to medium sized scale-out deployments
- Compute and Storage resources separate
- Compute and Storage scale and are managed independently
- Typically larger scale-out deployments
HYPER-V CLUSTER
HYPER-V CLUSTER(S)
SMB3 STORAGE NETWORK FABRIC
SCALE-OUT FILE SERVER CLUSTER

76. Software Storage Bus Cache
Cache scoped to local machine
Read and Write cache (see table below)
Automatic configuration when enabling S2D
Special partition on each caching device
Leaves 32GB for pool and virtual disks metadata
Round robin binding of SSD to HDD
Storage Configuration
Caching devices
Capacity devices
Caching behavior
SATA SSD + SATA HDD
All SATA SSD
All SATA HDD
Read + Write
NVMe SSD + SATA HDD
All NVMe SSD
NVMe SSD + SATA SSD
Write only
SATA
SSD
SATA
SSD
Caching Devices
SATA
HDD
SATA
HDD
Capacity Devices

77. Cluster Shared Volumes File System (CSVFS)
Software Storage Bus
Virtual storage bus spanning all nodes
Clusport: Initiator (virtual HBA)
ClusBlft: Target (virtual disk / enclosures)
SMB3/SMB Direct transport
Intelligent I/O Management
Prioritizing(App vs System)
De-randomization of random IO
Drives sequential IO pattern on rotational media
Node 1
Node 2
Application
Cluster Shared Volumes File System (CSVFS)
File System
File System
Virtual Disks
Virtual Disks
SpacePort
SpacePort
Block over SMB
ClusPort
ClusPort
ClusBflt
ClusBflt
Physical Devices
Physical Devices

78. Storage Spaces Direct: Requirements
4 up to 16 Storage Nodes
10 Gbps RDMA
Min. 2 SSD / 1 NMVe per Node (Cache / Journal)
Min. 4 SSD / HDD per Node (capacity)
Supported HW Model (VMs for LAB)

79. Storage Spaces Direct Development Partners
Microsoft Ignite 2015
4/26/ :27 AM
Storage Spaces Direct Development Partners
Cisco UCS C3160 Rack Server
Dell PowerEdge R730xd
Fujitsu Primergy RX2540 M1
HP Apollo 2000 System
Intel® Server Board S2600WT-Based Systems
Lenovo System x3650 M5
Quanta D51PH
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

80. Demo Storage Spaces Direct

81. Storage Replica

82. SR is used for DR preparation

83. Storage Replica at a glance
Volume based block-level storage replication
synchronous or asynchronous
HW agnostic (any type of source / destination volume)
SMB3 as transport protocol
Leverages RDMA / SMB3 Encryption Multichanneling
I/Os pre-aggregated prior to transfer
Managed via Powershell, cluadmin, ASR

84. Storage Replica Layer Source Destination SMB server
File system filters
CSVFS/NTFS/ReFS
VolSnap filter
BitLocker Filter
Volume Manager
Storage Replica
Storage Replica
Partition manager
Partition manager
Disk driver
Disk driver
Disk
Disk

85. SR: Streched Cluster Single Cluster, spanning DCs Asymmetric Storage
Datacenter A
Datacenter B
Single Cluster, spanning DCs
Asymmetric Storage
Automatic Failover
Synchronous only
Streched Cluster

86. SR: Cluster to Cluster Multiple Cluster Manual Failover
Datacenter A
Datacenter B
Multiple Cluster
Manual Failover
Synchronous or Asynchronous
Cluster A
Cluster B

87. SR: Server to Server To separate Servers Manual Failover
Datacenter A
Datacenter B
To separate Servers
Manual Failover
Synchronous or Asynchronous
Server A
Server B

88. Synchronous workflow Applications (local or remote) Source Server1 5 2
Source Server
Node (SR)
Destination Server
Node (SR) 4 t 2 t1 3
Data
Log
Data
Log

89. Asynchronous workflow
Applications
(local or remote) 1 3 4
Source Server
Node (SR)
Destination Server
Node (SR) 6 t 2 t1 5
Data
Log
Data
Log
The async difference is the IO completes on the source before travelling to the destination

90. Storage Replica: Requirements
Any volume (SAS, SAN, iSCSI, Local)
<5 ms round trip between sites for synchron mirror
RDMA
Identical size for source / target volume
SSDs for log disks recommended (min. 8GB size)
Identical physical disk geometry (phys. sector size)
Turn on SR write ordering for distributed app data

91. Demo Storage Replica

92. ReFS (Resilient File System)

93. ReFS - Data Integrity Metadata Checksums
Checksums protect all filesystem metadata
User Data Checksums
Optional checksums protect file data
Checksum Verification
Occurs on every read of checksum-protected data
During periodic background scrubbing
Healing of Detected Corruption
Healing occurs as soon as corruption is detected
Healthy version retrieved from Spaces’ alternate versions (i.e. mirrors or parity data), if available
ReFS uses the healthy version to automatically have Storage Spaces repair the corruption
Storage Spaces 3-way mirror with ReFS
Disk 1
Disk 2
Disk 3
Checksums verified on reads
On checksum mismatch, mirrors are consulted
Good copies used to heal bad mirror

94. ReFS - Resiliency and Availability
ReFS designed to stay online and keep your data accessible when all else fails
Even when corruptions cannot be healed via Storage Spaces’ resiliency (mirror- and parity-generated data versions)
Online Repair
CHKDSK-Like repairs performed without taking the volume offline
No downtime due to repair operations!
On-Volume Backups of Critical Metadata
Backups of critical metadata are automatically maintained on the volume
Online repair process consults backups if checksum-based repair fails
Provides additional protection for volume-critical metadata, in addition that provided by mirror and parity spaces

95. ReFS - Speed and Efficiency
Efficient VM Checkpoints and Backup
VHD(X) checkpoints cleaned up without physical data copies
Data migrated between parent and child VHD(X) files as a ReFS metadata operation
Reduction of I/O to disk
Increased speed
Reduces impact of checkpoint clean-up to foreground workloads
Accelerated Fixed VHD(X) Creation
Fixed VHD(X) files zeroed with just a metadata operation
Impact of zeroing I/O to foreground workloads eliminated
Decreases VM deployment time
Quick Dynamic VHD(X) Expansion
Dynamic VHD(X) files zeroed with a metadata operation
Impact of zeroing I/O for expanded regions eliminated
Reduces latency spike for foreground workloads
Hyper-V Checkpoint Merging
Virtual Hard Disk
Parent VHDX File
VHDX File
Merged VHDX
Stable Point-In-Time
Child VHDX File
Incoming Writes
Hyper-V VHDX Creation / Extension
VHDX on NTFS
VHDX on ReFS

96. Storage QoS

97. Distributed Storage QoS
Mitigate noisy neighbor issues
Monitor end to end storage performance
Deploy at high density with confidence

98. Storage Quality of Service (QoS)
Control and monitor storage performance
Simple out of box behavior
Enabled by default for Scale Out File Server
Automatic metrics per VHD, VM, Host, Volume
Includes normalized IOPs and latency
VIRTUAL MACHINES
HYPER-V CLUSTER
Flexible and customizable policies
Policy per VHD, VM, service, or tenant
Define minimum and maximum IOPs
Fair distribution within policy
Rate Limiter
Management
System Center VMM and Ops Manager
PowerShell built-in for Hyper-V and SoFS
SCALE OUT FILE SERVER SERVER CLUSTER
IO Scheduler
Policy Manager

99. Storage QoS Policy Types
Single Instance
VIRTUAL MACHINES
VIRTUAL MACHINES

100. Thank you!