none
Failing to migrate mailboxes from exchange 2010 to Exchange 2016 RRS feed

  • Question

  • Dear All,

    I have 2 CAS ,2 Mailbox (exchange 2010 ) on DC site , and 2 mailbox on DR site all in dag01

    I have installed Exchange 2016 in the DC site created new database but failing to migrate mailbox from old exchange to new exchange:

    From new exchange:

    getting this error databases Passive ServiceDown Content index state:  Unknown for the old databases. but new database are in healthy state. 

    Please kindly suggest


    Sunday, May 5, 2019 7:53 AM

Answers

  • No, thank , we have figured out the issue its actually the firewall issue , more specifically dynamic ports was causing this problem. Once when have opened all the ports the issue got resolved.

    • Marked as answer by rafiul islam Tuesday, May 21, 2019 5:11 PM
    Tuesday, May 21, 2019 5:11 PM

All replies

  • Hi,

    >>getting this error databases Passive ServiceDown Content index state:  Unknown for the old databases. but new database are in healthy state. 

    You may first run the Get-MailboxDatabaseCopyStatus cmdlet to display all database copies that have a content index in a failed state. Run the following cmdlet to update the content index on the server on which it has failed:

    Update-MailboxDatabaseCopy "MBX01" -CatalogOnly

    Then, try migrating the mailboxes again to see the result.

    Regards,
    Steve Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, May 6, 2019 6:44 AM
    Moderator
  • Are you getting the error when checking the DAG status from the 2010 server or 2016 server?

    If you run Get-MailboxDatabaseCopyStatus * are all servers online and healthy?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, May 7, 2019 9:28 AM
    Moderator
  • Name                                          Status          CopyQueue ReplayQueue LastInspectedLogTime                                                   ContentIndex
                                                                  Length    Length                                                                             State
    ----                                          ------          --------- ----------- --------------------                                                   ------------
    DB1\ASH-MBXLV-01                            ServiceDown     0         0                                                                                  Unknown
    DB2\ASH-MBXLV-01                            ServiceDown     0         0                                                                                  Unknown
    DB5\ASH-MBXLV-01                            ServiceDown     0         0                                                                                  Unknown
    DB3\ASH-MBXLV-01                            ServiceDown     0         0                                                                                  Unknown
    DB4\ASH-MBXLV-01                            ServiceDown     0         0                                                                                  Unknown
    Mailbox Database 1990668671\ASH-MBXDR-01    ServiceDown     0         0                                                                                  Unknown
    DB1\ASH-MBXDR-01                            ServiceDown     0         0                                                                                  Unknown
    DB2\ASH-MBXDR-01                            ServiceDown     0         0                                                                                  Unknown
    DB3\ASH-MBXDR-01                            ServiceDown     0         0                                                                                  Unknown
    DB4\ASH-MBXDR-01                            ServiceDown     0         0                                                                                  Unknown
    Mailbox Database 1630278097\ASH-MBXDR-02    ServiceDown     0         0                                                                                  Unknown
    DB5\ASH-MBXDR-02                            ServiceDown     0         0                                                                                  Unknown
    DB5\ASH-MBXLV-02                            ServiceDown     0         0                                                                                  Unknown
    DB4\ASH-MBXLV-02                            ServiceDown     0         0                                                                                  Unknown
    DB3\ASH-MBXLV-02                            ServiceDown     0         0                                                                                  Unknown
    DB2\ASH-MBXLV-02                            ServiceDown     0         0                                                                                  Unknown
    DB1\ASH-MBXLV-02                            ServiceDown     0         0                                                                                  Unknown
    EXDB01\EXMBX-DC-1                             Mounted         0         0                                                                                  Healthy
    EXDB03\EXMBX-DC-1                             Mounted         0         0                                                                                  Healthy
    EXDB05\EXMBX-DC-1                             Mounted         0         0                                                                                  Healthy
    EXRECOVERY\EXMBX-DC-1                         Mounted         0         0                                                                                  Healthy
    EXDB02\EXMBX-DC-1                             Healthy         0         0           5/9/2019 12:43:20 PM                                                   Healthy
    EXDB04\EXMBX-DC-1                             Healthy         0         0           5/9/2019 12:42:48 PM                                                   Healthy
    EXDB06\EXMBX-DC-1                             Healthy         0         0           5/9/2019 12:50:43 PM                                                   Healthy
    EXDB02\EXMBX-DC-2                             Mounted         0         0                                                                                  Healthy
    EXDB04\EXMBX-DC-2                             Mounted         0         0                                                                                  Healthy
    EXDB06\EXMBX-DC-2                             Mounted         0         0                                                                                  Healthy
    EXDB01\EXMBX-DC-2                             Healthy         0         0           5/9/2019 12:42:21 PM                                                   Healthy
    EXDB03\EXMBX-DC-2                             Healthy         0         0           5/9/2019 12:40:39 PM                                                   Healthy
    EXDB05\EXMBX-DC-2                             Healthy         0         0           5/9/2019 12:40:29 PM                                                   Healthy
    EXRECOVERY\EXMBX-DC-2                         Healthy         0         0           5/9/2019 12:42:06 PM                                                   Healthy

    Thursday, May 9, 2019 6:56 AM
  • Thank you for the update. 

    Have you tried restarting the Replication Service? 

    Is there any firewall blocking the communication between the Exchange servers and each others?

    Please also check whether there is any relevant error event in the Event Viewer.

    Regards,
    Steve Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, May 14, 2019 7:39 AM
    Moderator
  • Just wanted to say hi and check if there is anything that we can do for you on this problem. If so, please do not hesitate to let us know and we will be happy to help.

    Best regards,
    Steve Fan 


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, May 17, 2019 7:58 AM
    Moderator
  • No, thank , we have figured out the issue its actually the firewall issue , more specifically dynamic ports was causing this problem. Once when have opened all the ports the issue got resolved.

    • Marked as answer by rafiul islam Tuesday, May 21, 2019 5:11 PM
    Tuesday, May 21, 2019 5:11 PM
  • Good for you! Thank you for keeping us posted.

    Regards,
    Steve Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 22, 2019 1:37 AM
    Moderator