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

Protecting a Hyper-V environment


Preparing for a situation that hopefully never takes place; this is a definition of the process of backup and disaster recovery. While restoring a lost Word document on a file server is a common and well-practiced task occurring daily in most IT environments, the complete loss of a bunch of VMs or even a whole Hyper-V cluster is unlikely to occur; or so you may think. Almost all companies make use of redundant components, and even clusters are standard; however, single points of failures (SPOFs) can often be found. The following are a few examples:

  • Non-mirrored storage systems

  • Core switches

  • Intersite networking

  • Authentication systems

So, a typical technical architecture offers a realistic chance for a disaster to occur. Hardware and software issues aren't number 1 in a list of possible disaster scenarios. More than 50 percent of all disastrous issues are triggered by a human error according to the backup-focused company Acronis. Deleting the wrong VM, provisioning...