Configure the SharePoint Search topology

installed on a single server SharePoint Server , and a default search topology is created Search Service application. In the default search topology, all search components are located on the server that hosts central administration. Search in SharePoint is very powerful, but the resources you consume are huge. Therefore, it is very necessary to plan the SharePoint search topology reasonably under the condition of hardware .

to plan the topology of your search, it is important to understand SharePoint Farm topological structure.

• SharePoint Farm Installation Guide-Build a two-tier SharePoint Farm
• SharePoint Farm 3-tier implementation solutions for topologies

PlanningSharePointSearch Topology

was the one I implemented last year. SharePoint Farm and Will Database and the SharePoint the separation :

In the default search topology, all search components are located on the server that hosts central administration and go to SharePoint Central Administration you can see exactly, such as the default Search application topology:

Now we need to configure the search on this basis, taking into account SharePoint search requires a lot of resources, so add one more APP server, which is used to host searches and other Service Application role, the topology is as follows:

where the query processing component is used to process the user's request, I deploy him to the WFE server, and in order to improve performance and efficiency, I also deployed the index component to the WFE on the server.

as a result of the newly added APP The server has very strong performance and will host the following search components

• Analysis Processing components
• Content Processing Components
• Crawl Components
• Search Administration Components

Change the default search topology

1. Preparatory work

SharePoint Changing the default search topology must use the PowerShell , in Central Administration the interface is not available.

First you perform PowerShell (i.e. landing OS account) must be one of the following:

• is a Farm Administrators members of the group
• is a Search Service Application the Administrator

And make sure that no crawls are started and that the search index is empty.

Details: Https://technet.microsoft.com/zh-CN/library/jj862356.aspx#begin

1. Mobile Search Components

If you want to move the search component from one server to another, add a new search component to the search topology before you delete the old search component.

The following steps are described:

• Clones the active search topology.
• Add the new search component to the server for which you eventually want to host this search component.
• Activates the search topology. This topology will have an unnecessary search component.
• ensure that the current active topology is functioning correctly. View the status of the search topology or run Windows PowerShell cmdlet get-spenterprisesearchstatusin the Search administration page in Central administration.
• Clone the search topology again.
• Remove unnecessary search components.
• Activate the search topology again.

Full- PowerShell as follows:

add-PSSnapin Microsoft.SharePoint.PowerShell#1. Cloning an active search topology$ssa=get-spenterprisesearchserviceapplication$active=get-spenterprisesearchtopology-searchapplication$ssa-Active$clone=new-spenterprisesearchtopology-searchapplication$ssa-clone-searchtopology$active #The status of the new search topology is not activated at this time#2. Add a new search component to the server for which you eventually want to host this search component$app= Get-spenterprisesearchserviceinstance-identity"Your APP Server Name"#new-spenterprisesearchadmincomponent-searchtopology $clone-searchserviceinstance $app 01##new-spenterprisesearchcrawlcomponent-searchtopology $clone-searchserviceinstance $app 01##new-spenterprisesearchcontentprocessingcomponent-searchtopology $clone-searchserviceinstance $app 01#New-spenterprisesearchanalyticsprocessingcomponent-searchtopology$clone-searchserviceinstance$app#3. Launch the search Service Instance on the app serverStart-spenterprisesearchserviceinstance-identity$app#4. Activating the search topologySet-spenterprisesearchtopology-identity$clone#5. Cloning the search topology again because it cannot be followed in the current search topology state for active$ssa=get-spenterprisesearchserviceapplication$active=get-spenterprisesearchtopology-searchapplication$ssa-Active$clone=new-spenterprisesearchtopology-searchapplication$ssa-clone-searchtopology$active#6 Get the component ID to be removed$component=get-spenterprisesearchcomponent-searchtopology$clone-identity"Your Component Name"$componentId=$component. ComponentID#7. Remove the search componentRemove-spenterprisesearchcomponent-identity$componentId. Guid-searchtopology$clone-confirm:$false#activate the newly created search topology againSet-spenterprisesearchtopology-identity$clone

You can use the following PowerShell to add a search component

• New-spenterprisesearchadmincomponent
• New-spenterprisesearchanalyticsprocessingcomponent
• New-spenterprisesearchcontentprocessingcomponent
• New-spenterprisesearchcrawlcomponent
• New-spenterprisesearchqueryprocessingcomponent

after performing the above PowerShell after the script, the default search topology is changed to enter Central Administration a look at what :

can see App Server A resource-intensive search component, and the query Processing component and index component are in the same Server improves performance.

Summary

After configuring the search topology, you can confidently crawl the network, specifically, you can refer to this article-

Explore The SharePoint search feature

Configure the SharePoint Search topology