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 network


If you are using Fibre Channel Infrastructure for storage communication, you don't need additional considerations to integrate this communication into your converged network. However, if you are using the iSCSI communication, it's highly recommended that you use another network for storage communication. The iSCSI communication uses MPIO for resiliency instead of network teaming. There is just one upcoming scenario where iSCSI over teamed interfaces is possible, in all the major scenarios teaming iSCSI communication is not supported. Refer to http://bit.ly/1mVYDyq for more details.

It's best practice to separate the iSCSI communication from other traffic on a host level, so use two dedicated network cards on the host. Don't add them to a team, instead use the MPIO feature for resiliency.

If you are using SMB3 communication for your storage, use Switch Embedded Teaming to converge this kind of traffic if your network adapters support RDMA. To give the priority to SMB3 flow over...