Best Hyper-V Design
Posted on 2011-05-12
I have duplicate Dell R710 servers, each with boot to SAN (no internal drives), running Windows 2008 R2 Enterprise with only Hyper-V SP1 role installed. Each server has dual 6 core Intel CPU and 64MB RAM. Have 3 virtual servers that I'll need built. They are all clean installs.
1. Windows 2008 R2 Enterprise running Exchange 2010
2. Windows 2008 R2 Enterprise running Document Mangement (OpenText eDocs) + SQL 2008 R2
3. Windows 2008 R2 Enterprise running Accounting software (Juris) + SQL 2008 R2
I've read the best practices, multiple white papers, Microsoft's planning software, etc. but can't seem to settle on a design I'm comfortable with. Do I run all 3 virtual servers on 1 box and use the other as fail over only? Or do I split the load, for example, Exchange on 1 box and the other 2 servers on the other box and still use fail over? I realize the Exchange portion requires a little more planning, and currently we have a 400GB database size across 130 mailboxes, running on a Windows 2003 Enterprise/Exchange 2007 dual dual core server with 24MB RAM. The SQL databases on the DM and accounting servers are both right around 10GB in size. Any thoughts on a best design here?