Blog Archive » SharePoint 2013 Moving the Search Query Component to a WFE SharePoint 2013 Moving the Search Query Component to a WFE Colin Phillips (Regroove Alumni). After doing the following steps and checked search components, I found only crawled components moved successfully and others are suspended. After investigations I remembered, We did memory limitations for Fixing Performance Issue Caused By Node Runner In SharePoint 2013. Memory limitations prevent creation of new search components successfully.
I've done this a number of times, and have used a variety of others (blog) posts to do this in the past, some of which have gone offline since I first started using them, as such, I wanted to keep track of how to do this for myself, so I've gone ahead and grabbed the PowerShell from the following blog post.
Many thanks to Steve Mann for this post, and I truly appreciate your efforts in figuring out the proper PowerShell to do this correctly.
Step #1 – Clone the Active Search Topology
# Clone the active search topology
$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active Red alert 2 installer windows 10.
Step #2 – Add the New Search Component on the WFE
# Add New Search Component
$wfe = Get-SPEnterpriseSearchServiceInstance -Identity '[[web front end server name here]]'
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $wfe
Sharepoint Online Client Components
Step #3 – Start the Search Instance on the WFE
# Start Instance On Different Server
Start-SPEnterpriseSearchServiceInstance -Identity $wfe
Step #4 – Activate the Cloned Search Topology
# Activate Search Topology
Set-SPEnterpriseSearchTopology -Identity $clone
Step #5 – Clone the Search Topology Again
# Clone Again
$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active
Step #6 – Get the ComponentID to Move
# Get the Search Component ID To Move
$queryComponentID = (Get-SPEnterpriseSearchComponent -SearchTopology $clone -Identity QueryProcessingComponent1).componentID
Step #7 – Remove the Search Component from the Original Server
# Remove Search Component
Remove-SPEnterpriseSearchComponent -Identity $queryComponentID.GUID -SearchTopology $clone -confirm:$false
Step #8 – Activate the Search Topology Again
# Activate Search Topology Again
Set-SPEnterpriseSearchTopology -Identity $clone
Again, all the credit to Steve Mann, much appreciated.
SharePoint 2013 – Restore Search Service Application on different Server or Farm
With the following steps you can restore an existing Search Service Application on a different Server or Farm.
For example if like to restore your Search Service Application from your Producion environment (PRD) farm to a development (DEV) farm.
Overview:
- Restore the Search Service Application databases from your source SQL server (e.g. Production) to the target SQL server. (e.g. Development)
Required Databases: AdminDb, AnalyticsReortingStore, CrawlStore, LinkStore (or only AdminDb depending on your needs)
- There are two ways to restore an Search Service Application.
– Method1: Restore Search Service Application with a new default topology
– Method2: Restore Search Service Application with a given predefined topology (e.g. exported from your Production farm and modified for your requirements in your DEV farm)
My suggestion is using Method2 in Step2. Because then you can define the path for your Search Service Index Location etc…
See the example from an topology.xml at the bottom of this blog post.
Step1:
Use your SQL Management Studio or an script to complete that task.
Step2-Method1: (New default Search Topology)
Step2-Method2: (Given predefined Search Topology)
Attention: Change the server names and SQL server name in the exported search topology to the names in your DEV environment
Components Of A Sharepoint Site
Last but not least check and modify the Search Content Sources in your restored Search Service Application –> Search Administration to the URLs from your DEV environment.
Step #8 – Activate the Search Topology Again
# Activate Search Topology Again
Set-SPEnterpriseSearchTopology -Identity $clone
Again, all the credit to Steve Mann, much appreciated.
SharePoint 2013 – Restore Search Service Application on different Server or Farm
With the following steps you can restore an existing Search Service Application on a different Server or Farm.
For example if like to restore your Search Service Application from your Producion environment (PRD) farm to a development (DEV) farm.
Overview:
- Restore the Search Service Application databases from your source SQL server (e.g. Production) to the target SQL server. (e.g. Development)
Required Databases: AdminDb, AnalyticsReortingStore, CrawlStore, LinkStore (or only AdminDb depending on your needs)
- There are two ways to restore an Search Service Application.
– Method1: Restore Search Service Application with a new default topology
– Method2: Restore Search Service Application with a given predefined topology (e.g. exported from your Production farm and modified for your requirements in your DEV farm)
My suggestion is using Method2 in Step2. Because then you can define the path for your Search Service Index Location etc…
See the example from an topology.xml at the bottom of this blog post.
Step1:
Use your SQL Management Studio or an script to complete that task.
Step2-Method1: (New default Search Topology)
Step2-Method2: (Given predefined Search Topology)
Attention: Change the server names and SQL server name in the exported search topology to the names in your DEV environment
Components Of A Sharepoint Site
Last but not least check and modify the Search Content Sources in your restored Search Service Application –> Search Administration to the URLs from your DEV environment.
Tip: If continuous crawling was enabled then you first need to disable continuous crawling to be able to change the URLs.
TechNet Source: Link
Example: topology.xml for an Search Service Application with 2 Search / Application Servers
Sharepoint 2013 Move Search Components Free
