Link to home
Start Free TrialLog in
Avatar of JHMH IT Staff
JHMH IT StaffFlag for United States of America

asked on

Exchange 2013 Deployment on VMware

We are planning an Exchange 2013 deployment with Server 2012 on a VM. It will be a new deployment (not an upgrade) that will only support 100 users. How much CPU and RAM would you all recommend for this type of deployment?
SOLUTION
Avatar of Mai Ali (MVP)
Mai Ali (MVP)

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Are you looking for High Availability or just a stand alone box. According to that I can suggest you.
In addition to the above, please look through this guide from VMware.

https://www.vmware.com/files/pdf/Exchange_2013_on_VMware_Best_Practices_Guide.pdf

No more than 24 cores and no more than 96 gig of RAM.

If you go above these numbers it will adversely affect performance.

Exchange 2013 is designed to be scaled out not up.

When I was with MS supporting Exchange we had quite a few customers who had 256 gig of memory and 48 or more cores.  It was difficult explaining that 2 servers with half the resources would have been better.

Also don't over subscribe processors and memory.
Avatar of JHMH IT Staff

ASKER

I guess what we're looking for is the "cliff's notes"; that documentation is all very intense and a little beyond what we normally scope out. We currently run a virtualized Exchange 2003 server with 4 CPUs, 4 GB RAM, and serving 500 mailboxes on a 250 GB data drive (the server was P2V'd into our virtual environment). Looking at the documentation linked in the comments and fumbling with the calculator makes it seem as if we'll need almost 2 TB for only 100 mailboxes! I can't imagine that's actually the case.

What hard drive size would you recommend for a server which will only house 100 mailboxes, 20 mailboxes limited to 20 GB receiving 100 messages a day, the other 80 limited to 5 GB receiving 50 messages a day? We will be using Veeam backup for Exchange, so there is no need to keep several copies of the database locally, only the minimum.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You should read this first:
http://exchangeserverpro.com/exchange-2010-mailbox-database-growing-big-fast/

Best to create multiple DB's. Smaller DB's are always good. Keep disk size to 500GB max with 10% free space. If you are using stand alone, then you can keep logs on other drive. If DAG then you need to keep logs on same drives.
This is good info we were able to use as a guide.
Excellent. Glad we could help.