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

Storage Spaces Direct design


If you are looking for a more modern approach than using a hardware storage system, you will find this section interesting. Instead of using a NAS or a SAN, Storage Spaces enables you to deploy a Software-Defined Storage. In this section, two deployment models will be introduced, which leverage Storage Spaces Direct as seen in Chapter 4, Storage Best Practices. These models are called disaggregated and hyperconverged.

Network design

Before introducing each model available with Storage Spaces Direct, let's talk about network. Both solutions require the same network topology. The only difference is the location of the storage-in dedicated nodes or in the compute nodes. However, with both solutions you need the same network addressing plan. You require a management network (nodes deployment, Active Directory, remote session, administration, and so on), a live migration network, a cluster heartbeat network, a storage network, and all the VM networks. Instead of creating...