![exchange public folder migration stuck completing exchange public folder migration stuck completing](https://cdn.supertekboy.com/wp-content/uploads/2014/10/Migrate-Public-Folders-from-Exchange-2010-to-2013-A.jpg)
- Exchange public folder migration stuck completing serial#
- Exchange public folder migration stuck completing update#
Exchange public folder migration stuck completing update#
FAQĪ: This issue was first observed in Exchange Server 2013 Cumulative Update 1, Exchange Server 2016 RTM, and Exchange Online.Ī: In the MRS report, search for "Folder hierarchy changes reported in source," select the first "Folder hierarchy changes reported in source" item that's listed, and then select the date and time that's associated with the log.
![exchange public folder migration stuck completing exchange public folder migration stuck completing](http://2.bp.blogspot.com/-dpxP4RtlzyM/UaNJlT7DHEI/AAAAAAAAAYs/fsYxj8Y6cF0/s1600/Exchange2013-Migration-Part10_Page_17.jpg)
If you're in this situation, we recommend that you wait until the issue is fixed before you run a migration.
![exchange public folder migration stuck completing exchange public folder migration stuck completing](https://www.datarepairtools.com/blog/wp-content/uploads/2018/05/exchange-migrator.jpg)
We realize that this workaround won't work for some customers because of the size of the public folder deployment. This makes sure that the incremental data is copied (regardless of which replica it's originally written to). To work around this issue, add a replica of folders F2 and F3 on PFDB1, make sure that public folder replication is in sync, and then start batch migration. Also, make sure that the public replication is in sync. Workaroundīefore you start batch migration, make sure that all public folders have a replica on the public folder database that will be specified as the source for migration.
![exchange public folder migration stuck completing exchange public folder migration stuck completing](https://www.azure365pro.com/wp-content/uploads/2015/08/Exchange__transparent-1024x408-2013.png)
The fixes are available in Cumulative Update 13 for Exchange Server 2013and Cumulative Update 3 for Exchange 2016. Although data in newly added folder F3 is not copied, the folder appears in the hierarchy. Incremental data to folder F1 is copied, and changes to folder F2 are not copied. (This is true even though folder F3 is displayed in the hierarchy).įigure 2. The batch status is displayed as synced. However, any new data that was added to folder F2 after the first sync isn't copied to modern public folders.Īdditionally, if there are any new folders that are added to PFDB2 after first sync (folder F3 in Figure 2), the content of those folders won't be copied either. This is because PFDB1 is specified as the endpoint. Folder F1 and F2 from the source is copied to the destination during the first sync.ĭuring incremental and final sync, the incremental data from folder F2 isn't copied to modern public folders (as shown in Figure 2). You expect that any data that's added to folder F1 and F2 after the first sync should be copied over during the final sync.įigure 1. This occurs even though PFDB1 doesn't have a local replica of folder F2.Īfter this first sync process, you prepare for the final sync and you start to complete of the batch. When you start the migration and specify PFDB1 as the database to connect to in the New-MigrationEndpoint cmdlet, all data from folders F1 and F2 is copied during the initial sync (as shown in Figure 1). Folder F1 has a replica on PFDB1 and folder F2 has a replica on PFDB2. All data that is at first present in folders that are being migrated are copied, but any incremental changes that are posted after the initial sync may be lost.Īssume that you have two public folder databases, PFDB1 and PFDB2, that are running on Exchange 2007 or Exchange 2010 servers.
Exchange public folder migration stuck completing serial#
If you're using batch migration or serial migration to migrate public folders from Microsoft Exchange Server 2007 or Microsoft Exchange Server 2010 to Exchange Server 2013, Exchange Server 2016, or Exchange Online, data loss may occur if all the folder replicas aren't on the primary database (the primary database server that the migration service connects to). Exchange Server 2016 Enterprise Edition Exchange Server 2016 Standard Edition Exchange Server 2013 Enterprise Exchange Server 2013 Standard Edition Exchange Online More.