Windows Server 2012 Configure / Deploy Hyper-v Replica Broker How To #TEE13 #MSteched   12 comments

Windows Server 2012 Hyper-V Role introduces a new capability, Hyper-V Replica, as a built-in replication mechanism at a virtual machine (VM) level. Hyper-V Replica can asynchronously replicate a selected VM running at a primary site to a designated replica site across LAN/WAN

there is a great guide for you LAB on this site http://blogs.technet.com/b/yungchou/archive/2013/03/24/hyper-v-replica-broker-explained.aspx

Hyper-V Replica Cluster

To Deploy a Hyper-v failover cluster as a replica site, must use Failover Cluster Manager to perform all Hyper-V Replica configurations and management. And first create a Hyper-V Replica Broker role.

In this case I have two clusters left and right. first go to the FCM and add a role

image image

A Hyper-V Replica Broker is the focal point in this case. It queries the associated cluster database to realize which node is the correct one to redirect VM specific events such as Live Migration requests in a replica cluster.

Windows Active Directory domain is not a requirement for Hyper-V Replica which can also be implemented between workgroups and untrusted domains with a certificate-based authentication. Active Directory is however a requirement if involving a Hyper-v host which is part of a failover cluster, and in such case all Hyper-V hosts of a failover cluster must be in the same Active Directory domain with security enforced at the cluster level. I see sometimes that the broker creations is failing. The resource will not come online.

imageimage So During the creation of the cluster resource you will need a Name ( netbios ) and a IP. that is all.  But remember as all cluster resources the cluster will create the items and not you Mister Admin. Just make sure Your DNS and cluster resource can create Items.

If you are not sure about this check my old blog post https://robertsmit.wordpress.com/2012/06/26/cluster-network-name-resource-failed-to-create-its-associated-computer-object-in-domain/

Now that my Resource is created and it is in my cluster In both Cluster I want to do Cross Replication Winking smile

If you know Hyper-v then you would do the settings in the hyper-v settings but as you can see all the options are grayed out.

image   image

Go to the Cluster manager and right click on the broker select replication settings.

image Same menu and configurable.

First enable the replica server in the first case I use Kerberos ( the easy one )

So don’t check the certificate based box.

image 

here you can do give any server access to this replica easy to do and quick just fill in the path where the VM files need to be stored.

the other option is give only server that I want access. Well in my case I also used a * not that smart well now Only server in my domain can replicate and not every server. If you want to do a point to point connection just fill in the FQDN of the server.

once you have filled in the entry you can’t change the name only the storage path. Well that is fine for now.

image

image image

Again we add the Resource this time a Virtual machine. Just make sure there is a VM in the Hyper-v

What we do here is make the VM high available and yes you could also replicate the VM right from the Hyper-v console.

image but that does not make the VM High Available.

 

image

Selecting the VM image Now we can start the machine and the VM is HA

image

We have the broker in place and a VM it is time to replicate.

imageimage

Don’t use the broker on the current cluster you can’t replicate to your own cluster Smile

image All you have to know is the name of your cluster where the VM is placed

So I use the name of the cluster and see if it works, The wizard does see that there is a other broker in the left01 cluster and ask me to change that YES click on update

imageimage again Here can I choose Kerberos or certificate Rememeber I checked both boxes on the broker cluster resource If I made a choice there I could no choose here.

I go for……Kerberos

image Check what VM disk are needed to replicate If you have a disk that holds stuff that si not needed for replications then unselect the disk here.

 image image

You can create multiple recovery points or just one and change the time currently you can set this from 1 hour to 12 hours.  It is a wish to get this sooner.

and how to copy the stuff , over the network or with media. and the time to start.

I take the right now option

 

image image

imageimage

imageimage

and If you want to change the settings just go to the settings of the VM and change it

image

 

In the Cluster or in the Hyper-v console you can see the status easy quick and fast replication.

In my next blog post I will do the same with a Certificate and you need extra steps for this.

image

Advertisements

Posted June 12, 2013 by Robert Smit [MVP] in Hyper-V, Windows Server 2012

Tagged with ,

12 responses to “Windows Server 2012 Configure / Deploy Hyper-v Replica Broker How To #TEE13 #MSteched

Subscribe to comments with RSS.

  1. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #33 - TechCenter - Blog - TechCenter – Dell Community

  2. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #33 - Dell TechCenter - TechCenter - Dell Community

  3. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #33 | ServerGround.net

  4. Excellent article. I am dealing with some of these issues as well.
    .

  5. Can we have the hyper-V cluster in the productive site and a hyper-v host in replica site?

  6. Hi, I just wanna enable vm replication from Hyper-V host to failover cluster, but failed. replica broker(named ‘replica’) is install in the cluster, and I can config replication from Hyper-V host manager(THE UI), but when I invoke the following command, it failed with object not found. Can you help me?

    On the hyper-v host, to replica broker:

    PS D:\> Enable-VMReplication -VMName cirros -ReplicaServerName replica -ReplicaServerPort 80 -AuthenticationType Kerberos
    Enable-VMReplication : 由于找不到某个对象,Hyper-V 尝试在计算机“replica”上访问该对象时遇到错误。请验证该计算机上的虚拟机管理服务是否正在运行。
    所在位置 行:1 字符: 1
    + Enable-VMReplication -VMName cirros -ReplicaServerName replica.gcides …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (:) [Enable-VMReplication], VirtualizationException
    + FullyQualifiedErrorId : ObjectNotFound,Microsoft.HyperV.PowerShell.Commands.EnableVMReplication

    Best Regards
    Andes.

  7. Hi, I have a question. You said “Don’t use the broker on the current cluster you can’t replicate to your own cluster” and I imagine current cluster would be the one configured on production site? What if I want to failback, if I dont have replica broker at my production site, I will not be able to replicate changes made during VM working at DR site and I would have a big loss of data. Is this correct or am I missing something? Thank you in advance for Your answer.

    • Hi Thanks for reading my blog. Well what I meant is then selecting the replica you should not select your own cluster instead of the replica. You always can replicate back. it is just the selecting order. on the source select the replica.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

  • Twitter

  • %d bloggers like this: