SharePoint 2013/2016 – migrating search service to another server

Moving search service from one to another server in SharePoint – is typical task, that always happens on old and large projects. If you cannot scale old search app server resources, only one way to make it works properly – move service to another, more powerful server. This instruction will help you to do that.

Existing Topology:

SharePoint 2016 farm:

• WEB – Web Server (FrontEnd, …)
• APP – Application Server (SearchService, …)
• APP-2 – New Application Server (SearchService, …)
• …

Task:

Move SearchService from APP to new and more powerful computer APP-2

Instruction:

1. Clone existing search topology. Use this instruction in powershell:
   
   PowerShell

   $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone -SearchTopology $active

   1 2 3

   $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone -SearchTopology $active

2. In virtual clone of service topology ($clone) add new search components:
   • New-SPEnterpriseSearchAdminComponent
     
     PowerShell

     New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

     1 2	New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

   • New-SPEnterpriseSearchAnalyticsProcessingComponent
     
     PowerShell

     New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

     1 2	New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

   • New-SPEnterpriseSearchContentProcessingComponent
     
     PowerShell

     New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

     1 2	New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

   • New-SPEnterpriseSearchCrawlComponent
   • PowerShell

     New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

     1 2	New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

   • New-SPEnterpriseSearchQueryProcessingComponent
     
     New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

     1 2	New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance <GUID> # <GUID> - id of SearchService on new application server

   • New-SPEnterpriseSearchIndexComponent
     
     PowerShell

     New-SPEnterpriseSearchIndexComponent -SearchTopology $clone -IndexPartition 0 -SearchServiceInstance <GUID> -RootDirectory <PATH> # <GUID> - id of SearchService on new application server # <PATH> - local path where search index will be stored on new app server # example: C:\SearchIndex

     1 2 3 4

     New-SPEnterpriseSearchIndexComponent -SearchTopology $clone -IndexPartition 0 -SearchServiceInstance <GUID> -RootDirectory <PATH> # <GUID> - id of SearchService on new application server # <PATH> - local path where search index will be stored on new app server #    example: C:\SearchIndex

3.  Activate new search topology
   
   PowerShell

   Set-SPEnterpriseSearchTopology -Identity $clone

   1	Set-SPEnterpriseSearchTopology -Identity $clone

   And verify, is new topology set correct:
   
   PowerShell

   Get-SPEnterpriseSearchTopology -Active -SearchApplication $ssa

   1	Get-SPEnterpriseSearchTopology -Active -SearchApplication $ssa

4. Check is everything correct in SharePoint Central admin. Go to Search Service Application administration and take a look at top menu, with service topology. There will be 2 equal app servers with the same search components.
5. Clone search topology again (step 1)
6. Remove search components located on old app server:
   • SearchAdmin
   • SearchAnalytics
   • SearchContent
   • SearchCrawl
   • SearchQuery
   • SearchIndex
     
     PowerShell

     Remove-SPEnterpriseSearchComponent -Identity <GUID> -SearchTopology $clone # <GUID> - id of old search service component

     1 2	Remove-SPEnterpriseSearchComponent -Identity <GUID> -SearchTopology $clone # <GUID> - id of old search service component

7. Activate search topology again (step 3)
8. Check (step 4). Now there will be only one search server (new APP-2).
9. Run full craw in SharePoint Admin Center -> Search Application Management -> Content Sources

 

administration powershell searchservice sharepoint