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

Hyper-V Replica


The core feature of Hyper-V disaster recovery technologies is Hyper-V Replica, the ability to replicate a virtual machine in near real time to another Hyper-V host. On the second host, an offline copy of the virtual machine is created and updated every 30 seconds or alternatively, every few minutes, with changed blocks from the running source-VM. Both physical machines host nearly identical copies of the same virtual machine with the same name, the same IP address, and the same content. Optional VSS consistency provides additional data integrity throughout the replication process. The replicated VM is offline until a disaster takes place and the VM will be powered up (manually) when it's needed. Both hosts don't have to use identical hardware, storage systems, or Active Directory domains. Instead of restoring up to 24-hour-old data from your backup, the maximum data loss in this scenario is only a few minutes of data.

In the case of a broken SAN, you will decrease the time...