{"id":1048,"date":"2018-09-03T16:29:13","date_gmt":"2018-09-03T14:29:13","guid":{"rendered":"http:\/\/dety.net.ua\/?p=1048"},"modified":"2018-09-03T16:29:13","modified_gmt":"2018-09-03T14:29:13","slug":"fix-all-failed-exchange-database-content-indexes","status":"publish","type":"post","link":"https:\/\/dety.net.ua\/?p=1048","title":{"rendered":"Fix All Failed Exchange Database Content Indexes"},"content":{"rendered":"

Source:https:\/\/practical365.com\/exchange-server\/fix-all-failed-exchange-database-content-indexes\/<\/a><\/p>\n

One of the issues that my Get-DAGHealth.ps1<\/a> script alerts for is failed content indexes on database copies in a database availability group.<\/p>\n

Note: for failed content indexes on servers that are not DAG members refer to this article<\/a> instead.<\/em><\/p>\n

Failed content indexes can easily go unnoticed when everything else is working fine however they will eventually begin to cause problems for you, for example by preventing database switchovers<\/a>.<\/p>\n

Fixing a single failed content index is easy, but if there are multiple failed indexes you can speed things up a little by fixing them all with a single PowerShell command.<\/p>\n

To demonstrate, here is the Exchange Management Shell command for using Get-MailboxDatabaseCopyStatus<\/a> to display all database copies that have a content index in a failed state.<\/p>\n

\n
\n
\n
\n
<\/div>\n<\/div>\n
\n
<\/div>\n<\/div>\n
\n
<\/div>\n<\/div>\n
\n
<\/div>\n<\/div>\n
\n
<\/div>\n<\/div>\n
\n
<\/div>\n<\/div>\n<\/div>\n<\/div>\n