Exchange – High Memory Utilization

Back pressure is a system resource monitoring feature of the Microsoft Exchange Transport service that exists on Microsoft Exchange 2013 Mailbox servers and Edge Transport servers.

What this means is that the Exchange server monitors key resources, such as hard drive space and memory, and under pressure, can take action to prevent service unavailability. While this can prevent system resources from being completely exhausted, back pressure can cause service degradation. The Exchange server tries to process existing messages before accepting any new messages and therefore introduce delivery delays.

Exchange Server resource sizing is exact science, and furthermore, the environment may change over time with more users, higher email volume, and larger message sizes. Therefore the initial Exchange Server sizing may be inadequate a year later.

In this scenario back pressure was avoided by actively monitoring Exchange Server resources with Intelligent Monitoring. As shown in the figure below, the Exchange mailbox server memory utilization was increasing. Knowing that this was happening allowed the IT team to completely avoid Exchange performance issues by allocating more memory to the Exchange Server.

Identifying this potential issue would not have happened without having Intelligent Monitoring in place. Intelligent Monitoring allowed accessing server performance information easily, and with the guidance of the PCIS team, avert a potential Exchange service degradation completely. Talking about being proactive! 

Figure 8. Exchange Server memory utilization over time

Minimize these incidences with Intelligent Monitoring. Contact us to learn more about the best monitoring solution in the market

200 OK


The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.