Hardware setup for hyper-v servers and database

i'm student lab manger advanced lab used computer science major. going have moving new building have 3 advanced lab. want build new server setup this. reason being hardware have old , student replace me learn of feature of windows server.the setup support cluster-fail-over.

 

i looking information guide me on type of hardware need run setup. here setup i'm going for.this setup advanced lab used computer science major

information setup:

for virtual server file/user profile, domain control, , server printer running time. file/user profile support desktop redirection 93 computers. website, database, 3 generic used capstone projects students doing. ghost server running windows xp pro used ghost class room computers.

 

hyper-v server 2008 r2 run hyper-v server both using single huge lung ( using shared cluster volume ). hardware setup each server should be: 2x quad core 8 gb of ram each hyper-v server (node). 3 network cards min of 1gb speed. 1 of them can slow because used heartbeat. hard drive doesn't need large os, need fast because virtual server cached there. read hardware needs same between hyper-v server in order virtual computer work.

 

windows server 2008 r2 db role host lung hold virtual server data , user data virtual server. in short san , mirror each other. cpu doesn't need powerful, need ram. need 3 network cards min 1g.

 

current spec of server have now:  (note hyper-threading ht , visualization technology vt)

5x dell optiple gx270 (pointless list spec...)

poweredge 650
p4 @ 3.2ghz (32-bit)
1gb ram (2x 512mb

poweredge 1750
intel xeon @ 3.2ghz (32-bit)
1 gb ram (2x 512mb)
7.3gb max3073nc scsi , 70gb seagate st37320lc scsi

poweredge 840
intel xeon 3060 cpu @ 2.40ghz (64-bit ht no, vt yes)
4gb ram (4x 1024 mb ddr2-sync)
2x 250gb wdc sata , 120gb sata

one tb sata drive.

know of hardware considerations , each hyper-v node must have same hardware configuration.

hello,

here walkthrough of setting hyper-v cluster:

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

a few suggestions:

*  have low amount of ram in hosts (8 gb).  may want consider increasing more capacity.

*  suggest clusters seperate hyper-v network, live migration, host management, , storage.

*  using shared storage?

nathan lasnoski

---

http://blog.concurrency.com/author/nlasnoski/

Windows Server  >  Hyper-V