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

SANs versus Storage Spaces


One of the most crucial decisions in a storage design process for Hyper-V is the question of whether to stick with the traditional SAN model or hop on the wagon of Microsoft's Storage Spaces architecture. Both solutions can do the main job, that is, providing IOPS for VMs without any problems. Having done many projects using both architectures, the following is some real-world guidance I use for storage design.

The first and most important design principle is: do not use nonredundant systems in production for Hyper-V clusters-no single hardware storage node and no single point of failures in your storage design. If you cannot fulfill these requirements, don't plan for HA on Hyper-V. Plan for disaster recovery instead. Uncluster the Hyper-V Servers and replicate the VMs between the nodes in a small setup or between smaller clusters in a bigger environment via Hyper-V Replica. Having said that, let's focus on the decision to make.

Technically, it's possible to use...