Fixing Search/Indexing issues within Exchange 2019 mailboxes.

Exchange 2013/2016 Search/Indexing

DB13 GUID
DB13 Catalog indexing folder

Problem Statement

  • Rebuilding a failed search index might take a long time, in case users are working in Outlook Online mode or OWA, they will not be able to get any results in case of search queries.
  • During the indexing rebuilding, eDiscovery and the Search-Mailbox activities also will not get any results, related to mailboxes located on the database where the catalog is getting fixed.
  • Rebuilding the whole catalog indexing requires an intensive I/O and CPU resources from the server.
  • Moving mailboxes between databases will cause reindexing the mailboxes again at the target databases and removing the moved mailbox indexing from the source database.
    This might be critical where mailboxes are having a very high number of items.
  • Moving mailboxes will cause not only reindexing the target database copy but also all other copies of the same database.

Exchange 2019 Indexing

  • Rebuilding a failed search index will be faster
  • Moving mailboxes between databases will NOT cause reindexing the mailboxes again at the target and source databases since the moved mailbox already indexed!
  • Moving mailboxes won’t cause reindexing all the copies since indexing is builtin inside the mailbox!

How to check indexing issues in Exchange 2019?

  • Please note that Exchange 2019 CU5 fixed search issues with previous Exchange 2019 versions:
    “Cumulative Update 5 for Exchange Server 2019 is also required to fix a known issue with partial word searches when the client is using Outlook in online mode.”

How indexing is getting fixed in Exchange 2019?

  1. According to the video from Microsoft Ignite session BRK3130 you can use the Start-MailBoxAssistant command, which is available from Exchange 2019 CU11:
  • New-SettingOverride -Name “Big Funnel Permanent Retry” -Component “BigFunnel”
    -Section “BigFunnelFailedItemsQuerySettings”
    -Parameters @(“ExcludePermanentFailures=false”)
    -Reason “Re-Index Messages” -MinVersion “15.2.922.7” -MaxVersion “15.2.986.22”
  • Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

Conclusions:

--

--

--

During the last 14 years, I was working as a Senior PFE within Exchange area at Microsoft. Now I’m Senior Consult as Azure IAAS, PowerShell & Automations.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Why Python & Django Are Your Top Choice for Web Development

2020 Double 11 Highlights: Large Deployment of Cloud-Native Technology for Higher Efficiency and…

Getting started with the Salesforce CPQ Quote Calculator Plugin (QCP) VSCode Extension

day 9 of 30/June challenge/leetcode

How Much Does It Cost To Develop An App in 2021? Popular Startups With Mobile Apps.

Well, let me introduce you a very promising projects guys.

How to become a web developer — Without a degree

Project 1: The Emoji Story — from 😥to 😁

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tzahi Kolber

Tzahi Kolber

During the last 14 years, I was working as a Senior PFE within Exchange area at Microsoft. Now I’m Senior Consult as Azure IAAS, PowerShell & Automations.

More from Medium

The G-Story Test

Time is a sort of Paste

Everything is a setback

Do Architects Dream of Making Sandcastles?