Concern regarding moving Remote batch migration from exchange 2013 to Exchange online

Question

Hi,

I started the remote batch migration for two dummy accounts to move to exchange online. As batch is syncing but it super slow. overnight it just migrated 10 MB of mailbox. As I checked service health on Exchange online is healthy too.  Can someone help me what could be reason of syncing so slow. Is there any process to increase the speed of synchronization.

Regards !

Answer 1

Hi Alan,

I ran another migration with different source mailbox and error is coming this time is 

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​2019-09-17 12:53:12 AM [YQXPR01MB3864] 'MigrationService (on behalf of '<removed by Alan Wu for protecting your privacy>')' created move request.

2019-09-17 12:53:20 AM [YQXPR01MB3174] The Microsoft Exchange Mailbox Replication service 'YQXPR01MB3174.CANPRD01.PROD.OUTLOOK.COM' (15.20.2263.23 ServerCaps:03FFFFFF, ProxyCaps:0FFFFFFFC7FD6DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:03FFFFFF) is examining the request.

2019-09-17 12:53:20 AM [YQXPR01MB3174] Connected to target mailbox <removed by Alan Wu for protecting your privacy>\b0771725-7149-4c4e-8cab-410b5635885d (Primary)', database 'CANPR01DG199-db031', Mailbox server 'YQXPR01MB3174.CANPRD01.PROD.OUTLOOK.COM' Version 15.20 (Build 2263.0).

2019-09-17 12:53:20 AM [YQXPR01MB3174] Connected to target mailbox <removed by Alan Wu for protecting your privacy>\7764a7ec-f318-41e7-9251-2349769a4730 (Archive)', database 'CANPR01DG199-db031', Mailbox server 'YQXPR01MB3174.CANPRD01.PROD.OUTLOOK.COM' Version 15.20 (Build 2263.0).

2019-09-17 12:53:22 AM [YQXPR01MB3174] Connected to source mailbox <removed by Alan Wu for protecting your privacy>\b0771725-7149-4c4e-8cab-410b5635885d (Primary)', database 'DB1', Mailbox server 'pbs-ex1.pbssystems.com' Version 15.0 (Build 1367.0), proxy server 'pbs-ex1.pbssystems.com' 15.0.1367.0 ServerCaps:, ProxyCaps:, MailboxCaps:, legacyCaps:0400001F7FFFFFCB07FFFF.

2019-09-17 12:53:23 AM [YQXPR01MB3174] Connected to source mailbox <removed by Alan Wu for protecting your privacy>\7764a7ec-f318-41e7-9251-2349769a4730 (Archive)', database 'DB1-Archive', Mailbox server 'pbs-ex1.pbssystems.com' Version 15.0 (Build 1367.0), proxy server 'pbs-ex1.pbssystems.com' 15.0.1367.0 ServerCaps:, ProxyCaps:, MailboxCaps:, legacyCaps:0400001F7FFFFFCB07FFFF.

2019-09-17 12:53:25 AM [YQXPR01MB3174] Request processing started.

2019-09-17 12:53:25 AM [YQXPR01MB3174] Source mailbox information:

Regular Items: 758, 124.8 MB (130,867,773 bytes)

Regular Deleted Items: 298, 10.02 MB (10,506,708 bytes)

FAI Items: 40, 578.8 KB (592,706 bytes)

FAI Deleted Items: 0, 0 B (0 bytes)

2019-09-17 12:53:25 AM [YQXPR01MB3174] Source archive mailbox information:

Regular Items: 1391, 182.9 MB (191,762,844 bytes)

Regular Deleted Items: 0, 0 B (0 bytes)

FAI Items: 3, 4.402 KB (4,508 bytes)

FAI Deleted Items: 0, 0 B (0 bytes)

2019-09-17 12:53:25 AM [YQXPR01MB3174] Cleared sync state for request b0771725-7149-4c4e-8cab-410b5635885d due to 'CleanupOrphanedMailbox'.

