SharePoint 2013 Search - Crawl and FeedGP0|#716ae74d-8cf7-4cac-bfc0-a9a044456284;L0|#0716ae74d-8cf7-4cac-bfc0-a9a044456284|Crawl;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#0b83bd4b-e1d8-4db2-b273-ee9f3f2efb1a;GPP|#a5205c2f-ad79-446f-8d9e-afd0eeecf427;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​This blog series will go through what's changed with Crawl and Feed and more details about what components make up the Crawl and Feed portion of a crawl. I'll write about how these components work together plus Architecture and Scaling these components.
Best practices for crawling in SharePoint Server 2013GP0|#716ae74d-8cf7-4cac-bfc0-a9a044456284;L0|#0716ae74d-8cf7-4cac-bfc0-a9a044456284|Crawl;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#0b83bd4b-e1d8-4db2-b273-ee9f3f2efb1a;GPP|#a5205c2f-ad79-446f-8d9e-afd0eeecf427;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 The Search system crawls content to build a search index that users can run search queries against. This article contains suggestions as to how to manage crawls most effectively.
Troubleshooting SharePoint Search CrawlGP0|#716ae74d-8cf7-4cac-bfc0-a9a044456284;L0|#0716ae74d-8cf7-4cac-bfc0-a9a044456284|Crawl;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#0b83bd4b-e1d8-4db2-b273-ee9f3f2efb1a;GPP|#a5205c2f-ad79-446f-8d9e-afd0eeecf427;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​Every once in a while SharePoint Crawler will behave unexpectedly on web sites that you wish to crawl. You may get error messages that you can understand and help you troubleshoot the problem or you will get just one error that is not helpful at all. Either way, I have found that you can troubleshoot the crawl by using the following technique with Fiddler Web Debugging Proxy
SharePoint 2013 Crawler Troubleshooting ConceptsGP0|#716ae74d-8cf7-4cac-bfc0-a9a044456284;L0|#0716ae74d-8cf7-4cac-bfc0-a9a044456284|Crawl;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#0b83bd4b-e1d8-4db2-b273-ee9f3f2efb1a;GPP|#a5205c2f-ad79-446f-8d9e-afd0eeecf427;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 If you take a step back and view SharePoint 2013 crawling problems at a 32,000 foot level it is broken down into two main areas Repository (content) delay or locks (and everything between the gatherer and repository, for example networking). Performance problems based on backend resourcing issues. This post will focus on #2 the backend resources.
Stop CrawlingGP0|#716ae74d-8cf7-4cac-bfc0-a9a044456284;L0|#0716ae74d-8cf7-4cac-bfc0-a9a044456284|Crawl;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#0b83bd4b-e1d8-4db2-b273-ee9f3f2efb1a;GPP|#a5205c2f-ad79-446f-8d9e-afd0eeecf427;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213;GP0|#e076f06d-face-4c15-b118-1c910704bfbb;L0|#0e076f06d-face-4c15-b118-1c910704bfbb|PowerShell;GPP|#416f8251-f4d5-40dc-be28-d7400d10de85 ​If you want to clone the search topology in order to change it, you must stop all crawling activity.