Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 25, 2019 5:22 PM
Environment is Ex2016 Enterprise CU11 DAG, two sites, 6 DBs in one site and 5 in the other.
Trying to run a new-mailboxexportrequest on user mailbox (50G in size) using flag "-priority emergency". The export ratchets up to around 46% (last time I checked), then I get various stalls like StalledDueToSource_Processor (processor NEVER goes about 12%), StalledDueToHigherPriorityJobs (no other moves or exports in queue or running), etc. On Tuesday evening it was stalled sitting at 46%; came in today and it was copying messages at 10%. Tried restarting the mailbox replication service because the queued job FAILED to suspent; service went offline.
Are there know issues with Ex2016 and exporting large (50G) mailboxes? Migrations from Ex2013 to Ex2016 were rife with TONS of stalls, but we eventually pushed through. Now we need to do exports to PST and suddenly are having move/export issues here as well. And no, I am not going to do a CU12 update just to rule it out without being told there is a KNOWN issue in CU11 re: exporting and moving large mailboxes.
Suggestions welcome.
Steve In Reno
All replies (4)
Friday, April 26, 2019 4:35 AM
Hi Steve,
As per my experience, it is not recommend to import or export .pst files that are larger than 50 GB, because 50 GB is the maximum .pst file size that's supported by current versions of Outlook.
Mailbox imports and exports in Exchange Server Considerations
Please export mailboxes that are larger than 50 GB by dividing it into smaller chunks, and see if the issue persists. You can use multiple export requests that include or exclude specific folders, or use a content filter. For your reference:
Filterable properties for the -ContentFilter parameter
Regards,
Dawn Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Friday, April 26, 2019 11:54 AM
Agree with Dawn re 50GB limit you should break up export by date range, else your PST file will more then likely fail even if the export completes, i.e. you could end up with a corrupt PST. If you are interested in resolving this via a 3rd party tool, check out DigiScope since it will automatically spawn a new PST when it approaches the set size limit, i.e. John Doe, John Doe2, 3, 4, etc
Search, Recover, Export Mailboxes, Contacts, Calendars, Tasks from ALL versions of Exchange Offline EDB's, On-Premises Exchange Databases & Office 365. Export, Migrate/Recover into On-Premises Exchange Server, Office 365 with Lucid8's DigiScope
Tuesday, April 30, 2019 8:48 AM
Hi,
How is everything going? Do you try above methods?
If there is anything unclear or any update, please feel free to let us know. If the reply helps, kindly mark it as answer, which will be beneficial for answer searching in the forum.
Thanks for your understanding.
Regards,
Dawn Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Wednesday, May 1, 2019 11:29 AM
You can use contentfilter switch and use time range to split up large mailboxes into multiple PSTs. Also Refer Following References: Reference 1 , Reference 2