This blog post will show you how fix the status of an Exchange Server Database content Indexing from crawling to healthy state.
Before you start don’t forget to read how to:
- Monitor Exchange 2013 DAG
- Monitor Exchange 2010 DAG
- Install Exchange Server 2016 CU2 In Unattended Mode
The first step is to find out which databases are affected by running the cmdlet below:
Get-MailboxDatabaseCopyStatus * | where {$_.ContentIndexState -eq "crawling"}
Once confirmed Stop and start the “Microsoft Exchange Search Indexer” Service.
Next you can leave Exchange sync the content search Index or you can start the process manually by running the cmdlet below (You need to use the passive copy):
Update-MailboxDatabaseCopy "MBX\ExchangePassiveServer" -CatalogOnly
If you want to monitor the indexing status open Performance monitor on the passive server and select the settings below from the MSExchange Search Indexer and indices
You can also use this fix to fix Exchange Databases Content Index status set to failed.