MS Server 2008 R2 Minimums

I see the minimum of 32GB for Server 2008 itself, but what is the minimum that I should use.  One server will house Server 2008 with Exchanger CAS/HUB role and the other with Server 2008 with the Mailbox role.

With patches, anti-virus, what's the minimum I can get away with on a VM?  We're debating 2 seperate LUNs to present to the VM-- one with the OS and the other with the applications.
Who is Participating?
kevinhsiehConnect With a Mentor Commented:
We are finding that 30 GB for the C drive is too tight for our Exchange 2007 server on Windows 2008 SP2 and we will be expanding that to 40+ GB.

You absolutely should put the data on separate LUN/VMDK/VHD. Several times we have reverted the C drive on our Exchange and file servers without affecting the data which is stored separately. It is very nice to be able to do a quick restore of the OS like that.  
liquid101Author Commented:
Sorry, I should have specified Exchange 2010.  

I have the processor and memory specs from MS, but I was curious as to what everyone else is deploying as far as base Hard Drive space for the VM itself.  For the Mailbox roles we are adding separate DB LUNs to cover all the mailbox DB space.  I just need the bare minimum for upgrades, the applications, patches, etc. Or essentially a feel for what everyone is deploying and is what is practical.  If I can get away with 40GB initially, that would be great.  We're looking for a small footprint on 6 servers.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

AmitIT ArchitectCommented:
I don't think you need 40GB for HUB/CAS role. For MB role also there is a calculator from MS. You can give the inputs and it will give you the result.
liquid101Author Commented:
I'm hoping that 40-45GB will work for what we have since we're tight on space right now.  My goal is to be able to create at least one DAG and it's going to be tight considering the size of our organization.  With smaller footprints initially, I may be able to create a DAG for redundancy and upgrade with more HDD space in the SAN later just in case we need to grow the size of the VM or the data drive (d:).
You can use dynamic VHD or whatever VMware calls it when you thin provision the drive. That will save you on SAN space now and in the future. I always thin provision my OS volumes. No need to tie up 60% of my space that will never get written to.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.