Microsoft Exchange 2010
Customer's archive jobs were slowing down their Exchange server. When they would abort the job, performance on the Exchange server immediately picked back up to normal.
Retain archive jobs have a very light footprint on the Exchange server, so this is not normal behavior. Turned out that the customer was running a CommVault backup job on the Retain server at the same time as the job was running.
The customer changed the job to run at a time when CommVault was not running its backup and the performance issue on the Exchange server went away.
This article was originally published in the GWAVA knowledgebase as article ID 2322.