Consider this. You need to run an eDiscovery query for a legal discovery and the data returned does not match what was expected. For example, the results do not include any data from the past month or so. Here is what we used to troubleshoot why data was missing:
1) Run the query from the EAC in Exchange 2013 – change the date range, change mailboxes… basically change the criteria for the search to verify the results are consistent.
In our case the results were consistently missing the past one month of results.
2) Run the query with PowerShell like the following:
New-MailboxSearch -Name “Legal-Discovery” -SourceMailboxes Sales,Executives -TargetMailbox LegalDiscovery@domain.com -StartDate “01/1/2013” -EndDate “1/1/2014” -Recipients “*@domain.com” -SearchQuery “Sell high” -StatusMailRecipients “DiscoveryTeam”
Again, the results were consistently missing the past one month of results.
3) Then it occurred to me that Exchange Search is directly tied to the Content I

“In-Place eDiscovery uses the content indexes created by Exchange Search”
As such, we should check the state of the Content Index on the databases we want to search. Here’s how:

Now that we know the Content Index is failed we simply need to reseed the database. Here’s how:
Get-MailboxDatabaseCopyStatus * | where {$_.ContentIndexState -eq “Failed”} | Update-MailboxDatabaseCopy -CatalogOnly
Once the content indexes are recreated, then your eDiscovery search should work flawlessly.
Related Information
New-MailboxSearch
Update-MailboxDatabaseCopy
1 thought on “eDiscovery and Database Content Indexing”
Comments are closed.