Hi everyone,

I was trying to migrate all mailboxes from the default built-in DB to a new one. Most of them has been moved successfully, but there are 2 of them stand still. As you can see in the screenshot, the job completed with no error, but no mailbox has been migrated.

We have 2 Mailbox servers making a DAG, all of them are running Exchange Server 2013 CU1.

Can you help me with the idea where to dig for more information? The last step I would take is to backup these 2 mailboxes, delete them, and then restore them in the new DB.

Thank you all in advanced!

Tu9a2

Try using New-MoveRequest on each mailbox.  You'll have to remove the existing move requests first if you haven't done so already.  Then look at the statistics by using Get-MoveRequestStatistics with the -IncludeReport switch.  This is one of the many cases where the Shell is more useful than th

After getting the detailed statistics

Get-MoveRequestStatistics -Identity Tony@contoso.com -IncludeReport | Export-CSV C:\MRStats.csv

I found out that the root cause is "The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database)"

So it leads to another well-known error thread: http://social.technet.microsoft.com/Forums/exchange/en-US/1562fc53-2147-406e-af60-a132948dd421/mailbox-batch-move-stalls-with-content-indexing-lagging-behind-on-resource-message

I decided that I should return to this issue after update the Exchange Server 2013 to CU2 first.
Thanks,

Tu9a2