Thanks-I have a process running now, and noderunner.exe is only using 5 to 8% cpu, so it's actually very light.
For anyone else, the link I referenced earlier will not work with Exchange 2013 as they have removed/did not include the ResetSearchindex.ps1 and associated scripts. A little more searching and I came across this: http://theucguy.net/fix-corrupted-content-index-catalog-of-a-mailbox-database-with-single-copy/ which I've done. It's currently rebuilding the index, and then since this is in a DAG, I plan to reseed the other copy when it's done crawling: http://technet.microsoft.com/en-us/library/ee633475.aspx If anyone knows of a more official procedure for 2013, please post back. -Bonnie From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, November 06, 2014 7:10 PM To: [email protected] Subject: [Exchange] RE: Rebuilding the full text index catalog You'll be fine. It is resource intensive, but it's "self-aware" of the impact and throttles itself. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller Bonnie L. Sent: Thursday, November 6, 2014 12:04 PM To: '[email protected]' Cc: Miller Bonnie L. Subject: [Exchange] Rebuilding the full text index catalog I've had a second report in a week now of a user searching items in Outlook, but they aren't showing up in search results (even though messages are there). For the first person, moving their mailbox fixed them. But I noticed the source DB on the second report is the same and I've just confirmed others in this db have the same issue, so have it narrowed to that DB. So, I'm looking at how to rebuild the full text index catalog for that db: http://technet.microsoft.com/en-us/library/aa995966(v=exchg.80).aspx I'd like to use the online ResetSearchIndex.ps1, as it looks like you only have to run it once for a db in a DAG. For those of you who've used this before: 1) About how long might I expect this to take to run, as someone commented it can be resource-intensive on the server? This DB is 87GB right now. 2) Would it speed anything up or improve performance on other DBS not being repaired to move them the other server while this one is being re-indexed? We have 6 DBs on each server in normal operation, but all 12 can run from one if needed. 3) How will I know it's done? Just check EAC for the Content index state to be Healthy, or are there any PS commands to better monitor the status? Thanks, Bonnie
