Return
-
Title
The Exchange 2007/2010/2013 Tracking Log task takes a long time to complete -
Description
The Exchange 2007/2010/2013 Tracking Log task a long time to complete for specific servers. It may take much longer than other servers -
Cause
Prior to Exchange 2007 There would be one MessageTracking log created per server, per day. Exchange 2007 and 2010 limit the Max MessageTracking Log file size to 10MB, which can create hundreds of tracking logs per server in larger busy environments. When processing the tracking logs, the MessageStats database has to be queried for each tracking log processed. With a very large number of Tracking Logs, this can cause the task to run for a long time. -
Resolution
The workaround for this would be to increase the Maximum MessageTracking log file size on the Hub transport servers to limit the number of files created each day.
Run the following cmdlet from the Exchange Management Shell, to increase the Max log file size to 100MB (this could improve performance by as much as 90%).
Get-TransportServer | Set-TransportServer -MessageTrackingLogMaxFileSize 100MB
Note: For very large environments or if increasing the Tracking Log size to 100MB has not significantly reduced the time it takes for the task to complete, the Tracking Log max file size should be increased to 500MB or 1GB