I am in the process of migrating mailboxes from Exchange 2007 to 2013. The moves seem to take an awfully long time. I am migrating a batch of 10 users and the total mailbox size is 32GB. It has been running for 12 hours and is not complete. I have notice that there is a "Stalled Duration Time" what does that represent? Also, what should I expect in terms of migration time?

Have you looked at the move logs? Try this

$MoveHistory = (Get-MailboxStatistics "John Doe" -IncludeMoveReport).movehistory
$MoveHistory[0] | Out-file FilePath c:\Temp\MRS-History.Log | Notepad c:\Temp\MRS-History.Log

The report should give you more details into the issue. It could be a network issue or content issue on within the users mailbox. 

Also, seeing this in the logs. It's been about 18 hours now.

Relinquishing job because of large delays due to unfavorable server health or budget limitations.

12/15/2014 9:06:11 PM [Server01] Copy progress: 7546/44948 messages, 167.4 MB (175,539,357 bytes)/2.441 GB (2,620,927,938 bytes), 9/300 folders completed.
12/15/2014 9:06:11 PM [Server01] Relinquishing job because of large delays due to unfavorable server health or budget limitations.
12/15/2014 9:22:30 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:24:35 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:27:10 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:31:53 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:36:51 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:39:47 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:41:21 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:54:43 PM [Server01] Connected to target mailbox 'f491b26b-4a91-4b23-a9aa-d256e8acb8c4 (Primary)', database 'Server0101', Mailbox server 'Server01.domain.com' Version 15.0 (Build 995.0).
12/15/2014 9:54:44 PM [Server01] Connected to source mailbox 'f491b26b-4a91-4b23-a9aa-d256e8acb8c4 (Primary)', database 'mailbox01\Database\DatabaseDB', Mailbox server 'MAILBOX01.domain.com' Version 8.3 (Build 379.0).
12/15/2014 9:58:16 PM [Server01] Request processing continued, stage LoadingMessages.

• Edited by Email Tech Tuesday, December 16, 2014 8:25 PM

Hi,

Please run the following command to check the move status about the migration:

Get-MigrationBatch -Identity batchname -IncludeReport 
Get-MoveRequest | Get-MoveRequestStatistics

Please collect the CUP usage when you are performing migration. Also check the server RAM and examine the storage subsystems. We can also use the Exchange 2013 Server Role Requirements Calculator to calculate the server requirement:

https://gallery.technet.microsoft.com/office/Exchange-2013-Server-Role-f8a61780

Additionally, here is an article which is related to Mailbox Migration Performance Analysis:

http://blogs.technet.com/b/exchange/archive/2014/03/24/mailbox-migration-performance-analysis.aspx

Hope it helps.

Regards,

Hi,

Any updates?

Regards,

Migrations still take a very long time and have a very high "stalled" time. THe content indexes are all in healty state. I have been researching articles and have consisting seen conversations involving the "ContentSubmitters" group. I am running 2013 with CU7 and this group does not exist in AD. Not sure if this could still be an issue? I am only a third completed in my migration and would like to speed it up. Any thoughts? We have allocated 12 CPUs and 32GB of memory to each server. CPU usage is never vary high during the moves.

We resolved the issue by increasing the "MaxActiveJobsPerSourceMailbox" from 5 to 10 and "MaxActiveJobsPerTargetMailbox" from 2 to 10.

• Marked as answer by Email Tech Sunday, March 01, 2015 10:18 AM

We resolved the issue by increasing the "MaxActiveJobsPerSourceMailbox" from 5 to 10 and "MaxActiveJobsPerTargetMailbox" from 2 to 10.

I had the very same problem with same build of Exchange 2013.  This resolution appears to have fixed my problem, too.