I see a number of my mailbox moves going into a stalled state migrating from Exchange 2007 to 2013. I have paired back the number of simultaneous moves to 7 max. This has helped, but not eliminated the problem. Looking at the MoveRequestStatistics I see that StalledDueToWriteCpu number is high. No other counter is of concern.

I see the status shows as below;

 Informational: The request has been temporarily postponed due to unfavorable
 server health or budget limitations. MRS will attempt to continue processing
 the request again after 4/23/2015 10:39:02 AM. 

Does this mean that the CPU is spiking to a high level and causing the mailbox move to stall? I have 8 cores allocated to this server 4 of the cores are averaging around 80% the other 4 about 30-40%.

Thanks

• Edited by BTRowdy1 Thursday, April 23, 2015 6:18 PM

Hi BTRowdy1,

Thank you for your question.

By the information reminder, mailbox movement will be stopped because you have high hardware usage. it occurred when the server have some performance issues, for example hardware performance, you could add hardware(eg: memory) for move mailbox, we could move few mailboxes at the simultaneous.

Are there any other applications on this server which occurred on CPU?

I suggest we move mailboxes out of production. In addition, we could monitor it for 24 hours if there is any improvement. If not, we could create a new move request for mailbox movement.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,