Hyper-V R2 Datacenter Cluster Licensing with Hyper-V Server


hi,

i have 10 blade servers which starting come end of their life. purchased 7 blades in 2004 and 3 more in 2007 which still have support another 18 months.

i have run msmap utility , says can virtualize all 10 blades , place 9 of 10 vms on hosta. the left on vm placed on hostb. doesn't give me failover capability i need run 3rd server (hostc).

from understand must license each server maximum number of virtual oss run.

does mean can run 2008 r2 dc on hosta 2008 r2 hyper-v server on hostb (the guest vm running copy of 2008 r2 std which has already been purchased under e.a.) , 2008 r2 dc on failover server?

this mean that in case of hosta failing 9 vms migrate hostc. in event of hostb failing single vm migrate hostc.

this mean require 4 processor license 2008 r2 dc instead of 6 processor license. when hardware replaced looking replace 3 node cluster 2 node cluster. not want have pay extra 2 processors licensing when, ultimately, of no use to me within 18 months time.

thanks in advance.

james.

hi,

 

from understand must license each server maximum number of virtual oss run.

 

>> correct this.

 

does mean can run 2008 r2 dc on hosta 2008 r2 hyper-v server on hostb (the guest vm running copy of 2008 r2 std has been purchased under e.a.) , 2008 r2 dc on failover server?

 

>> honest, can’t concern through above description. please check following post see whether helpful.

 

hyper-v high availability / live migration licensing

http://social.technet.microsoft.com/forums/en-us/winserverhyperv/thread/eb5c4931-cdd2-4539-9ce1-2227f9933001

 

by way, if want build test environment, can put domain controller on hyper-v host machine or within vm running on hyper-v. however, if in production environment, microsoft recommends locate critical server roles on domain controllers installed directly on physical hardware. these include global catalog servers, domain name system (dns) servers, flexible single master operations (fsmo) roles , replication bridgeheads.

 

for more information, can refer to:

 

the domain controller dilemma

http://blogs.msdn.com/virtual_pc_guy/archive/2008/11/24/the-domain-controller-dilemma.aspx

 

running domain controllers in hyper-v

http://technet.microsoft.com/en-us/library/dd363553(ws.10).aspx

 

hyper-v , domain controllers – demo tips , tricks

http://blogs.msdn.com/virtual_pc_guy/archive/2009/11/20/hyper-v-and-domain-controllers-demo-tips-and-tricks.aspx

 

deployment considerations virtualized domain controllers

http://technet.microsoft.com/en-us/library/dd348449(ws.10).aspx

 

domain controller on hyper-v

http://social.technet.microsoft.com/forums/en-us/winserverhyperv/thread/e9bd1852-0e84-4885-b6cd-ab888cb71806/

 

considerations when hosting active directory domain controller in virtual hosting environments

http://support.microsoft.com/default.aspx/kb/888794

 

 

best regards,

vincent hu

 



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

Group Policy Event ID 1058 Error Code 1326 (The user name or password is incorrect)

Suspicious event log Event ID: 4905

DCOM received error "2147746132" from...