Hi Team,
I know this is an old post but my situation is related. I am working on the Public Folder migration from Exchange 2010 to Exchange 2016 in a lab, when processing the migration batch, I have found the replication health check is interrupting the data move due to the mrs has not been satisfied. The problem is when the replay queue length keeps growing when data is syncing. It stops the move when the queue length reaches 100, then has to wait until the queue is clear and the mrs starts checking the request again. How can I resolve the issue? Should I set the datamovereplicationconstraint to None? Can it bypass the replication health checks?
Thank you so much!
Gary Lee