This is easy to do using Windows PowerShell. Exchange 2010 DAG with a Failed Database Copy. Although it is something that usually does not need to be monitored, it is always good to keep an eye on it to see how it is doing. To move the mailbox from one database to another, you need to create a move request (if a migration occurs within the same Active Directory forest, this is called a local move request, if you want to move a mailbox between AD forests—this is a remote move request). After all mailboxes in the databases have been indexed, Exchange Search changes the status of the database to Notification. To reseed the database copy launch the Exchange Management Shell on the server that is in a failed state. The file is locked or in use. But all other copies with Activation preference 3, 4 and 5 are in a FailedandSuspended state. To move user mailbox the New-MoveRequest cmdlet is used. The file is locked or in use. Use the following command, specifying the mailbox database in the format “
”. Stoping the MSExchangeFastSearch is failing the content index states of other DBs on that server to go on failed state :/ Reply. The Get-MailboxDatabaseCopyStatus cmdlet gives us … The status remains Crawling until all mailboxes in the database have been indexed. The first Copy of every Mounted Database with the Activation Preference set as 2 is in a Healthy State for Content Indexing. Resolution Error: File check failed: File ' ' could not be opened. How to Reseed a Failed Mailbox Database Copy in Exchange ? Crawling state is where Exchange Search indexes mailboxes in the database. Get-MailboxDatabaseCopyStatus and find the database with failed or supended status Test-ReplicationHealth –Identity “DB_name” suspend the copy Suspend-MailboxDatabaseCopy –Identity “db_name\server” Now update it from a good copy of the replication server Update-MailboxDatabaseCopy –Identity “DB_name\Server” –DeleteExistingFiles so wait untill Crawling notifications changes to Healthy state The final step is to get the database copies index state back to a healthy state. First we need to suspend replication for the mailbox database copy on this server. All I need to do is use the Get-MailboxDatabase cmdlet to retrieve all of my Exchange databases, then I pipe the resulting objects to the Dismount-Database cmdlet, as shown here. To resolve these issues, install one of the following updates: Update Rollup 3 for Exchange Server 2010 For more information about Update Rollup 3 for Exchange Server 2010, visit the following Microsoft website: But if I am going to run Eseutil to check the dirty status of the database, then the mailbox databases need to be offline. Operation completed successfully in 1.404 seconds. To reseed the database copy launch the Exchange Management Shell on the server that is in a failed state First we need to suspend replication for the mailbox database copy on this server. So for each database i have one Active good state and one Copy good Healthy state. Even more disconcerting, refreshing the Database Copies tab for that mailbox server shows that several of the DB's are bouncing around between healthy and the 'disconnected and healthy' state. At this point, I'm not sure if it's worth it to reseed the passive copy through the EMC. What can I do to fix the content Index state of both the database. Log file: C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E0000001D64.log - OK No damaged log files were found. Resolution. Seeding large mailbox databases can potentially take a long time. I have the ContentIdexState of Active and passive database copy of a mailbox database in ‘FailedandSupended’ and ‘Crawling’ State respectively.