Sharepoint 2013 Move Search Components

| Posted on by

SharePoint 2013 – Restore Search Service Application on different Server or Farm
Sharepoint 2013 Move Search Components

Search Engine Optimization functionality of SharePoint 2013 is provided as a single functional unit. When you enable the SearchEngineOptimization Feature you will deploy all Site Columns, enable the UI and activate all Delegate Controls. By default there is no way for you to choose which components you would like to use. SharePoint 2013 Move Search Components to Another Server To move SharePoint search components from application server to dedicated search server, need to run following PowerShell command. Before you run any command, please make sure that the current environment has following topology Clone Search Service Application. SharePoint 2013 - Search https. Recommended move query component but I've read another blog post which recommend to move Index partitions as well to improve.

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.

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:

  1. 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)

  2. 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

Sharepoint 2013 Move Search Components

Sharepoint 2013 Move Search Components To Another Server

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.

ComponentsSharepoint 2013 move search components to another server

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

Share
With this post I’ll try to explain the complete step-by-step guide how to check and change Search Index Location in SharePoint 2013. Unfortunately in internet I found different posts but non of them was complete
For one of our customers we have to check Search Index Location and I found this post , great I’ll find very easy the location. BUT I was surprised when I got the result in Power Shell:
  • $ssa = Get-SPServiceApplication –Name “Search Service Application”
  • $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
  • Get-SPEnterpriseSearchComponent -SearchTopology $active | ?{$_.Name -like “*index*”}
Sharepoint online client components
Root directory is empty in my case, in the aforementioned post I could not find what actually this means.
Another post stated that with only 2 Power Shell commands I’ll get the necessary for me information. The result after execution was:
OK looks like the location is the default search index location and I’ve to change it.

Sharepoint Online Client Components

Found one very useful Power Shell script which I highly recommend to use in case you would like to change index location. The only thing you have to change at the bottom of the script are:
  • SearchServiceName
  • Server (name)
  • Index Location (suggestion use non system drive)

Execution on my servers finished with success.

Then I would like to check index location again and executed again:

  • $ssi = Get-SPEnterpriseSearchServiceInstance
  • $ssi.Components

And SURPRISE the Index Location was the same … C:Program FilesMicrosoft Office Servers15.0DataOffice ServerApplications … I can’t believe it.

Then I executed the first 3 cmdlets and now the result is a bit different:

Actually the changes are here 🙂

Conclusion

If you would like to check your Search Index Location in SharePoint 2013 you need the following power shell commands:

Sharepoint 2013 Move Search Components Free

  1. $ssa = Get-SPServiceApplication –Name “Search Service Application”
  2. $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
  3. Get-SPEnterpriseSearchComponent -SearchTopology $active | ?{$_.Name -like “*index*”}

In case RootDirectory is empty that means your search index location is the default location – C:Program FilesMicrosoft Office Servers15.0DataOffice ServerApplications, if it shows something different like D:SearchIndex this is you index location

I hope you will find this post usefull!

Sharepoint Move Files

Article from: http://pavlovsp2013.blogspot.ca/2015/05/search-index-location-sharepoint-2013.html