Hyper v cluster domain controller best practices

I am trying to setup hyper v cluster for first time. I am setting up an active-active high availability iscsi failover. So I have two hyperv servers and two San servers and two switches.

I have an existing network called domain1. All my workstations and vms will be on this domain.

The instructions I have say that I need an active directory server for my hyperv clusters.

I realize I need a private network for all my and replication connections, however do my hyper v servers need a dedicated domain controller? Or Does the private network for iscsi connection and replication need aidomain controller?

Or could I use my existing network domain controller on domain1? For the hyperv servers....and no domain controller for the private network?
MEATBALLHEROAsked:
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.

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Best practice is to have a network where your servers and workstations reside and the host servers need to be on this network.   Networks for iSCSI, replication, heartbeat and live migration do not need a DC.
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
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
How we would set this up:

SANs <--> Switch 1/2 via MPIO <--> Hyper-V Hosts <--> Switch 3/4 <--> Production Network

Keep your storage traffic isolated from your production network.

Then, there is the question of where to put your Live Migration traffic. If LM is to be a regular thing then a dedicated switch or switches would be a good idea unless your storage is 10GbE/40GbE. You If yes to high performance then VLAN for LM.

As to your specific question we _always_ have a physical DC on our cluster based setups. We also run a DC within the cluster.

Why a physical DC since it is not required to cold-boot the cluster?
 + AD may be needed in the event of a cluster failure
 + DNS IS required in the event of a cluster failure
 + Physical DC is our time authority (Critical in a virtualized environment especially with high-load VMs where time skews)
 + Point of management in the event of a problem

Those are the ones that come off the top. :)
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
Virtualization

From novice to tech pro — start learning today.