Manage indexer failure (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Articolo
03/09/2011

Data pubblicazione: 16 dicembre 2010

If the farm deployment includes a backup indexer row, you must synchronize the indexer servers when you replace a server.

Follow these steps to replace a primary indexer server or a backup indexer server if a non-recoverable hardware failure has occurred.

To replace a failed indexer server

Pause crawling:
- If you are using the FAST Search Content SSA to crawl content, see Start, pause, resume, or stop a crawl (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese) for information about pausing a crawl.
- If you are using the Crawler Web di FAST Search to crawl content, see Start, suspend, resume, or stop a crawl process (FAST Search Web crawler)(informazioni in lingua inglese) for information about suspending a crawl.
Pause the Web Analyzer components. These components analyze links between items and search clickthrough logs. The components must be stopped to avoid partial updates for indexed items during the procedure.
1. On the administration server, open a FAST Search Server 2010 for SharePoint shell.
  1. Verify that you meet the following minimum requirements: You are a member of the FASTSearchAdministrators local group on the server where FAST Search Server 2010 for SharePoint is installed.
  2. On the Start menu, click All Programs.
  3. Click Microsoft FAST Search Server 2010 for SharePoint.
  4. Click Microsoft FAST Search Server 2010 for SharePoint shell.
2. Inspect the Web Analyzer schedule status. At the Windows PowerShell command prompt, type the following command:
```
waadmin ShowStatus
```
  Nota
  
  Refer to waadmin.exe reference(informazioni in lingua inglese) if you are using multiple views for the Web Analyzer.
  
  In the Views section of the command output, for the default view, inspect the Schedule status. If the Schedule status is set to paused, perform the following steps:
  1. At the Windows PowerShell command prompt, type the following command:
```
waadmin enqueueview
```
  2. Wait until the default Web Analyzer view is running. Type the command waadmin ShowStatus and inspect the Schedule status. The Schedule status shall be set to running.
3. At the Windows PowerShell command prompt, type the following commands:
```
waadmin AbortProcessing
spreladmin AbortProcessing
```
Wait until all item processing is finished. At the Windows PowerShell command prompt, type the following command:
```
psctrl status
```
Nota

All processor servers must report "idle" before you proceed to the next step.
Stop the indexer. On the running (not failed) indexer server, open a FAST Search Server 2010 for SharePoint shell and type the following command:
```
nctrl stop indexer
```
On the administration server, open the deployment configuration file (%FASTEARCH%\etc\config_data\deployment\deployment.xml) to view the server configuration for the index column with the failed indexer server.

%FASTSEARCH% represents the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.

Locate the host element that specifies the failed indexer. The column attribute of the searchengine element indicates the index column for this indexer.

The following example shows an extract of a deployment.xml file with the host definition for the primary and backup indexer for index column 0. The first host element specifies the primary indexer server. The second host element specifies the backup indexer server. The searchcluster element specifies which server that is the primary indexer and which server that is the backup indexer, by using the row element. Typically, row 0 corresponds to the primary indexer server.
```
<host name="fs4sp2.contoso.com">
    <content-distributor />
    <searchengine row="0" column="0" />
    <document-processor processes="12" />
  </host>
  ...
  <host name="fs4sp5.contoso.com">
    <query />
    <searchengine row="1" column="0" />
  </host>
  ...
  <searchcluster>
      <row id="0" index="primary" search="true" />
      <row id="1" index="secondary" search="true" />
  </searchcluster>
```
Reconfigure the deployment to change the indexer server configuration:
1. Determine the changes you must apply to the deployment configuration file (deployment.xml):
  - Change the host element that specifies the failed indexer server for this index column. Change the name attribute of the host element to specify the host name of the new server that will replace the failed server.
    
    Nota
    
    If you use the same host name for the new server, you do not have to modify the content of the file, but you must modify the file in order for the Windows PowerShell cmdlet Set-FASTSearchConfiguration to re-deploy the configuration. You can do that by opening the file in Notepad, add a space and save the file.
2. Follow the steps in Reconfigure the farm deployment including adding new servers.
  
  Importante:
  
  Do not restart the server that replaces the failed indexer server after you have installed and configured the server. You restart the server later in this procedure.
Copy all FiXML files between the indexer servers in the index column.
- If you have replaced the primary indexer server, copy the FiXML files from the backup indexer server (source) to the primary indexer server (destination).
- For all other cases, copy files from the primary indexer server (source) to the backup indexer server (destination).
The FiXML files are stored in the following directory on the indexer servers:

%FASTSEARCH%\data\data_fixml\
1. On the destination indexer server, create two temporary folders. At the Windows command prompt, type the following commands:
```
mkdir %FASTSEARCH%\data\data_fixml_new
mkdir %FASTSEARCH%\data\ftStorage_new
```
2. On the destination indexer server, at the Windows command prompt, copy the data_fixml folder from the source server:
```
robocopy /E /MT:100 /COPYALL /LOG:\incoming\robocopy_fixml.log <source_path>\data\data_fixml %FASTSEARCH%\data\data_fixml_new
copy <source_path>\data\ftStorage\processed_checkpoint.txt %FASTSEARCH%\data\ftStorage_new
```
  Where <source_path> is the network path of the FAST Search Server 2010 for SharePoint installation folder on the source server.
3. Swap the copied folders (%FASTSEARCH%\data_fixml_new and %FASTSEARCH%\ftStorage_new) with the old folders (%FASTSEARCH%\data\data_fixml and %FASTSEARCH%\data\ftStorage) on the destination server.
Restart the server that replaces the failed indexer server.
Start the indexer. On the running (not failed) indexer server in the affected index column, at the Windows PowerShell command prompt, type the following command:
```
nctrl start indexer
```
Resume processing for the Web Analyzer components. On the administration server, at the Windows PowerShell command prompt, type the following commands:
```
waadmin EnqueueView
spreladmin Enqueue
```
Start a full crawl of all content:
- If you are using the FAST Search Content SSA to crawl content, see Start, pause, resume, or stop a crawl (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese) for information about starting a crawl.
- If you are using the Crawler Web di FAST Search to crawl content, see Start, suspend, resume, or stop a crawl process (FAST Search Web crawler)(informazioni in lingua inglese) for information about starting a crawl.

Importante:
Do not restart the server that replaces the failed indexer server after you have installed and configured the server. You restart the server later in this procedure.

Vedere anche

Informazioni di riferimento

About FiXML files

Concetti

Manage high availability of the content index (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Verify the status of the backup indexer (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Add a backup indexer row (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Manage indexer failure (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Cronologia delle modifiche

Data	Descrizione	Motivo
16 dicembre 2010	Pubblicazione iniziale