Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hyper-V 2016 Best Practices

You're reading from   Hyper-V 2016 Best Practices Harness the power of Hyper-V 2016 to build high-performance infrastructures that suit your needs

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781785883392
Length 246 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Benedict Berger Benedict Berger
Author Profile Icon Benedict Berger
Benedict Berger
Romain Serre Romain Serre
Author Profile Icon Romain Serre
Romain Serre
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Accelerating Hyper-V Deployment FREE CHAPTER 2. Deploying Highly Available Hyper-V Clusters 3. Backup and Disaster Recovery 4. Storage Best Practices 5. Network Best Practices 6. Highly Effective Hyper-V Design 7. Hyper-V Performance Tuning 8. Management with System Center and Azure 9. Migration to Hyper-V 2016

Overview of the failover cluster

A Hyper-V Failover Cluster consists of two or more Hyper-V Server compute nodes. Technically, it's possible to use a Failover Cluster with just one computing node; however, it will not provide any availability advantages over a standalone host and is typically only used for migration scenarios.

Note

I don't recommend you to implement a Hyper-V cluster in production without at least three nodes. A single node cluster doesn't ensure high availability. A two-node cluster is not efficient because half of the resources are dedicated to high availability.

A Failover Cluster hosts roles such as Hyper-V virtual machines on its computing nodes. If one node fails due to a hardware problem, it will no longer perform cluster heartbeat communication, even though the service interruption is almost instantly detected. The virtual machines running on that particular node are powered off immediately because of the hardware failure on their computing node. The...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image