SharePoint Serch Service resources

 

 

Move SharePoint 2013 Search Index LocationGP0|#1a8f085c-40e9-4a01-b25b-abeddf498837;L0|#01a8f085c-40e9-4a01-b25b-abeddf498837|Search Service;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#aa2447c2-0307-4407-bd59-fedab9e12903;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​SharePoint 2013 makes heavy use of the file system for the Index Partition. By default this is placed on the system drive. You should plan to use a dedicated drive for the partition and it must exist as the same drive letter on any replica servers. 100Gb per TB of content is a rough estimate of the sapce required. This script will let you move it if it is only deplyed to one server.
Changing search topolgy causes disk space to be consumed until it runs outGP0|#1a8f085c-40e9-4a01-b25b-abeddf498837;L0|#01a8f085c-40e9-4a01-b25b-abeddf498837|Search Service;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#aa2447c2-0307-4407-bd59-fedab9e12903;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213
Configuring Search Service Application and Topology using PowerShellGP0|#1a8f085c-40e9-4a01-b25b-abeddf498837;L0|#01a8f085c-40e9-4a01-b25b-abeddf498837|Search Service;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#aa2447c2-0307-4407-bd59-fedab9e12903;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 ​This article shows how to configure topology for one search service application with multiple search components across 2 servers for redundancy and performance.