How to Reseeding After Mailbox Database Copy Failed and Suspended? Get the Solution

When users are creating a replica of the Microsoft Exchange 2016 / 2013 / 2010 mailbox database and if it gets failed & suspended then don’t need to worry. Here, we will help users and providing a reliable solution for the mailbox database copy failed and suspended error by using the manual solution i.e. Exchange PowerShell cmdlet and the advanced software which help users to remove the corruption from Exchange database file and extract mailbox from EDB file Exchange 2016/2013/2010 & below version and export directly to the Live Exchange Server, Office 365, and different file formats simplified way.

Before proceeding toward the solution to solve this issue let’s know about seeding.

When users update the EDB (Exchange Database) by copy its data into another Microsoft Exchange Server that is called seeding. All this is done by using the “Update-MailboxDatabaseCopy” in the system.

User would require the DAG (Database Availability Group) to reseed the mailbox server with the failed copy of the mailbox database, if the DB fails to copy in the Exchange 2016, 2013, 2010 Server.

When Users Require Seeding?

1. When the first actual database has encountered the threat or a disaster and become unreachable. The static duplicate data set at that point can be useful or valuable in rebuilding or re-establishing the data information.
2. It also needs in case of offline defragmentation event with the actual database.
3. At that particular point when the log generation for Exchange EDB changed to 1.
4. When the server has received the degenerate log file which cannot be accessed in the actual database then this can confirm in the copy DB (Database).

Important Point to Remember Before Carry Out the Reseeding Process

1. To run the seeding process users should have DAG and permission of Exchange mailbox database copy. The Exchange admin must allocate such permission to the client
2. Any current or recent Exchange mailbox database should be suspended
3. Exchange Server should run the remote registry service to facilitate latent databases

Error Occurs If the Seeding Procedure Fails

The issue arises due to the corrupted email and it may damage the entire database if it is not treated properly.

In case of inability to process copy database properly, then the user will encounter the failed status of this procedure.

Error message: Passive copy ‘DB08\EX2016SRV1’ isn’t in a good state. Status: FailedAndSuspended

Similarly, the user can execute the command given below to get the current state of the update.

Get-MailboxDatabaseCopyStatus | where  {$_.State - eq "Failed"}

After the seeding procedure fails, the command will display all the update measure that failed to run. If users want to again execute the update process then that is called reseeding at that point.

To check the status of the copy you can use the Exchange PowerShell cmdlet given below:

Get-MailboxDatabaseCopyStatus

How to Fix “Mailbox Database Copy Failed and Suspended” the Error?

To solve the error you have to update the Exchange mailbox database copy by using the cmdlet given below:

Update-MailboxDatabaseCopy -Identity “DB08\EX2016SRV1” -DeleteExistingFiles

For longer reseed and in case when the Exchange PowerShell is closed, use the following command i.e. given below:

Update-MailboxDatabaseCopy -Identity ‘DB08\EX2016SRV1’ -BeginSeed

To keep away any error message, use the DeleteExistingFile command which deleted all existing log file

Update-MailboxDatabaseCopy -Identity “DB08\EX2016SRV1” -BeginSeed -DeleteExistingFiles

Ensure the Point Given Below Before Running the Reseeding Command

1. Depending on the size of the mailbox database & network speed between the source & destination Exchange Server, reseeding procedure takes time.

2. The size of the final database at the destination is larger then the original or source database.v

Example: If the source DB size if 500 GB then the database size at the destination side is more than 500 GB. The reason behind this that it contains content index data and the transaction log file.

3. By default, the Database Availability Group (DAG) group member server, only use the command with the active database copy when host server copy the DB.

4. If the source and destination Exchange Server doesn’t belong to the same DAG group then it would take time to complete the process. Likewise, if they blog to the same Database Availability Group then the time take to complete the procedure is quite less.

Use Exchange Admin Center to Perform Reseeding

Follow the steps given below to reseed the copy process

Step 1: Login in via admin credentials >> Navigate to the Server >> Database

Step 2: Select the required database that is needed to update

Step 3: To start the reseeding procedure, click on the update button

Step 4: Click on the browse button to add the source Exchange Server

Step 5: After that, the reseeding process will begin. You have to wait till the process gets end

This is the complete procedure to deal with the mailbox database copy failed and suspended issue. Users can also deal with conditions by using the different Exchange PowerShell command and EAC solution accordingly.

Note: In case, if the mailbox database is corrupted, sometimes the copy process will become pointless, then users can use the advanced solution i.e. Exchange Server EDB Recovery Tool provided by SysTools easily fix Exchange database corruption automatically without using any command in a hassle freeway. The recovery manager for Exchange database software support offline/dismounted Exchange database and it provides scan mode option i.e. Quick & Advance scan which easily resolves database corruption Exchange 2010, 2013, 2016 and repair EDB file with no data loss in a simplified manner. After recovery, users can export the healthy and recovered mailboxes directly to the Exchange Server Mailboxes, Office 365, and multiple file formats.

Download Now Purchase Now

Drawback Of Manual Solution

1. This process requires technical expertise and in-depth knowledge
2. It is a time take process. If you are new to the Exchange environment then it would be difficult you to understand all the technicalities and sometimes the experts also take time to fix the issue by using this solution
3. A little bit of mistake can screw up the entire process and results in the corruption of the original EDB file

Bringing It All Together

Now users know how & when the error mailbox database copy failed and suspended occurs. They can free to use the manual as well as automated solution provided in this write-up but their repercussion is unavoidable. The automated wizard is used by many IT Experts, Exchange, and novice users to recover, repair Exchange mailbox and EDB file from corruption. Then after the recovery process, users can extract the Exchange database mailboxes and  export recovered EDB mailboxes to Live Exchange Server mailboxes in a simplified manner without any hindrance. So, to avoid the data loss due to corruption it is suggested to use the advanced software to remove corruption from Exchange database without any loss of data.