Friday, July 12, 2013

Exchange 2013 generating “Transaction logs” for the wrong database while moving mailboxes



If you are using EAC it will use New-MigrationBatch cmdlet and New-MigrationBatch cmdlet uses a system migration mailbox “Migration.8f3e7716-2011-43e4-96b1-aba62d229136” to keep the metadata. 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.

So Microsoft given the solution , while moving mailboxes around databases if you think it will be a problem to generate transaction logs on the database where Migration System Mailbox is (Due to large metadata), than you should consider the following options.
  1. Turn on Circular Logging for the database where Migration System Mailbox is. (Circular logging is evil don’t do it if you have important mailboxes on that database, lol).
  2. Go back to your Exchange 2010 days and use New-MoveRequest to move mailboxes.
  3. Move the transaction log path to a very large volume for the database where Migration System Mailbox is.

2 comments:

  1. With Exchange Migration it is possible to simply migrate coming from a foreign messaging technique or older exchange versions to newer one.

    ReplyDelete
  2. Yes you can migrate Exchange 2007/2010 to 2013 normally but legacy/foreign messaging you need third party tools.

    ReplyDelete