Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd like to use Hyper-v replication on Windows Server 2012.

My client will be Windows 2008 R2, I'd like to know if there are some limitations or if it is totally independant from the operating system ? For example, some configuration are missing like the IP configuration.

And can you confirm that process is totally safe ? In particular some open source database.

share|improve this question

closed as not constructive by joeqwerty, Khaled, mgorven, mdpc, Mathias R. Jessen Mar 10 '13 at 21:31

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 3 down vote accepted

I really see two key questions here so I will address them separately.

Q1: Do you have to be running a specific Operating System in the Guest VM to create a Replica of that VM in Server 2012 Hyper-V?

A1: Hyper-V Replica is a function of Hyper-V in Windows Server 2012. You can create a replica of any VM regardless of the Guest OS running in the VM.

Q2: For the Hyper-V Replica IP Injection to work when failing over to the replica, are there any requirements for the Guest OS? Just to be sure, I'm referring to the setting in the following screenshot. Hyper-V VM Settings - Failover TCP/IP

A2: For this feature, there are some requirements for the VM configuration and Guest OS.

  1. You must have the latest integration services installed for the VM.
  2. You have to use Synthetic network adapters (Won't work for Legacy network adapter).
  3. At this time, this feature is available for Supported Windows Guest OS's only.

To be clear, Windows Server 2008 R2 is indeed one of the supported Guest OS's so you should have no problem using this feature.

* EDIT - New Information *

I am including a screenshot that shows the difference between a Legacy Network Adapater and a Network Adapter (referred to as Synthetic network adapter in my original answer). When adding hardware, you can choose to add in a Legacy or "normal" adapter. If you look on the left side of the settings pane, you can see how both show up. I hope this helps.

Network Adapter

share|improve this answer
Harold, on the windows 2008 R2 I have a network card "bus network card for hyper-v" (translated from french, so it may be a bad translation). Can you confirm that I have the synthetic network adapter ? – P. Sohm Mar 8 '13 at 16:02
P. Sohm, I updated the answer to include a screenshot at the bottom of the original answer to show the difference between Legacy and non Legacy network adapters in my English version. – Harold Wong Mar 8 '13 at 16:17

Not the answer you're looking for? Browse other questions tagged or ask your own question.