grovenetsupport
asked on
Exchange 2010 overuse of memory
We are runnng SBS 2011 and Exchange server starts to use all the memory left available making the system slow. If we reboot the information store it drops from 8.4GB to 300MB which it should be. The next day it will be back up to 8.4GB. We have a secondary member server running BES if this has anything to do with it.
Can anyone help. We have SP2 for Exchange installed as this was supposed to stop memory leaks?
Can anyone help. We have SP2 for Exchange installed as this was supposed to stop memory leaks?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Chances are it isn't overused. The Exchange store.exe process has always grabbed as much memory as possible and released it as required.
Here look - it was normal even back in Exc 5.5 days:
http://blogs.technet.com/b/exchange/archive/2004/08/02/206012.aspx
And then 2007:
http://blogs.technet.com/b/exchange/archive/2008/08/06/3406010.aspx
The effect was excascerbated in Exchange 2007 when MS moved from holding things on disk to RAM.
I couldn't find the specific entries for 2003 & 2010, but the above all stands true.
As long as the server isn't behaving in such a way that it appears resource bound, you should be ok.
Here look - it was normal even back in Exc 5.5 days:
http://blogs.technet.com/b/exchange/archive/2004/08/02/206012.aspx
And then 2007:
http://blogs.technet.com/b/exchange/archive/2008/08/06/3406010.aspx
The effect was excascerbated in Exchange 2007 when MS moved from holding things on disk to RAM.
I couldn't find the specific entries for 2003 & 2010, but the above all stands true.
As long as the server isn't behaving in such a way that it appears resource bound, you should be ok.
ASKER
This does seem to be the case but we have to restart the information store to resolve the memory issue
But what, exactly, do you believe the memory "issue" to be? Restarting the information store, will indeed drop the use of RAM down to a nominal amount depending on the system - what roles it has etc - but it will soon be back up to as much as it can grab.
http://docs.blackberry.com
BES is a tricky little thing to troubleshoot, as it is an absolute resource pig. But, I would start with that and see if it helps and let me know.