ContentIndexState AutoSuspended for lagged copies

Your Exchange 2016 lagged copies may stopped being indexed with ContentIndexState AutoSuspended after applying recent CU4
You may also see these events :
ID:       1009
Level:    Warning
Source: MSExchangeFastSearch
Message :
The indexing of mailbox database <mailboxdatabase> encountered an unexpected exception.
Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed.
---> Microsoft.Exchange.Search.Core.Abstraction.CatalogReseedException:
The database 'guid (<mailboxdatabase>)' needs to be crawled but is not mounted on the preferred active server. Requesting a reseed.
at Microsoft.Exchange.Search.Engine.SearchFeedingController.DetermineFeederStateAndStartFeeders()
at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()
at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)"

This is in fact expected behavior to Autosuspend lagged copies when possible.
This change allows to save network bandwidth by suspending such index which would likely not be used.

I would recommend to keep this normal behavior.
But if for some reason you require such database to be indexed , you can use this command to block this feature and index all databases as in CU1 :
New-SettingOverride -Name DisableSkipLagCopyForOnPrem2016 -Component Search -Section SkipLagCopy -Parameters @("Enabled=false") -Reason "Disable SkipLagCopy"

Comments (1)

  1. DDog80sRocked says:

    We have this exact “issue” after updating Exchange 2016 servers from CU2 to CU4. I can’t seem to find anything in the release notes or other blogs anywhere mentioning this. Is there a way to have Microsoft confirm this via a document or announcement?

Skip to main content