Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Windows Server 2016 Hyper-V Cookbook - Second Edition

You're reading from  Windows Server 2016 Hyper-V Cookbook - Second Edition

Product type Book
Published in Jan 2017
Publisher Packt
ISBN-13 9781785884313
Pages 524 pages
Edition 2nd Edition
Languages
Concepts
Authors (3):
Charbel Nemnom Charbel Nemnom
Profile icon Charbel Nemnom
Patrick Lownds Patrick Lownds
Profile icon Patrick Lownds
Leandro Carvalho Leandro Carvalho
Profile icon Leandro Carvalho
View More author details
Toc

Table of Contents (19) Chapters close

Windows Server 2016 Hyper-V Cookbook - Second Edition
Credits
About the Authors
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface
1. Installing and Managing Hyper-V in Full, Server Core, and Nano Server 2. Migrating and Upgrading Physical and Virtual Servers 3. Managing Disk and Network Settings 4. Saving Time and Cost with Hyper-V Automation 5. Hyper-V Best Practices, Tips, and Tricks 6. Security and Delegation of Control 7. Configuring High Availability in Hyper-V 8. Disaster Recovery for Hyper-V 9. Azure Site Recovery and Azure Backup for Hyper-V 10. Monitoring, Tuning, and Troubleshooting Hyper-V Hyper-V Architecture and Components Index

Configuring Hyper-V Replica Broker for a Failover Cluster


If you have either the primary, replica or extended replica server as a member of a Failover Cluster environment, you will need to configure the Hyper-V Replica Broker role. This role is necessary to enable a cluster to be part of a Hyper-V Replica so that it can support seamless replication. In this scenario, you can have a standalone server and a cluster working as primary or replica server, or a cluster for each.

When configuring a Hyper-V Replica for a virtual machine, a different virtual name called Client Access Point (CAP) must be used. The CAP is created during the Hyper-V Replica Broker configuration.

In this recipe, you will see how to configure Hyper-V Replica Broker to use your cluster servers in the Hyper-V Replica scenario.

Getting ready

You will need a Failover Cluster environment already configured with a cluster created as well. For more information on how to install and configure it, have a look at the Installing and...

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 $15.99/month. Cancel anytime}