Large transaction logs are generated when you move mailboxes in Exchange Server 2013 or Exchange Server 2016 Administration Center


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 1

Enable circular logging on the mailbox database that hosts the "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" arbitration mailbox.

To do this, follow these steps:
  1. Run following command to identify the mailbox database that hosts the "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" arbitration mailbox (Refer the following screen shot): 
    Get-Mailbox -Arbitration | ft Name,Database
    Screenshot for running the command to get the database name
  2. Run the following command to enable circular logging on the mailbox database that you identified identified in step 1:
    Set-MailboxDatabase DB1 -CircularLoggingEnabled $true
Note You must unmount and mount the database to apply the changes.

Method 2

Run the New-MoveRequest EMS command to move mailboxes. For more information about the New-MoveRequest EMS command, go to the following Microsoft website:

文章 ID:2800556 - 上次审阅时间:2015年10月1日 - 修订版本: 1

Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition, Microsoft Exchange Server 2013 Enterprise, Microsoft Exchange Server 2013 Standard