Hi,

Overall we are and have been migrating from Exchange 2007 to Exchange 2013 for some time now.

An issue we get in Exchange 2013 is that when we enable In-Place archiving (with the default MRM pol) for multiple users (lets say 15 this last time) the Exchange MB server starts to die for a number of reasons:

1) Noderunner.exe & parserserver.exe both consume a lot of CPU over the following day(s) after enabling

2) The log file for the Archive Mailbox DB grows massively over the same period, it does shrink once the backup is completed (nightly).

The main issue I have with this is the lack of control of when this runs - if for example I could stop this happening during daytime hours then it could churn away to its hearts content over night (aslong as we have sufficient log drive space available)

I suspect its not just the actual moving of the mails from the primary DB to the Archive DB - but also the search indexing (or similar) which must be running on the new content on the Archive DB.

The timing issue of knowing when this runs or being able to control it affects the log drive issue because we run nightly backups at 20:00 - if we knew for example that archiving would only run up to 20:00 I could then trigger the backup to run after that - but seemingly it is random when it kicks off - so last nights backup completed fine and was a few GB - when I came in this morning the Archive DB log is 120 GB and getting close to being out of space on the disk so I had to grow the disk and kick off a new backup.

Question:

Can you schedule when the archiving run kicks in, and tell it to stop at a certain time?

thanks

Chris

anyone?

this is currently happening right now - going to have to keep increasing the log drive as it is out pacing my backup at the moment (using DPM)..

is there a way to stop the archiving process temporarily or pause it? like a specific service I can stop?