Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hyper-V 2016 Best Practices

You're reading from   Hyper-V 2016 Best Practices Harness the power of Hyper-V 2016 to build high-performance infrastructures that suit your needs

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781785883392
Length 246 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Benedict Berger Benedict Berger
Author Profile Icon Benedict Berger
Benedict Berger
Romain Serre Romain Serre
Author Profile Icon Romain Serre
Romain Serre
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Accelerating Hyper-V Deployment FREE CHAPTER 2. Deploying Highly Available Hyper-V Clusters 3. Backup and Disaster Recovery 4. Storage Best Practices 5. Network Best Practices 6. Highly Effective Hyper-V Design 7. Hyper-V Performance Tuning 8. Management with System Center and Azure 9. Migration to Hyper-V 2016

Storage Spaces and tiering


A way to leverage SOFS is to use Storage Spaces with storage tiering. Having some shared JBODs with SSDs and HDDs connected to your SMB3 file servers enables great I/O performance. Frequently read data will be cached on the SSDs and long-term data will be archived on the HDDs by default, without the need for manual editing, which results in a great performance boost. Using the previously explained CSV, a cache can further improve read performance.

With Windows Server 2016, Storage Spaces using shared JBOD should be considered when you already have the hardware (file servers and shared JBOD). If you don't want to invest money in storage because you already have hardware, Storage Spaces with shared JBOD is the way to go. If you plan to buy new hardware, I suggest that you use Storage Spaces Direct which does not require shared JBOD. Shared JBODs are not flexible because they have a limited number of SAS ports. So, the number of file servers is limited by the number...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image