Book Image

Hyper-V 2016 Best Practices

By : Romain Serre, Benedict Berger
Book Image

Hyper-V 2016 Best Practices

By: Romain Serre, Benedict Berger

Overview of this book

Hyper-V Server and Windows Server 2016 with Hyper-V provide best-in-class virtualization capabilities. Hyper-V is a Windows-based, very cost-effective virtualization solution with easy-to-use and well-known administrative consoles. This book will assist you in designing, implementing, and managing highly effective and highly available Hyper-V infrastructures. With an example-oriented approach, this book covers all the different tips and suggestions to configure Hyper-V and provides readers with real-world proven solutions. This book begins by deploying single clusters of High Availability Hyper-V systems including the new Nano Server. This is followed by steps to configure the Hyper-V infrastructure components such as storage and network. It also touches on necessary processes such as backup and disaster recovery for optimal configuration. The book does not only show you what to do and how to plan the different scenarios, but it also provides in-depth configuration options. These scalable and automated configurations are then optimized via performance tuning and central management ensuring your applications are always the best they can be.
Table of Contents (15 chapters)
Hyper-V 2016 Best Practices
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface

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...