2019-09-17 12:53:25 AM [YQXPR01MB3174] Cleared sync state for request 7764a7ec-f318-41e7-9251-2349769a4730 due to 'CleanupOrphanedMailbox'.

2019-09-17 12:53:25 AM [YQXPR01MB3174] Mailbox signature will not be preserved for mailbox <removed by Alan Wu for protecting your privacy>\b0771725-7149-4c4e-8cab-410b5635885d (Primary)'. Outlook clients will need to restart to access the moved mailbox.

2019-09-17 12:53:25 AM [YQXPR01MB3174] Mailbox signature will not be preserved for mailbox '<removed by Alan Wu for protecting your privacy>\7764a7ec-f318-41e7-9251-2349769a4730 (Archive)'. Outlook clients will need to restart to access the moved mailbox.

2019-09-17 12:53:27 AM [YQXPR01MB3174] A corrupted item was encountered: Unable to translate principals to the target mailbox: "Failed to find a principal in the target forest that corresponds to a source forest principal."

2019-09-17 12:53:27 AM [YQXPR01MB3174] A corrupted item was encountered: Unable to translate principals to the target mailbox: "Failed to find a principal in the target forest that corresponds to a source forest principal."

2019-09-17 12:53:27 AM [YQXPR01MB3174] A corrupted item was encountered: Unable to translate principals to the target mailbox: "Failed to find a principal in the target forest that corresponds to a source forest principal."

2019-09-17 12:53:27 AM [YQXPR01MB3174] A corrupted item was encountered: Unable to translate principals to the target mailbox: "Failed to find a principal in the target forest that corresponds to a source forest principal."

2019-09-17 12:53:27 AM [YQXPR01MB3174] A corrupted item was encountered: Unable to translate principals to the target user: "Failed to find a principal in the target forest that corresponds to a source forest principal."

2019-09-17 12:53:27 AM [YQXPR01MB3174] A corrupted item was encountered: Unable to translate principals to the target user: "Failed to find a principal in the target forest that corresponds to a source forest principal."

2019-09-17 12:53:29 AM [YQXPR01MB3174] Stage: CreatingFolderHierarchy. Percent complete: 10.

Let me know, what will be solution ?

Answer 2

Hi Divesh,

If you got an update, please share it with us. We are always here for you. 

Regards,

Alan

Answer 3

Hi Divesh,

Thanks for your information provided in the PM. 

After checking the log, we have found that the migration is repeating and repeating due to an error "The job has been paused temporarily because the mailbox is locked. The job will attempt to continue again after". So this should be the root cause which leads the migration processed so long. As the error indicates that the issue should be connecting to the source mailbox (shown in the following picture). 

Under the current situation, I suggest you try with another source mailbox (Exchange On-premises) to start the migration and see if it makes a difference. 

Regards,

Alan

Answer 4

Hi Divesh,

It is my big pleasure to reply to your post here. 

For your scenario, please re-confirm/try 

1. The network environment, especially the network speed is fast. 
2. Supposing the network is good, you can re-perform the migration and check if it makes a difference. 

If the issue persists, I'd like to collect the following information for analysis. 

1.Get-MigrationBatch -Identity contoso | FL

2.Get-MigrationUserStatistics -Identity ******@contoso.com -IncludeReport | Format-List Status,Error,Report

Note: You need to replace "contoso" and "******@contoso.com" with your real migration batch name and user's email address while running the 2 cmdlets.

For protecting your privacy, it is recommended that you provide the above information in the Private Message (PM).

Regards,

Alan

Answer 5

Hi,

I started the remote batch migration for two dummy accounts to move to exchange online. As batch is syncing but it super slow. overnight it just migrated 10 MB of mailbox. As I checked service health on Exchange online is healthy too.  Can someone help me what could be reason of syncing so slow. Is there any process to increase the speed of synchronization.

Regards!