server 2012 r2 Hyper-v architecture

PowerEdge 2950 is a pretty old server. I won't use it as Hyper-V host even if it supports hardware virtualization.

I've not seen a 1950/2950 that supported the extensons required for Hyper-V. I saw a *couple* 2950 III's that did, but even those are old. I'd not be doing it for SAAS. One outage and your uptime guarnantees go out the window.

With that said, *NEVER* collocate Hyper-V with other roles. So that kills Server 1 and 2 right there. A (slightly) better architecture would be Hyper-V with 4 (or more) VMs with some of those VMs dedicated to the roles you want.  There are new considerations to be taken into account when virtualzing DCs once you  hit that point too.

You can't just casually put together an idea for a network like this. It takes careful planning. As in several weeks' worth. And obviously a project of that scope cannot be covered in one simple EE question.

Please explain collocate hyper-v, you mean hyper-v on a full install physical server.

what considerations should I be thinking if DCs also go hyper-v?

Thinking that maybe all should be hype-v for easier recovery and future move into newer machines.


While both of you have pointed out that 2950 Gen 3 are older machines I thought the point of hyper-v was to utilize the full machine, currently this is not done. Yes, Gen 3 2950s do support Hyper-v.  We have 5 of these so that if a machine does go down we do not; as full redundancy is in place.  This is a startup and building so gathering new machines just does not make business sense.