Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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

Cluster shared volumes


The most common question on cluster shared volumes is how many CSVs you need and how huge they may get when filled with data. As mentioned before, it's a good rule of thumb to create one CSV per cluster node; in larger environments with more than eight cluster nodes, a CSV per two to four nodes. The number of VMs per-CSV is not limited. Commonly, I do not see more than 50 VMs on a CSV for server VMs and 100 VMs for client VMs in the VDI environment. However, don't think in units here, plan in IOPS. Spread the IOPS evenly between your CSVs. To utilize the redundant storage hardware I wrote about earlier, never use a single CSV. Start with at least two CSVs to spread the load over your two storage controllers. This isn't necessarily a design of CSVs, rather a behavior of the SAN and how it manages its disks. If you use one CSV, it's possible that the SAN allocates ownership of that LUN to a single controller and could introduce a bottleneck in performance. Dividing the...

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