reindex, BigFunnelCorruptedCount

Андрей Михалевский 3,451 Reputation points
2024-01-15T07:07:08.3033333+00:00

Hello. Exchange 2019. On-premise. After the crash, mailboxes were restored via Veeam. Users started complaining that the search was not working properly.

PS C:\Users\user> Get-MailboxStatistics ******@domain.ru | fl BigFunnelCorruptedCount
BigFunnelCorruptedCount: 151625

After moving the box to a different base, the search works fine.

PS C:\Users\user> Get-MailboxStatistics ******@domain.ru | fl BigFunnelCorruptedCount
BigFunnelCorruptedCount: 0

https://support.microsoft.com/en-us/topic/incomplete-search-results-after-installing-an-exchange-server-2019-update-96ae2ef0-4569-4327-8d0c-8a3c1abdc1f6 I found this article, ran the commands:

New-SettingOverride -Name "Big Funnel Permanent Retry" -Component "BigFunnel" -Section "BigFunnelFailedItemsQuerySettings" -Parameters @("ExcludePermanentFailures=false") -Reason "Re-Index Messages"

Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

Start-MailboxAssistant -Identity "user" -AssistantName BigFunnelRetryFeederTimeBasedAssistant

But the indexing is not done.

Exchange | Exchange Server | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2024-01-15T08:47:48.51+00:00

    Hello Андрей Михалевский

    Normally you just need to move it to another database.

    Did any errors occur when you ran the above command? Just noticed something different, are you missing the Build Number part?

    User's image

    Regards SF


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.