Symptoms
Consider the following scenario:
-
Update Rollup 3 for Microsoft Exchange Server 2010 Service Pack 2 (SP2) or a later update rollup for Microsoft Exchange Server 2010 SP2 is installed in an environment.
-
You move a mailbox from an Exchange Server 2010 mailbox database to another Exchange Server 2010 mailbox database.
-
The "Completed with warnings" status is displayed for the move operation.
In this scenario, the move operation fails. Additionally, a move request log that resembles the following is logged in the properties of the move request:
Date & Time [Server] Move has completed and final cleanup has started.
Date & Time [Server] Source mailbox 'Primary (Mailbox GUID)' was successfully cleaned up after the move.
Date & Time [Server] Target mailbox 'Primary (Mailbox GUID)' was successfully reset after the move.
Date & Time [Server] Post-move cleanup failed. The operation will try again in 30 seconds (1/6).
Date & Time [Server] Post-move cleanup failed. The operation will try again in 30 seconds (2/6).
Date & Time [Server] Post-move cleanup failed. The operation will try again in 30 seconds (3/6).
Date & Time [Server] Post-move cleanup failed. The operation will try again in 30 seconds (4/6).
Date & Time [Server] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).
Date & Time [Server] Request is complete.
Note If you move many mailboxes to another database at the same time, the move process takes longer than expected.
Cause
This issue occurs because the Mailbox Replication service does not check a certain flag when you move the mailbox. Additionally, a move process for a mailbox that fails takes 30 seconds by default. When a move process for a mailbox fails, the Mailbox Replication service tries five more times to move the mailbox. Therefore, there is a 2.5 minute delay for each mailbox move process when you move many mailboxes at the same time.
Resolution
To resolve this issue, install the following update rollup:
2803727 Description of Update Rollup 1 for Exchange Server 2010 Service Pack 3
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
