Microsoft Exchange Replication Service 2010 - high CPU usage
We have a problem where Microsoft Exchange Replication Service on Exchange 2010 (SBS 2011) consistently hogs server CPU and this grows over 10-14 days until the server CPU is permanently maxing out at 100%, slowing everything else down.
The only resolution we have found so far is...to reboot the server. But that is not a solution, just a temporary fix as it sends MS ERS CPU usage back down to 1-2% only, but this grows day by day until a couple of weeks have gone by and MS ERS is on 55-60% and with other software running the server is maxed out again.
Anyone have any clues?
We only have one Exchange server. We do also run Blackberry Enterprise Server Express on the same server.
Thanks for any help.
The only resolution we have found so far is...to reboot the server. But that is not a solution, just a temporary fix as it sends MS ERS CPU usage back down to 1-2% only, but this grows day by day until a couple of weeks have gone by and MS ERS is on 55-60% and with other software running the server is maxed out again.
Anyone have any clues?
We only have one Exchange server. We do also run Blackberry Enterprise Server Express on the same server.
Thanks for any help.
Please refer below article for Throttling the Mailbox Replication Service
http://technet.microsoft.com/en-us/library/ff963524.aspx
http://technet.microsoft.com/en-us/library/ff963524.aspx
ASKER
Thanks for your suggestions. We have had a Microsoft engineer look at it over the last few days, and he cannot find anything wrong with the MS software, so has suggested we trying first uninstalling our McAfee VirusScan, and if that doesn't solve it the other possible one he thought is our antispam software, which is Hexamail.
Trying first with the McAfee...
Trying first with the McAfee...
It's good to rule out the Third party software by disabling/uninstalling it.
If you still see this issue then you should go for a Memory Dump.
Does it always take High CPU or intermittently? How much does it spike? 100% or 70% etc?
Is this a physical box or VM?
~ Singh
If you still see this issue then you should go for a Memory Dump.
Does it always take High CPU or intermittently? How much does it spike? 100% or 70% etc?
Is this a physical box or VM?
~ Singh
ASKER
It is a physical machine, only a few months old.
The CPU usage is all the time. It will build incrementally after a reboot, starting for the first day fluctuating between 1% and 2% of CPU usage, but that grows day by day by 2-3% a day, until after 2 weeks or so it is permanently taking 50-60% of CPU (and with the other software also taking up CPU this means the CPU is permanently at 100%, and slowing the system down so we have to reboot).
The CPU usage is all the time. It will build incrementally after a reboot, starting for the first day fluctuating between 1% and 2% of CPU usage, but that grows day by day by 2-3% a day, until after 2 weeks or so it is permanently taking 50-60% of CPU (and with the other software also taking up CPU this means the CPU is permanently at 100%, and slowing the system down so we have to reboot).
Did you solve it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I found this Microsoft KB in the meantime:
http://support.microsoft.com/kb/2741117
Symptoms:
The Microsoft Exchange Replication service consumes excessive CPU resources on Client Access servers in an Exchange Server 2010 environment. This issue occurs even though you do not perform mailbox move operations.
Cause:
This issue occurs because the Exchange Replication service checks the mailbox databases status too frequently. This causes the service to consume unnecessary CPU resources.
Solution:
To resolve this issue, install the following update rollup:
Update Rollup 6 for Exchange Server 2010 Service Pack
http://support.microsoft.com/kb/2741117
Symptoms:
The Microsoft Exchange Replication service consumes excessive CPU resources on Client Access servers in an Exchange Server 2010 environment. This issue occurs even though you do not perform mailbox move operations.
Cause:
This issue occurs because the Exchange Replication service checks the mailbox databases status too frequently. This causes the service to consume unnecessary CPU resources.
Solution:
To resolve this issue, install the following update rollup:
Update Rollup 6 for Exchange Server 2010 Service Pack
ASKER
Actual cause never found
Best way to find out why it is taking High CPU is to collect Hang Dump of process during problem time and get it analyzed by one of microsoft Exchange Escalation Engineers.
~ Singh