Solved

Exchange 2010 overuse of memory

Posted on 2012-03-27
5
830 Views
Last Modified: 2012-08-13
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?
0
Comment
Question by:grovenetsupport
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 70

Accepted Solution

by:
KCTS earned 500 total points
ID: 37771062
Exchnage seems unused memory as 'wasted' and if there is memory going begging it will use it to cache the database and to genarally make itself more efficient.

This is not a problem - its normal. if other processes need the memory then exchnage will release it.
0
 
LVL 4

Expert Comment

by:pwnbasketz
ID: 37771097
There was a memory leak that Exchange 2010 had with RPC access that was exacerbated by BES.  It should have been addressed by this rollup for SP1, and so I would imagine also addressed with SP2.  I did come across another article that pointed towards the throttling policy for the the BESadmin account (at least that's what RIM documentation will have you name it, if that's what you followed while setting it up).  If you'd like to take a look at the throttling policy setup, it is here:

http://docs.blackberry.com/en/admin/deliverables/16575/Configuring_Exchange_2010_environ_962756_11.jsp

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.
0
 
LVL 25

Expert Comment

by:Tony Johncock
ID: 37771140
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.
0
 

Author Comment

by:grovenetsupport
ID: 37948422
This does seem to be the case but we have to restart the information store to resolve the memory issue
0
 
LVL 25

Expert Comment

by:Tony Johncock
ID: 37949037
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.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question