Solved

Exchange Public Folder migration - Items too large

Posted on 2014-09-14
3
381 Views
Last Modified: 2014-09-21
I am running a migration of Exchange public folders from 2007 to 2013.  There is approx 70GB of data in public folders arranged through approx. 5000 folders and I am getting issues running the initial sync with some items being too large.

Searching the folders for large items is apparently not a thing.

I have not found any logs of what these items are, is there anyway to tell before I skip all large items or is there some way to force the large items through?
0
Comment
Question by:Benlton IT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 20

Expert Comment

by:Peter Hutchison
ID: 40322156
Check the max message size on the receive connectors on the Hub Ttansport servers and also on the replication settings for the Public Folder databases.
You can view any replication event logs in Event Viewer by increasing the event levels in Exchange Powershell, in the the eMC using the Set-EventLogLevel to either Medium or High levels:
http://technet.microsoft.com/en-us/library/dd335139%28v=exchg.141%29.aspx
0
 
LVL 1

Accepted Solution

by:
Benlton IT earned 0 total points
ID: 40326790
All connectors and transport config was set to 100MB to try allow it through but this still did not allow it to complete.

In the end I set the large item limit for the move higher which allowed it to get to 95% and also tell me what items it skipped (in the report generated by

get-publicfoldermigrationrequest | get-publicfoldermigrationrequeststatistics -includereport | fl > c:\pfmigration\report.txt

Open in new window

"

I did not have to alter the logging levels for this to be logged.  These items could then be moved manually (there turned out to be only one and it was 37MB).

The command used to change this setting if anyone is interested was (executed from the 2013 server):

get-publicfoldermigrationrequest | set-publicfoldermigrationrequest -largeitemlimit 50

Open in new window


In my case I did not have to use the acceptlargedataloss switch
0
 
LVL 1

Author Closing Comment

by:Benlton IT
ID: 40335074
I ended up solving my own problem after research and testing
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question