Wednesday , October 23 2019

Rebuild an Index on Exchange 2013/2016 for Specific Databases

Let see how to rebuild and Content Index on Exchange 2013/2016 if the content index of the primary database went to a bad shape.

Note : This process takes more I/O on your disk . and increases the load on the server. if you have multiple databases on the same disk/server. Consider doing one by one.

If the Content index of the DAG copy failed you can run

Update-MailboxDatabaseCopy  "DBname\Servername" –CatalogOnly

If the Content index of the primary DB failed

Get-MailboxDatabaseCopyStatus -Server EXCH2016A | fl

ExtendedErrorInfo                     :
SuspendComment                        :
RequiredLogsPresent                   :
SinglePageRestore                     : 0
ContentIndexState                     : FailedAndSuspended
ContentIndexErrorMessage              : The content index is corrupted.

ContentIndexErrorCode                 : 19
ContentIndexVersion                   :
ContentIndexCrawlVersion              :
ContentIndexBacklog                   :
ContentIndexRetryQueueSize            :

 

Stop below Exchange Services –

Microsoft Exchange Search  – MSExchangeFastSearch

Microsoft Exchange Search Host Controller – HostControllerService

image

Go to the affected database location – Move the Catalog folder to a different location –

Start the above services back.

image

Content Index will kick off (This process takes time)– going to unknown –> Crawling –> Healthy.

image

image

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Office Server and Services MVP , Publisher of Azure365pro.com. Specialized in Office365 / Microsoft Exchange / Virtualization , Sathesh is an Messaging Expert supporting/Designing/Deploying many medium size businesses to large enterprises when it comes to Corporate messaging and Virtualization Infrastructure

Check Also

Save Public IPs using F5 LTM Policies

F5 has different modules and one of them is LTM – Local Traffic Manager . ...

5 comments

  1. Hi Satheshwaran, could you please at my post below and help me with Exchange Search.

    I’m running Exchanging 2013 with two mailbox servers in a DAG. Get-MailboxDatabaseCopyStatus * showed both servers in FailedAndSuspended state. I think this issue occurred after I extended disk space on the mailbox servers. I tried Update-MailboxDatabaseCopy -CatalogOnly but that didn’t help I presume as there was no Heatlty copy present.

    On the passive node I stopped Exchange Search and Exchange Host Controller service, renamed .single to .single.old and started the service again which created a new folder. But state was still showing FailedAndSuspended, so I tried to do same on the Active node and upon service start status was changed to Crawling on active node and passive was still showing FailedAndSuspended.

    It took more than 24 hours and status was changed from Crawling to Failed on Active node. Then again on the passive node I stopped and started Exchange Search and Exchange Host Controller service, after a while status was changed from Failed to Crawling and then to Healthy. Once status was healthy then I ran MailboxDatabaseCopy -CatalogOnly which made the active node healthy as well.

    Now the issue which I’m facing is that search still isn’t working other than recent emails (1 day old emails)

    .single.old size is showing as 30 GB while new folder .single is showing only 6 GB. Is there any possible solution I could fix the search issue?

    Could you please help me to resolve this.

    Regards,

    Mobin

Leave a Reply

Your email address will not be published.