New answers tagged crawling
I would do the following: priorize the incremental crawl with "high" priorize the new content source with "low" limit the requests to the new site in crawler impact rules start the crawl on friday night and pause it on monday - repeat until you have the main chunk indexed (use powershell to automate) With this the impact should not be that hard.
This isn't really possible without having multiple farms each with a separate Search Service Instance. I would suggest you basically split out your 1.5TB of content into a separate farm with a dedicated Search instance. You can even use HOSTS entries on the crawl servers so they have their own local dedicated WFE servers for the crawl process to iterate ...
Have you looked at adding an XML iFilter? Depending on the coding you could index the values and would be a crawled property. The other alternative would be to write a Content Processing Callout. Register the callout trigger for FileExtension="config" and you can perform the processing yourself.
Top 50 recent answers are included