Article ID: 2800556 - View products that this article applies to.
Assume that you use the Migration wizard in Exchange Administration Center or *-MigrationBatch commands to move mailboxes in Microsoft Exchange Server 2013 or Microsoft Exchange Server 2016. In this situation, transaction logs are generated for the mailbox database that hosts the "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" arbitration mailbox. This issue occurs even though the mailbox database that hosts the Migration mailbox is neither the source or target mailbox database. The transactions logs that are generated may be very large, depending on the size of mailboxes that are moved, and could lead to disk space issues.
The behavior is by design. The migration batch framework uses the "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" arbitration mailbox to store migration metadata (such as batches and migration user information). This behavior generates transaction logs.
To work around this issue, use one of the following methods:
Method 1Enable circular logging on the mailbox database that hosts the "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" arbitration mailbox.
To do this, follow these steps:
Method 2Run the New-MoveRequest EMS command to move mailboxes. For more information about the New-MoveRequest EMS command, go to the following Microsoft website:
General information about the New-MoveRequest command
Article ID: 2800556 - Last Review: October 1, 2015 - Revision: 3.0