HyperV 2012’s Replica service is designed for disaster recovery and given the complexity of what is happening in the background, this is a shockly simple task.  Below are the steps and a lovely video to explain graphically:

  1. Install Hyper-V on two Windows Server 2012 (or 2012 R2) servers
  2. In Hyper-V, click HYPER-V SETTINGS (on the right)
  3. In REPLICA CONFIGURATION,
    1. select ENABLE THIS COMPUTER AS A REPLICATION SERVER
    2. select USE KERBEROS (assuming the servers are on the same Active Directory domain)
    3. select ALL REPLICATION FROM ANY AUTHENTICATED SERVER
    4. Click OK
  4. As per the warning that just poped up, start your WINDOWS FIREWALL WITH ADVANCED SECURITY
    1. select INBOUND RULES
    2. scroll down to the two HYPER-V REPLICA entries
    3. right click and select ENABLE (you really only need the HTTP rule)
  5. Do all of the above on BOTH SERVERS
  6. On the server you want to replicate from:
    1. Open the HYPER-V MANAGER
    2. Right click on the VM in question
    3. Select ENABLE REPLICATION
    4. Type the name of the destination (replica) server
    5. Select ADDITIONAL RECOVERY POINTS and set to whatever you would like (I like 3)
    6. Select REPLICATE INCREMENTAL VSS COPY every… whatever you like (I like 3 hrs)
    7. Accept the defaults to the end
  7. Watch your HYPER-V MANAGER to see what is happenning on both the STATUS column and REPLICATION tab (in the DETAILS pane) and wait for the replication to be complete
  8. In HYPER-V MANAGER, right click on the replica and select REPLICATION then VIEW REPLICATION HEALTH, just for the fun of it!

You have completed the core configuration and below is the FAILOVER details if you want to automate the network config of the replica:

  1. In HYPER-V MANAGER, right click on the replica and select REPLICATION

 

 

 


0 Comments

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *