Christoph
asked on
Public Folder Migration from Exchange 2010 to Office 365
Hi,
I'm in a migration, mailboxes already onboarded but public folders not at all. I setup batch migration as described here:
https://technet.microsoft.com/en-us/library/dn874017(v=exchg.150).aspx
The problem is:
One mailbox isn't syncing and I don't get any error message. After one week I just got a SyncTimeoutException without any detailed information.
Please help ;)
Thx
I'm in a migration, mailboxes already onboarded but public folders not at all. I setup batch migration as described here:
https://technet.microsoft.com/en-us/library/dn874017(v=exchg.150).aspx
The problem is:
One mailbox isn't syncing and I don't get any error message. After one week I just got a SyncTimeoutException without any detailed information.
Please help ;)
Thx
Hello,
The issue you are getting might be because of following few reasons:
1. The mailbox either have rather big attachments or may be the items with multiple small attachments.
2. The mailbox might be corrupt.
You can try the given solution to resolve this issue.
First, try to locate and remove the messages which are larger than 150 MB from the mailbox. Follow the steps given below:
1. Access the mailbox by MS Outlook.
2. Now, arrange all items in all folders by size.
3. Locate the large size items to another location such as the local computer or a local Personal Folders file (.pst). Now, delete the items that are larger than 150 MB from the user's mailbox.
4. Go to the Exchange admin center again and then resume the migration.
5. After the complete migration of the mailboxes, you can re-imported the data to the Exchange Online mailbox.
I hope this works well for you.
Note: In order to be safe in future, you can try third-party tools which help you to migrate mailboxes from Exchange Server to Office 365 efficiently.
Best Regards,
Tej Pratap Shukla
The issue you are getting might be because of following few reasons:
1. The mailbox either have rather big attachments or may be the items with multiple small attachments.
2. The mailbox might be corrupt.
You can try the given solution to resolve this issue.
First, try to locate and remove the messages which are larger than 150 MB from the mailbox. Follow the steps given below:
1. Access the mailbox by MS Outlook.
2. Now, arrange all items in all folders by size.
3. Locate the large size items to another location such as the local computer or a local Personal Folders file (.pst). Now, delete the items that are larger than 150 MB from the user's mailbox.
4. Go to the Exchange admin center again and then resume the migration.
5. After the complete migration of the mailboxes, you can re-imported the data to the Exchange Online mailbox.
I hope this works well for you.
Note: In order to be safe in future, you can try third-party tools which help you to migrate mailboxes from Exchange Server to Office 365 efficiently.
Best Regards,
Tej Pratap Shukla
@Tej Pratap Shukla might be on to something. But large or corrupted items would be marked as SKIPPED ITEMS (or the column to the right - since you're on German Locacity).
Also - the size limit for Public Folder migration is 50MB - not documented anywhere, had to drag it out of the O365 Support.
If you choose the failing folder - download error logs - do they tell you anything? We discovered that O365 slapped rather restrictive Throttling on public folder migration. The last 20GB took 3 days to complete.
500MB imported
throttled for 8 hrs
400MB imported
throttled for 9hrs
500MB imported
throttled for ..... found that in the downloaded error report
Also - the size limit for Public Folder migration is 50MB - not documented anywhere, had to drag it out of the O365 Support.
If you choose the failing folder - download error logs - do they tell you anything? We discovered that O365 slapped rather restrictive Throttling on public folder migration. The last 20GB took 3 days to complete.
500MB imported
throttled for 8 hrs
400MB imported
throttled for 9hrs
500MB imported
throttled for ..... found that in the downloaded error report
ASKER
Thanks for your replies...
@Jakob
yes, mailbox stays in syncing until it times out!
I got about 220GB public folders, the script provided in the link from microsoft description created those mailboxes...
so you would suggest:
delete the migration batch from O365 admin center
delete Mailbox7 from O365 admin center
create new migration batch from on-premise exchange via powershell
In my opinion I should re-create Mailbox7 before starting new migration batch?
@Tej
I checked item sizes, there are no bigger items than 10MB
So what is your suggestion?
thanks ;)
@Jakob
yes, mailbox stays in syncing until it times out!
I got about 220GB public folders, the script provided in the link from microsoft description created those mailboxes...
so you would suggest:
delete the migration batch from O365 admin center
delete Mailbox7 from O365 admin center
create new migration batch from on-premise exchange via powershell
In my opinion I should re-create Mailbox7 before starting new migration batch?
@Tej
I checked item sizes, there are no bigger items than 10MB
So what is your suggestion?
thanks ;)
ASKER
@Jakob
Here's the "error"-log of Mailbox7:
09.01.2017 09:24:27 [DB6PR0801MB1383] '' created request.
09.01.2017 09:24:40 [HE1PR0801MB2009] The Microsoft Exchange Mailbox Replication service 'HE1PR0801MB2009.eurprd08. prod.outlo ok.com' (15.1.817.10 caps:07FFFF) is examining the request.
09.01.2017 09:24:40 [HE1PR0801MB2009] Connected to target mailbox '9f0b91b8-a100-457f-aeb9-f fd1383ec4e d', database 'EURPR08DG126-db103', Mailbox server 'HE1PR0801MB2009.eurprd08. prod.outlo ok.com' Version 15.1 (Build 817.0).
09.01.2017 09:24:43 [HE1PR0801MB2009] Connected to source mailbox 'Outlook Anywhere Public Folders (/o=XXXXXX/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi guration/c n=Servers/ cn=XXXXXX) ', database '', Mailbox server 'XXXXXX' Version 14.3 (Build 319.0).
09.01.2017 09:25:05 [HE1PR0801MB2009] Job is quarantined.
09.01.2017 09:25:05 [HE1PR0801MB2009] Relinquishing job.
11.01.2017 08:59:38 [DB6PR0801MB1383] '' modified request.
16.01.2017 18:15:24 [DB6PR0801MB1383] '' modified request.
16.01.2017 18:15:24 [DB6PR0801MB1383] '' allowed a large amount of data loss when moving the mailbox (5000 bad items, 5000 large items).
16.01.2017 18:17:59 [DB6PR0801MB1383] '' suspended request.
24.01.2017 09:33:27 [HE1PR0801MB2009] Suspending job.
24.01.2017 09:33:27 [HE1PR0801MB2009] Relinquishing job.
Here's the "error"-log of Mailbox7:
09.01.2017 09:24:40 [HE1PR0801MB2009] The Microsoft Exchange Mailbox Replication service 'HE1PR0801MB2009.eurprd08.
09.01.2017 09:24:40 [HE1PR0801MB2009] Connected to target mailbox '9f0b91b8-a100-457f-aeb9-f
09.01.2017 09:24:43 [HE1PR0801MB2009] Connected to source mailbox 'Outlook Anywhere Public Folders (/o=XXXXXX/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
09.01.2017 09:25:05 [HE1PR0801MB2009] Job is quarantined.
09.01.2017 09:25:05 [HE1PR0801MB2009] Relinquishing job.
11.01.2017 08:59:38 [DB6PR0801MB1383] '' modified request.
16.01.2017 18:15:24 [DB6PR0801MB1383] '' modified request.
16.01.2017 18:15:24 [DB6PR0801MB1383] '' allowed a large amount of data loss when moving the mailbox (5000 bad items, 5000 large items).
16.01.2017 18:17:59 [DB6PR0801MB1383] '' suspended request.
24.01.2017 09:33:27 [HE1PR0801MB2009] Suspending job.
24.01.2017 09:33:27 [HE1PR0801MB2009] Relinquishing job.
looks like something went wrong - obviously. Yes - try to create a new batch. You might get a mailbox in another server next time. But 220GB migration - I guess that would take you 18 - 30hrs to migrate ---
ASKER
Jakob, many thanks, could you please confirm:
-delete the migration batch from O365 admin center
-delete all public mailboxes from O365 admin center
-create new migration batch from on-premise exchange via powershell including script for creating new mailboxes in O365
thx
-delete the migration batch from O365 admin center
-delete all public mailboxes from O365 admin center
-create new migration batch from on-premise exchange via powershell including script for creating new mailboxes in O365
thx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
can I also delete mailbox 7 and recreate it through O365 EAC? I think deleting won't be a problem for me through powershell (remove-mailbox -PublicFolder Mailbox7 --> correct?) but recreating seems to be a bit more tricky through powershell (size has to be defined etc.)
Yes --- no problem
ASKER
just start a new batch and see
ASKER
same error? if so - I suspect some corrupt items in any of you Public Folders.
ASKER
same error but different mailbox. the mapping from legacy public folders to O365-Mailboxes is unchanged so in my opinion, if corrupt items would cause the problem, the same mailbox (Mailbox7) should fail but now Mailbox12 not working...
ASKER
Good News - Mailbox12 started to sync automatically...so let's wait until all 17 Mailboxes are synced ;)
nice ! --- best of luck :)
ASKER
migration complete...thank you jakob ;)
Great news !
But that mailbox stays in syncing until it times out?
I think I'd delete migration batch - delete the failing public folder mailbox and restart. I guess you've created more than enough mailboxes, based on PF size? You got around 200GBs of public folder data?