Skip to Content

How to Resolve Exchange 2013 Passive Database Replication Failure with Incremental Seeding Error

By: Author Alex Lim

Posted on

Categories Troubleshooting

When an Exchange 2013 database experiences a space issue, like in your case with DB4 on the hac-mbx2 server, it can disrupt the replication process to the passive copy on the hac-csmb server. If the system admin forgets to resume the replication after resolving the disk space problem, attempting to manually resume it may result in an incremental seeding error.

The detail error message as below:

Incremental seeding of database DB-4\HAC-CSMB encountered an error. A full reseed is required. Error: Incremental reseed check failed because 'TCP:HAC-MBX2.abul.com.kw/DB-4\E0400A157EC.log' is missing.

The error message you encountered indicates that incremental reseeding failed because a specific log file (TCP:HAC-MBX2.abul.com.kw/DB-4\E0400A157EC.log) is missing. In this situation, a full reseed is necessary to get the replication back on track.

Solution

To resume the replication of DB4 on hac-csmb, follow these steps:

  1. Open the Exchange Management Shell on the server hosting the passive copy (hac-csmb).
  2. Run the following command to suspend the database copy: 
    Suspend-MailboxDatabaseCopy -Identity "DB4\hac-csmb"
  3. Remove the existing database files from the passive copy server (hac-csmb) by navigating to the database file path and deleting the files.
  4. Run the following command to update the database copy: 
    Update-MailboxDatabaseCopy -Identity "DB4\hac-csmb" -DeleteExistingFiles
  5. Run the following command to resume the database copy: 
    Resume-MailboxDatabaseCopy -Identity "DB4\hac-csmb"
  6. Monitor the replication status using the Get-MailboxDatabaseCopyStatus cmdlet to ensure the reseed process completes successfully.

By following these steps, you’ll initiate a full reseed of the DB4 database copy on the hac-csmb server, effectively resolving the incremental seeding error and resuming the replication process.

Remember to keep an eye on disk space and regularly monitor Exchange environment to prevent similar issues in the future. Implementing disk space alerts and having a well-defined maintenance plan can help you avoid disruptions to database replication and ensure a smooth-running Exchange 2013 deployment.