Video Screencast Help

EV 10 Sizing for 8000 Mailboxes

Created: 13 Mar 2013 • Updated: 01 Apr 2013 | 4 comments
This issue has been solved. See solution.


We are on EV 9.0.3 32bit OS for Vault Server and archiving 8000 mailboxes from 2 x Exchange 2010 DAG groups which runs pretty slow at the moment.

We are planning to migrate to EV 10.0.3 on 64bit OS for Vault (2008 R2) and virtualize EV Server usign VMWare ESX.

If we get 32GB Memory and 8 CPU cores, would that be good enough for archiving 8000 mailboxes or would you recommend to split EV into two EV servers and slipt the laod?

Please suggest

Many Thanks

Operating Systems:

Comments 4 CommentsJump to latest comment

GertjanA's picture


It all depends on how much needs to be archived. If you have little backlog, it might be sufficient, if your archiving window is large enough, if your average message size is not too big. Do you also do Journal Archiving on this server? If yes, then it might be wise to use 2 EV-servers.

You might want to talk to a partner to make a good sizing plan.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS

Tremaine's picture

There is no out and out straightforward answer here as it all depends on your environment, nature of the data being archived, quantities, network, etc.. Ideally you should have professional services evaluate your environment and provide a best recommendation going forward. That being said the alternative is to test it out and see how it goes. Typically the rule of thumb is 5000 active mbxs per EV server.

Additionally if you are Journaling as well then you might want to carefully monitor your Memory usage on a single server and make sure you have the recommended 2.5-3x RAM for Pagefile allocation, especially on the 64Bit system.

Also review the EV VMWare best practices guide at:

ia01's picture

Thanks Guys! Is it good idea to have journaling running in a seperate EV Server?

Tremaine's picture

It may depending on how much you are journaling. However considering that most of your Journaling load would be during the workday and your archiving load probably out of hours when the Journal load is less or non-existent depending on your environment it may not matter. Where you would need to be cautious though is if you run searches regularly against your Journal Archive/s using something such as one or more of Compliance/Discovery Accelerators or Clearwell etc. in which case you again want to monitor the Memory being used by Indexing.