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

NIC Teaming


Before Windows Server 2012, the teaming of NICs was a part of the NIC-driver but not of the operating system. This policy led to regular support cases with problematic implementations; therefore, the present NIC Teaming is done on the operating system level.

NIC Teaming in Windows Server 2016 allows us to span a team over NICs from different vendors and of different bandwidths with classic Load Balancing and Failover (LBFO) capabilities. However, it's best practice to have only active interfaces with equal bandwidth active in one team. Creating a NIC Team will create a logical network object, a team NIC (tNIC), that is then connected to our created Hyper-V vSwitch.

It's possible to create additional tNICs on an existing team without using vSwitches. However, this option lacks the ability of QoS and should be avoided.

There are different Teaming modes available in Windows Server 2012 R2. They are as follows:

  • Switch independent: This should be your default option for newly created...