Hyper V on windows 2012 standard

Hi,

Old Scenario,  We have a physical DC, a virtual DC, a physical App server, and a physical FTP server.
We bought  2 new identical Servers with windows 2012.  Idea is to turn on HYper V and p2v the physical to virtual.    However, I want to provide redundancy incase one of the servers go down.   What's the best approach here?
seven45Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
There are several approaches. You could use Hyper-V replica if you can tolerate some downtime and a small window of data loss. Some workloads should not be replicated (like DCs) and you'd instead just run a separate DC on each physical server. If one went down, the DC on the other would remain running. Exchange and SQL are also examples of roles where you'd architect another solution instead of Hyper-V Replica. And finally, if you have a LOB app where you cannot tolerate some data loss and need very high availability, setting up a failover cluster would be the way to go. SQL supports failover clustering, and Exchange's DAG setup is also built on a variant of the failover cluster. But these solutions are more expensive in both licensing and hardware requirements such as shared storage.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Svet PaperovIT ManagerCommented:
You will have to add both Hyper-V servers into the domain in order to use the replication. In that case, make sure that you have at least one DC on different hardware.

Note that, if you using the same Windows Server license for physical as well for virtual machines, you cannot add DC role on the same hardware where the Hyper-V role is added.
0
seven45Author Commented:
Hi,

Thanks for the tips.

Luckily we don't have to worry about exchange and/or a full sql server.  we have an app server that uses sql express, an ftp server on windows 2003.  other than that---just the AD roles.   I was trying to get redundancy without having to go with expensive solutions.   Would you mind elaborating on the hyper-v replica?

From what you mentioned, I assume I can install a DC on each of the physical hosts, then p2v the ftp and the app server to one server and configure a replica on the other server so its in standby?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Cliff GaliherCommented:
That's the basic idea. There are several tutorials out there for Hyper-V Replica and it is free in 2012 and 2012 R2. Just bing/google "Hyper-V Replica" or "technet Hyper-V Replica" to get the technet articles (which I consider trustworthy and thorough enough) and other blog posts by people that have set them up (not necessarily trustworthy, but often more detailed.)  Plus the newest Hyper-V books cover the topic in great detail. Amazon has several Hyper-V 2012 books and, when purchased from a reputable publisher, are often quite trustworthy and are usually more detailed than technet...best of both worlds, but at the cost of a book.
0
seven45Author Commented:
Thanks---i'll look up the details on Hyper-V replica.  Do I need to worry about licensing if I 1: p2v existing windows 2003 to the 2012?   or 2: if I create a new virtual server with 2012 on it and upgrade the ftp and/or app to the 2012?
0
Cliff GaliherCommented:
Well, of course you always have to consider licensing. And you don't "p2v from 2003 to 2012" ...a p2v, by definition, converts a physical install to a virtual install. It is the same OS, same apps, same software, same profiles. If you want to upgrade from 2003 to 2012, that'll be a step independent of your p2v. And if you are upgradiong, p2v may not even make sense since a more traditional migration may be faster and less error prone. There is a lot of planning involved in that process and without a lot more detail, I couldn't possibly cover all the permutations through EE.
0
seven45Author Commented:
Thanks---I actually meant p2v as option 1 where I keep everything the same till next year until support for 2003 expires.    or think about option 2--traditional migration.   I should have been more precise.      My question would be on option 2, I believe I have the option of having 2 VM's per license of 2012  (not including the physical host)---so if I use the physical host as a DC, then I only have 1 more license to use for a virtual machine.      I was just trying to confirm that i'm on the right path.
0
Svet PaperovIT ManagerCommented:
No, if you use the physical host as a DC you don’t have virtual licences – it’s either one physical or two virtual machines.

Moreover, it is not recommended to add additional roles on a Hyper-V host from performance point of view.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.