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 introduces delivery delays. Exchange Server resource sizing is an exact science. Over time, with more users, higher email volume, and larger message sizes, environment will change over time. Therefore the initial Exchange Server sizing may be inadequate a year later.

In this scenario back pressure was avoided by actively monitoring the 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 gives you access to server performance information easily and with the guidance of the PCIS team, can avert a potential Exchange service degradation issue.


Exchange 2013 – Failed to detect the BitLocker state for EDS log drive ‘C:\’

BitLocker is a feature in Windows Server 2012 (and newer) for encrypting the hard drive. Most organizations are not required to encrypt the data on the server hard drives and to my experience, very few organizations choose to do so unless they are forced to do so. Therefore, to the surprise of many of us, the Windows Event Log starts filling up with BitLocker related messages on the Exchange 2013 servers after installing Cumulative Update 7 (CU7) for Exchange Server 2013. It turns out that Exchange will try to check for the drive encryption status and will keep failing unless the feature is installed.

Alternatively, these Event Log messages can be supressed by applying a small configuration file change. Locate the configuration file Microsoft.Exchange.Diagnostics.Service.exe.config (located in C:\Program Files\Microsoft\Exchange Server\V15\Bin\), and change the DriveLockCheckEnabled setting to false as shown below.

<add key=”DriveLockCheckEnabled” value=”false” />

Restart the Microsoft Exchange Diagnostics service after this and the messages should no longer pop up. This issue is not critical but creates a lot of noise in the Windows Event Log potentially hiding other more important error messages. I try to check Windows Event Logs after every CU update immediately and also check the following day.


Symantec Backup 2012 Disaster Recovery to different hardware, or other testing routes

I need a solution

Okay, I know this post is going to sound like a broken record, but I have searched and read through other threads but it seemed to either not address or solve the issue directly or give an unclear explanation that pertained to that specific persons problem. Here it goes and please accept my apologies if this post seems so redundant. 

Okay so I have a HP Proliant DL380 G4 server running Symantec Backup Exec 2012 (I know, I know, it’s an old server lol) and I’m used to using Puredisk but it seems quite easy administering backups with SBE 2012 UNTIL! it’s time to do recovery testing. I noticed I didn’t have an adequate testing environment for my recovery tests, so I grabbed the best computer I could find which is a Dell Tower 5810 w/ a 1TB backup drive and a 250GB boot drive which isn’t setup for RAID. So I tried doing a recovery of my HP Proliant server to my Dell Tower and I was met with a number of obstacles that indicated my recovery might go so smoothly, I will list those messages at the end. A little FYI – I do full SDR backups on our server here, the server is setup in a RAID 0 with a C: and D: drive and the Dell Tower is booting AHCI. Basically, I am not able to recover my backups to the Dell Tower. It’s obvious that either this scenario won’t work at all or I will need to do quite a bit of tweaking to make my test recoveries successful. I would really like to be able to find a way to recovery to the Dell Tower because if that HP server did crash then that may very well be all I have to use. So I have two questions if anyone can please answer:

1. How can I get this scenario to work; how can I get my recovery my backups to different hardware?

2. In the future, what is the best test environment to setup for conducting test recoveries? 

Thanks, thanks, thanks, to anyone who can help me with this. It has been a headache going on three days trying to figure this out on my own. Below are the messages I ran into while trying to test-recover my backups to a different computer:

– Your computer may not start successfully, if your system or boot volume resides on one of the hard disks attached to an inactive controller

– Drivers for one or more controllers are not installed. The computer may not start because the required system…

– If the recovered computer contains multiple hard disks, ensure that the computer’s BIOS is configured to start the computer from the hard disk that contains the Windows Operating System

– invalid partition table (I received this message after rebooting from a restore)




WebSphere proxy server routing capabilities in a secured environment

This article discusses the various routing capabilities of the WebSphere
proxy server, which is a feature of IBM WebSphere Application Server Network
Deployment. Multiple configuration scenarios are presented, along with
background information, setup
instructions and tips to help you achieve success routing content using proxy
server features in a secured environment.