Yesterday we patched one of our exchange 2013 CU23 servers due to the new exploit reported by MS, after doing so, we noticed that the newly patched server's content index state was showing as FailedAndSuspended.
Having misread an article, tried re-seeding the catalog for this particular database from the unpatched server back to itself which resulted in both showing as FailedAndSuspended. Unfortunately the database is our Public Folder database which is heavily used. Searching does not working unless you search by From:"xyz" or Subject:"xyz".
The server which has the DB mounted (unpatched) showed crawling after sometime, then this morning showed as FailedAndSuspended and has since started crawling again.
Need to get this fixed by Monday, can anyone help?