my personal blog about systemcenter

Windows Server 2012 Hyper-V Replica

 

One of the great news features included in the box with Hyper-V and Windows Server 2012 is the ability to replica machines between systems that are only connected though IP , so no requirement for special shared storage

This free feature will be a game changer for many customers where SAN with replication is out of the question or where management will have a disaster recovery site without breaking their budgets

Creating full disaster recovery sites for FREE will be the feature everyone will embrace and ask where its been all their live.

Matthijs from Microsoft made a great post with detailed information about the powershell commands out so far for Hyper-V replica http://blogs.technet.com/b/matthts/archive/2012/04/02/managing-hyper-v-replica-from-powershell.aspx

 

This is done without Virtual Machine Manager integration so even shops wihout systemcenter can do this

 

 

 

image

If you are using a cluster as either the source or target you need to configure a new role from Failover Cluster Manager

 

 

 

image

Create Hyper-V Replica Broker , one is needed pr cluster

image

Give it a fitting name and ip address

image

Configure Replication for the Broker

image

image

For testing we allow connection though http and from all servers

image

Select the virtual machine you want to replicate , right client Replication Enable Replication

image

Select target Hyper-V host or Replica Broker on a different cluster

image

On the target we need to enable replication under Hyper-V manager and set authentication and port , the authentication and port type need to match the source

image

Select a default path for replica machines

 

image

image

Select what VHD files to replicate

image

If storage permits we can keep additional recovery points

 

 

image

image

Verify that initial replicate is complete

image

and to test a planned failover shutdown the machine and select planned failover

image

image

And the planned failover is complete , and the VMM is now running on the different host in the datacenter.

image

If the source and target is on different subnets we can inject a new ip address into the guest as it fails from one host to another keeping services up and running without any steps needed from IT straff

 
Comments

No comments yet.

Leave a Reply

You must be logged in to post a comment.