Reseeding a database copy

There may be times when database replication issues arise in your environment. These issues could be caused by hardware failures, network issues, or, in extremely rare cases, logfile corruption, and leave you with failed database copies that need to be reseeded. This recipe outlines the process for reseeding database copies using the Exchange Management Shell.

How to do it...

1. To reseed a database copy, suspend replication using the following command syntax:

   Suspend-MailboxDatabaseCopy -Identity DB01\MBX2 -Confirm:$false
   

2. Next, you're ready to reseed the database. Use the Update-MailboxDatabaseCopy cmdlet, as shown:

   Update-MailboxDatabaseCopy -Identity DB01\MBX2 `
   -DeleteExistingFiles
   

How it works...

When using the Update-MailboxDatabaseCopy cmdlet to reseed a database copy, you can use the -DeleteExistingFiles switch parameter to remove the passive database and logfiles. Depending on the size of the database, it may take a long time to perform the reseed. Once the reseed...