Changing Search Topology in SharePoint 2013 - Run all 6 components in 2 App Servers

Ref Links:

This link is to split and run across 4 servers
https://technet.microsoft.com/en-us/library/jj862356(v=office.15).aspx

This link is to run same 6 components in 2 servers
http://blog.fpweb.net/modify-search-topology-in-sharepoint-server-2013/


$hostA = Get-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP2APP01"
$hostB = Get-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP2APP02"
Start-SPEnterpriseSearchServiceInstance -Identity $hostA
Start-SPEnterpriseSearchServiceInstance -Identity $hostB


Get-SPEnterpriseSearchServiceInstance -Identity $hostA
Get-SPEnterpriseSearchServiceInstance -Identity $hostB

$ssa = Get-SPEnterpriseSearchServiceApplication
$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa


New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostA -IndexPartition 0

New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostB -IndexPartition 0

Set-SPEnterpriseSearchTopology -Identity $newTopology

Get-SPEnterpriseSearchTopology -SearchApplication $ssa

Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Text


Now stop in the other app servers

Stop-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP1APP01" (Where central admin is present)
Stop-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP1APP02" (Where central admin and other services are running)

$ssa = Get-SPServiceApplication –Name “Search Service Application”
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
Get-SPEnterpriseSearchComponent -SearchTopology $active

The above 3 cmdlets are for finding index location, if the RootDirectory is not returning any results, then run the below 2 cmdlets


$ssa = Get-SPEnterpriseSearchServiceApplication
$ssa.AdminComponent.IndexLocation

This should show the correct Path. If you are not happy with this path, then run the below command to set the Index location to a drive which has more space.

Set-SPEnterpriseSearchServiceInstance -DefaultIndexLocation "D:\SP Search Index"


Comments

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp
Read more

NAV 2009 Issues in Role Tailored Client

Image
Role tailored client issue Changing stored procedure to 64 bit in NAV 2009 Did install Dynamics NAV 2009 on windows 2008 64 bit / Windows 7 65 bit. When trying to connect to the database in classic client I got this error. The following SQL server error or errors occurred: 17750,“42000”,[Microsoft][ODBC SQL Server Driver][SQL Server]Could not load the DLL C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database\xp_ndo.dll, or one of the DLLs it references. Reason: 193(failed to retrieve text for this error. Reason: 15100). SQL: INSERT INTO [#$ndo$groups] {CALL [master]..[xp_ndo_enumusergroups](?,?)} The reason for this error is that the installed xp_ndo.dll is 32 bit and not 64 bit. My solution was simple to replace xp_ndo.dll with the 64 bit version. 1. Stop SQL server 2. Copy \\vedfssrv01\DynamicsNAV2009\W1\DVD\Sql_esp\x64\ xp_ndo_x64.dll to C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database 3. Rename existing xp_ndo.dll to xp_ndo_x32.dll 4. Rename xp
Read more