Best Practices for Deploying Disaster Recovery Services with Microsoft Azure Site Recovery
Description
Windows Server vNext allows you to centrally monitor and manage performance for Hyper-V workloads using Scale-Out File Servers. Learn how to monitor storage performance from a customer, Hyper-V, and storage admin’s viewpoint, then author effective policies to deliver the performance your customers need.
Share
Download
Download this episode
- High Quality MP4 (0.0 B)
- Low Quality MP4 (0.0 B)
More episodes in this series
Taking a Deep Dive into Microsoft Azure IaaS Capabilities
Related episodes
MS-HVRS: HyperV SMB3 Protocol Requirements
Microsoft's Storage Strategy & Capabilities in Datacenter vNext
Platform Vision & Strategy (4 of 7): Storage Overview
Server Based File Storage
Software-Defined Storage in Windows Server 2012 R2 and Microsoft System Center 2012 R2
File Server Networking for a Private Cloud Storage Infrastructure in Windows Server 2012 R2
Upgrading Your Private Cloud with Windows Server 2012 R2
Storage and Availability Improvements in Windows Server 2012 R2
HyperV Server over SMB3
Application Availability Strategies for the Private Cloud
The Discussion
-
JoseBarreto As promised, I recorded the demos for this session, without the issues we had during the talk. Here are those links:
- Windows Server 2012 R2 Storage QoS.
- Windows Server 2016 TP2 Storage QoS: PowerShell Monitoring.
- Windows Server 2016 TP2 Storage QoS: Managing policies with VMM.
- Windows Server 2016 TP2 Storage QoS: Managing Policies with PowerShell.
- Windows Server 2016 TP2 Storage QoS: Managing with a PowerShell script.
The script used in the demo can be found at:
More links about Windows Server 2016 TP2 Storage QoS at:
-
Aaron Patten Will the slide deck from this presentation be posted?