locked
Database Copy DB1 shows "Failed and Suspended" status after reseed and/or adding a mailbox database copy from the source RRS feed

  • Question

  • Hi, Guys.

    Good Day!

    Need your assistance on this.

    We're having an issue wherein you we only have a single copy of DB1 on our EXCH2 server. So we basically, we have single point of failure here. We tried to add a database copy of DB1 on EXCH1 and the seed automatically commenced. However, right after completion of the seed activity, such database copy of DB1 on EXCH1 shows in "Failed and Suspended" status. We attempted to reseed the database copy of DB1 on EXCH1 but getting the same error right after completion of the reseed.

    Please advise how to fix this issue. This is somewhat urgent to us.

    Thank you.


    Saturday, August 8, 2015 5:05 AM

Answers

  • Is there anything in the event log?

    If you can't find a solution, you might try this, if you have enough disk space.  Create a new database, and create a copy on the other server.  Move all mailboxes from DB1 to the new database.  Then delete DB1.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    • Proposed as answer by Allen_WangJF Tuesday, August 11, 2015 3:26 AM
    • Marked as answer by Allen_WangJF Tuesday, August 18, 2015 1:24 PM
    Saturday, August 8, 2015 5:24 AM
  • Hi,

    Please check your replication network if replication is happening properly.

    It seems that replication is in suspended state. 

    If replication is working fine, then update the database copy deleting the previous one to add a fresh copy using the below command

    Update-MailboxDatabaseCopy -Identity "DB1\EXCH1" -DeleteExistingFiles

    • Proposed as answer by Allen_WangJF Tuesday, August 11, 2015 3:26 AM
    • Marked as answer by Allen_WangJF Tuesday, August 18, 2015 1:24 PM
    Sunday, August 9, 2015 6:14 AM

All replies

  • Is there anything in the event log?

    If you can't find a solution, you might try this, if you have enough disk space.  Create a new database, and create a copy on the other server.  Move all mailboxes from DB1 to the new database.  Then delete DB1.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    • Proposed as answer by Allen_WangJF Tuesday, August 11, 2015 3:26 AM
    • Marked as answer by Allen_WangJF Tuesday, August 18, 2015 1:24 PM
    Saturday, August 8, 2015 5:24 AM
  • Hi,

    Please check your replication network if replication is happening properly.

    It seems that replication is in suspended state. 

    If replication is working fine, then update the database copy deleting the previous one to add a fresh copy using the below command

    Update-MailboxDatabaseCopy -Identity "DB1\EXCH1" -DeleteExistingFiles

    • Proposed as answer by Allen_WangJF Tuesday, August 11, 2015 3:26 AM
    • Marked as answer by Allen_WangJF Tuesday, August 18, 2015 1:24 PM
    Sunday, August 9, 2015 6:14 AM
  • Hi There,

    Before trying any anything please check the Exchange Mailbox server logs.

    From the error it's very hard to say what is the problem.

    Cheers,


    Exchange Blog:

    www.ntweekly.com

    MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

    Sunday, August 9, 2015 6:32 AM