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, log file corruption, and leave you with failed database copies that need to be reseeded. This recipe outlines the process of reseeding database copies using the Exchange Management Shell.

How to do it...

Let's see how to reseed a database copy using the following steps:

1. To reseed a database copy, suspend the 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 in the following command:

   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...