New to Hyper V, questions before design

i run department not profit corporation.  cheer loudly amazement we're getting off netware 6.5 , groupwise.   yayyyyy!!!!!!

i'll scratch setting our new network using 2008 hyperv , need advice whom have done this.

being not profit fantastic deals on pc's dell, we'll using new servers them.  we're looking at:

3 database servers, 1 ms sql , 7 users, 1 mdac , 3 users, 1 pervasive sql that's used maybe once month @ best 1 person.
1 exchange server 30 employees use webmail.
1 blackberry enterprise server sql server installed
file sharing 30 employees, maybe 600 gig, opt gave 1tb
one workstation either run terminal services or run xp occasional remote connection
1 test server me  :-)
2 centos servers may keep separate , not virtualize.

that's 10 systems total.  pretty low use compared companies.

here's choices:

1) run 2 or 3 dell 1950 servers spreading virtualization out among them, loaded dual 2.5 quad cores, 16 gig of ram, , raid 5, , run 2950 file sharing
2) run 2 2950's , connect them both sas enough hd space handle storage, virtualize on 2 2950's. 

any thoughts?  consider other configs, , i'd love hear gotcha's out for.  , if both of these severe overkill i'd hear other configs. 

  

hello,

 

we plan on high availability (n+1) in hyper-v solutions design.  main reason consequences of single server failure escalate when virtualizing , want server able receive workload.  in case, use following guide:

 

• windows server 2008 enterprise edition hyper-v using failover clustering
• n+1 server architecture: n = servers required load, failover server
• single u servers (dell 1950 great), quad core, 32 gb ram, internal drives os
• iscsi or sas storage shared disk access.  use raid 10 storage.

 

this typically starting point. 

 

i wrote more on topic here (after seeing jeff woolsey speak):

http://nathanlasnoski.spaces.live.com/blog/cns!f7a33f1f9ebd9237!211.entry

 

nathan lasnoski

Windows Server  >  Hyper-V