Quantcast
Channel: msexchangerepl.exe processor utilization keeps climbing
Viewing all 65 articles
Browse latest View live

msexchangerepl.exe processor utilization keeps climbing


msexchangerepl.exe processor utilization keeps climbing

$
0
0

We have an antivirus solution installed, but we have set exclusions. We have also tried disabling it and the issue still occurs. We do use snapmanager for exchange. 

No drops in connection with the cluster. 

I have not run the ExPBA, I will do that and report back. 

If we restart the service or the server, the processor utilization returns to normal, but then starts to climb again. I would say with our 8 vcpus, we get about 2 and a half weeks before the issue forces us to restart the server or service. 

msexchangerepl.exe processor utilization keeps climbing

$
0
0

can you check what processes are taking your cpu

msexchangerepl.exe processor utilization keeps climbing

$
0
0

Hi

Do you have any 3rd party products installed?

Do you have file level anti-virus scans enabled?

Do you have any drops in connection with your cluster?

Is anything logged in event viewer?

Can you run ExBPA and check if it generates any issue/warning?

If you restart the service does the utilization drop?

msexchangerepl.exe processor utilization keeps climbing

$
0
0

Hello,

We have an exchange server 2010 sp2 installation that is about 6 months old. We have always had an increasing processor utilization issue  since the environment was built that we have not been able to resolve. Our setup is as follows:

We have a DAG with two member servers, and one witness server. The servers are located in separate data centers with a 100Mbps link and <1ms latency. There is only one AD site for both data centers, there is not an AD site per datacenter. I believe the subnet/nic configuration is different than what Microsoft recommends. We have 2 nics per server, replication and local area connection. On one server, both nics are on a .0 subnet, and on the other server, both NICs are on a .47 subnet. 

I have a theory that the lack of seperate AD sites, and the non-standard subnet configuration could be contributing to, if not causing our replication issues. Is this the wrong line of thinking? Thanks!


Viewing all 65 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>