Condividi tramite

SharePoint 2013 Search IO critical component locations

  • Articolo

While working with a customer I found an undocumented (on TechNet anyways) bit of information on where SharePoint 2013 keeps Indexing files, Analytic report and link databases and crawler / gatherer temp files.

This blog will help you understand where those files are and how to change them.

 

TechNet reports on hardware recommendations for Indexing and Analytics but nothing for Crawler temp files or how to make that change HERE:

Application servers hosting search components

Index component

                       
             80 GB regardless of the number of search components hosted on the server.

            500 GB additional disk space, preferably a separate disk volume/partition.

 

Analytics processing component

           
            80 GB regardless of the number of search components hosted on the server.

            300 GB additional disk space, preferably a separate disk volume/partition. This disk space is necessary for local processing of analytics data before it is written to the analytics reporting database.

 

 

Index file location, default:

C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Nodes\34357C\IndexComponentN

Analytic file location, default:

C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics_f04b3beb-ee00-4f2b-b7db-ed368ccca47f -This GUID will be different per install

Gatherer temp files were being place in two places:

C:\Program Files\Microsoft
Office Servers\15.0\Data\Office Server\Applications\gthrsvc

C:\Program Files\Microsoft
Office Servers\15.0\Data\Office Server\Applications\f04b3beb-ee00-4f2b-b7db-ed368ccca47f-crawl-0\gthrsvc  -This GUID will be different per install

This can be found in these two registry keys respectfully:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Global\Gathering Manager] TempPath

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\c96ac2e3-b2c0-4abc-aabe-e61c6546d90b -crawl-0] GathererDataPath -This GUID will be different per install

 

Currently (As of Oct and Dec 2013 CU) the only supported way to make this change is by reinstalling SharePoint 2013 server, at install time change the location of your new drive and bring the node back into your farm. There are a few scripts showing up online that make these changes on the fly but this may create issues when updating CUs. Screenshot of what this look like at install time:

Comments

  • Anonymous
    February 12, 2014
    thanks a lot for that quick question, is it a way to clean the files located in this folder C:Program FilesMicrosoft Office Servers15.0DataOffice ServerAnalyticsGUIDAEAnalyticsProcessingComponent1SearchAnalytics ?

  • Anonymous
    February 27, 2014
    The comment has been removed

  • Anonymous
    May 19, 2014
    Hi, Thank you nice information. My C drive is having a little space(4G). So I want chagen crawler tempfolder From [C:Program FilesMicrosoft Office Servers15.0DataOffice ServerApplicationsgthrsvc] to D drive. I tried change regestfile...But I could not solve this. Can i get your help? Thank you

  • Anonymous
    May 19, 2014
    I ran powershell script, But this is just create index file. crawler is using C drive as ever. need your help, Thank you.

  • Anonymous
    May 25, 2014
    Kristopher, did the SP1 change something regarding this behaviour? Is it possible to move the gatherer temp directory to another location if you have SP1 installed?

  • Anonymous
    September 07, 2014
    We recently found ourselves in the same position and were able to overcome this by creating a symlink in the default location to another drive with more space.  Symlinks are explained here: msdn.microsoft.com/.../aa365682(v=vs.85).aspx This approach takes effect outside of SharePoint so you'll need to be sure to make an equivalent link on other servers if you change your topology but this got us past the problem of our gatherer temp files growing beyond our C: drive.

  • Anonymous
    December 30, 2014
    re: Jeff Woltz I tried the symlinks, but SharePoint figured it out and deleted them.  It was pretty impressive, one minute the new location was filling up, the next the C: drive was full again.