Cannot move mailbox to a new Database - Exchange 2016 on Prem

Gavin Ross 231 Reputation points
2021-03-04T17:35:09.56+00:00

Not sure how to fix this, had no problem moving a mailbox to a new database before, but trying to move a mailbox to a new database and it is stuck at syncing and when I check the status, I see the following error - StalledDueToTarget_MdbReplication. I have checked both the databases on the DAG and there are no health issues and copy queue length is 0. I have tried to move 2 separate mailboxes on separate databases and the same thing is happening. I have also tried from both the Web GUI and powershell and they both seem to stall at the same 37%. I have also verified that the Migration Mailbox is listed when checking for the Arbitration mailbox. I am not sure what else to check, but seems I cannot migrate any mailboxes at this point. Anyone have any suggestions on what could be causing this issue?

Exchange 2016 - 2 DAG groups - 4 Servers - Hybrid mode with all mailboxes on-prem. Tried to move a mailbox from each DAG and have the same problem on both of them.

Thanks,
Gavin

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,349 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,886 questions
0 comments
Accepted answer
  1. Gavin Ross 231 Reputation points
    2021-03-10T21:14:36.267+00:00

    So it appears that the problem was related to the other issue you were helping me with regarding the missing Self Signed Cert, after I fixed that issue, the replication errors went away as well.

    [PS] C:\WINDOWS\system32>Test-ReplicationHealth -Identity SERVER1

    Server Check Result Error

    SERVER1 ClusterService Passed
    SERVER1 ReplayService Passed
    SERVER1 ActiveManager Passed
    SERVER1 TasksRpcListener Passed
    SERVER1 TcpListener Passed
    SERVER1 ServerLocatorService Passed
    SERVER1 DagMembersUp Passed
    SERVER1 MonitoringService Passed
    SERVER1 ClusterNetwork Passed
    SERVER1 QuorumGroup Passed
    SERVER1 FileShareQuorum Passed
    SERVER1 DatabaseRedundancy Passed
    SERVER1 DatabaseAvailability Passed
    SERVER1 DBCopySuspended Passed
    SERVER1 DBCopyFailed Passed
    SERVER1 DBInitializing Passed
    SERVER1 DBDisconnected Passed
    SERVER1 DBLogCopyKeepingUp Passed
    SERVER1 DBLogReplayKeepingUp Passed

    0 comments

7 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andy David - MVP 141.6K Reputation points MVP
    2021-03-10T19:16:12.423+00:00

    Had a similar thread just recently:
    https://learn.microsoft.com/en-us/answers/questions/287972/exchange-2016-test-replicationhealth-databaseavail.html

    Run:
    Get-ServerComponentState -Identity <server> | FL

    then see if that thread is related

  2. Gavin Ross 231 Reputation points
    2021-03-10T21:13:08.197+00:00

    So it appears that the problem was related to the other issue you were helping me with regarding the missing Self Signed Cert, after I fixed that issue, the replication errors went away as well.

    [PS] C:\WINDOWS\system32>Test-ReplicationHealth -Identity SERVER1

    Server Check Result Error

    SERVER1 ClusterService Passed
    SERVER1 ReplayService Passed
    SERVER1 ActiveManager Passed
    SERVER1 TasksRpcListener Passed
    SERVER1 TcpListener Passed
    SERVER1 ServerLocatorService Passed
    SERVER1 DagMembersUp Passed
    SERVER1 MonitoringService Passed
    SERVER1 ClusterNetwork Passed
    SERVER1 QuorumGroup Passed
    SERVER1 FileShareQuorum Passed
    SERVER1 DatabaseRedundancy Passed
    SERVER1 DatabaseAvailability Passed
    SERVER1 DBCopySuspended Passed
    SERVER1 DBCopyFailed Passed
    SERVER1 DBInitializing Passed
    SERVER1 DBDisconnected Passed
    SERVER1 DBLogCopyKeepingUp Passed
    SERVER1 DBLogReplayKeepingUp Passed

  3. Gavin Ross 231 Reputation points
    2021-03-10T21:37:53.38+00:00

    The migration of the mailbox completed as well. Seems like it was all related to the missing certificate on the server.