I want to express that you are greatly appreciated! Has anyone had to do this? Have I missed an obvious article for such a process? ![]() My reasoning for disabling services on the other two DAG server is to not have them attempt to auto-start/build while trying to get a clean index made on the active server. When complete, repeat the index delete on the remaining two DAG server, enable/restart services and let them complete. In my mind, I think you would just stop the MSExchangeFastSearch/HostControllerService(s) on all 3 members, disable the services on the two non-active members, remove the index on the active server and then let it re-build on service restart. I haven’t found anything yet but my google-fu is a bit lacking since I’ve working other issues related to this restore. In a case where Exchange lists the content index as healthy and you have a DAG, what should be the correct steps to re-build the content index from scratch? I don’t want it attempting to copy over an index from the other DAG servers since they all have same ‘healthy’ but unsearchable indexes. ![]() It’s been advised to rebuild the content index from scratch. Exchange shows the content index as healthy for all DAG servers containing the database copy. Running a test-exchangesearch from EMS reports time outs/errors and Outlook searches are inconsistent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |