Deployment options (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Aggiornato: 11 novembre 2010

This article addresses topology planning considerations for Microsoft FAST Search Server 2010 for SharePoint.

In this article:

• Selecting standalone deployment or multiple server installation

• Topology options

• Deployment configuration file examples

Importante:
This article covers deployment of the FAST Search Server 2010 for SharePoint farm. For more details on deployment aspects related to the parent Microsoft SharePoint Server 2010 farm, see Plan search service applications (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese).

Selecting standalone deployment or multiple server installation

When you install FAST Search Server 2010 for SharePoint you must select between standalone deployment and multiple server installation. The main differences are indicated below.

Standalone deployment

A standalone deployment is useful when you want:

• A small-scale deployment with minimal administrative overhead

• A development or test environment

• A deployment for product evaluation

Importante:
Even for a standalone deployment, you have to deploy the Query SSA and Content SSA separately. These components must be installed on an application server within the associated SharePoint Server 2010 farm, and not on the server where you plan to install FAST Search Server 2010 for SharePoint.

It is possible to change a standalone deployment into a multiple server deployment at a later stage.

Multiple server deployment

A multiple server deployment is recommended for most production environments, except small deployments without any fault-tolerance requirements.

When performing a multiple server deployment, you first install FAST Search Server 2010 for SharePoint on all servers to be used in the deployment. After that you deploy the different components to the servers based on your selected topology. For more information, see Configure a stand-alone deployment or a multiple server deployment (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese).

Topology options

The following sections discuss topology options for deployment of FAST Search Server 2010 for SharePoint.

Search cluster architecture

The search cluster provides the main topology for indexing and query matching. These components require their own scaling models using a matrix of servers in a row/column configuration. For details on the search cluster row/column concepts, see Search Cluster.

Importante:
Search rows and indexer rows use the same row numbering in the deployment configuration. However, they represent different scaling concepts within the topology.

Recommended topologies

The following table shows recommended topologies for various deployment sizes.

For information about additional deployment alternatives and performance aspects, see FAST Search Server 2010 for SharePoint Capacity Planning (white paper). This white paper provides performance test data for multiple deployment alternatives, including deployment on virtual server architectures.

Size of deployment	Deployment details
FAST Search Server 2010 for SharePoint small farm deployment (1 server) for up to 15 million indexed items. One server (host computer) dedicated for the FAST Search Server 2010 for SharePoint farm deployment.	Standalone (single server) deployment. No scalability and failover capabilities. All FAST Search Server 2010 for SharePoint components are deployed to the same server. Importante: This must be a different server than the server(s) hosting the parent SharePoint Server 2010 farm.
FAST Search Server 2010 for SharePoint medium farm deployment (4 servers) for up to 40 million indexed items. Key performance characteristics: Feeding rate: 100-250 items/second, depending of the type of content. Query performance: 15-25 QPS, depending on feeding rate.	The deployment consists of 3 index columns and one search row. Components deployed on server 1: Administration component (admin) Query processing component (query) Web Analyzer component (webanalyzer) Item processing component (document-processor). The number of processes is set to 12 Components deployed on server 2: Content distributor component (content-distributor) Indexing and query matching components for index column 0 (searchengine) Item processing component (document-processor). The number of Processes is set to 12. Components deployed on server 3: Content distributor component (content-distributor) Indexing and query matching components for index column 1 (searchengine) Item processing component (document-processor). The number of Processes is set to 12. Components deployed on server 4: Indexing dispatcher component (indexing-dispatcher) Indexing and query matching components for index column 2 (searchengine) Item processing component (document-processor). The number of Processes is set to 12. For details on the deployment configuration file, see Medium deployment. Nota: Under certain conditions it is also possible to index up to 40 million items on a single server. This requires a modification of the indexer configuration. For more information, see FAST Search Server 2010 for SharePoint Capacity Planning (white paper)
FAST Search Server 2010 for SharePoint medium farm deployment (7 servers) for up to 40 million indexed items including search load balancing and failover. Key performance characteristics: Feeding rate: 100-250 items/second, depending of the type of content. Query performance: 20-30 QPS, depending on feeding rate.	The deployment consists of 3 index columns and one search row, with 3 additional servers dedicated to query matching. Components deployed on server 1, 2, 3 and 4: See Medium farm deployment (4 servers) for up to 40 million indexed items. Components deployed on servers 5, 6 and 7: Query processing component (query) Query matching component for index column 0, 1 and 2 (searchengine) For details on the deployment configuration file, see Medium deployment with fault tolerance.
FAST Search Server 2010 for SharePoint large farm deployment (7 servers) for up to 100 million indexed items. Key performance characteristics: Feeding rate: 100-250 items/second, depending of the type of content. Query performance: 10-15 QPS, depending on feeding rate.	The deployment consists of 6 index columns and one search row. Components deployed on server 1: Administration component (admin) Query processing component (query) Web Analyzer component (webanalyzer) Item processing component (document-processor). The number of processes is set to 12. Components deployed on server 2: Query processing component (query) Indexing and query matching components for index column 0 (searchengine) Item processing component (document-processor). The number of Processes is set to 12. Components deployed on server 3, 4 and 5: Content distributor component (content-distributor) Indexing and query matching components for index column 1, 2 and 3 (searchengine) Item processing component (document-processor). The number of Processes is set to 12. Components deployed on server 6 and 7: Indexing dispatcher component (indexing-dispatcher) Indexing and query matching components for index column 4 and 5 (searchengine) Item processing component (document-processor). The number of Processes is set to 12. For details on the deployment configuration file, see Large deployment.

The terms in parentheses indicate the component naming used in the deployment configuration file (deployment.xml). For details on the deployment configuration file, see deployment.xml reference(informazioni in lingua inglese).

The following figure shows a FAST Search Server 2010 for SharePoint medium farm deployment.

FAST Search Server medium deployment topology

Deployment configuration file examples

The deployment configuration file (deployment.xml) describes all the servers in your FAST Search Server 2010 for SharePoint deployment and the distribution of services. For more information, see deployment.xml reference(informazioni in lingua inglese).

The examples below correspond to the deployment options described in Recommended topologies. The instanceid value corresponds to the deployment alternatives described in FAST Search Server 2010 for SharePoint Capacity Planning (white paper).

Medium deployment

The following deployment.xml configuration file may be used:

<?xml version="1.0" encoding="utf-8" ?>
  <deployment version="14" modifiedBy="contoso\user"
    modifiedTime="2009-03-14T14:39:17+01:00" comment="M1"
    xmlns=”https://www.microsoft.com/enterprisesearch”
    xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
    xsi:schemaLocation="https://www.microsoft.com/enterprisesearch deployment.xsd">
  
  <instanceid>M1</instanceid>
  
  <connector-databaseconnectionstring>
  [<![CDATA[jdbc:sqlserver://sqlbox.contoso.com\sql:1433;DatabaseName=M1.jdbc]]>
  </connector-databaseconnectionstring>

  <host name="fs4sp1.contoso.com">
   <admin />
 <query />
 <webanalyzer server="true" link-processing="true" lookup-db="true" max-targets="4"/>
<document-processor processes="12" />
  </host>

  <host name="fs4sp2.contoso.com">
    <content-distributor />
    <searchengine row="0" column="0" />
<document-processor processes="12" />
  </host>

  <host name="fs4sp3.contoso.com">
    <content-distributor />
    <searchengine row="0" column="1" />
<document-processor processes="12" />
  </host>
  
  <host name="fs4sp4.contoso.com">
    <indexing-dispatcher />
    <searchengine row="0" column="2" />
<document-processor processes="12" />
  </host>
   
  <searchcluster>
      <row id="0" index="primary" search="true" />
  </searchcluster>

</deployment>

Medium deployment with fault tolerance

The following deployment.xml configuration file may be used:

<?xml version="1.0" encoding="utf-8" ?>
  <deployment version="14" modifiedBy="contoso\user"
    modifiedTime="2009-03-14T14:39:17+01:00" comment="M4"
    xmlns=”https://www.microsoft.com/enterprisesearch”
    xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
    xsi:schemaLocation="https://www.microsoft.com/enterprisesearch deployment.xsd">
  
  <instanceid>M4</instanceid>
  
  <connector-databaseconnectionstring>
  [<![CDATA[jdbc:sqlserver://sqlbox.contoso.com\sql:1433;DatabaseName=M4.jdbc]]>
  </connector-databaseconnectionstring>

  <host name="fs4sp1.contoso.com">
   <admin />
 <query />
 <webanalyzer server="true" link-processing="true" lookup-db="true" max-targets="4"/>
<document-processor processes="12" />
  </host>

  <host name="fs4sp2.contoso.com">
    <content-distributor />
    <searchengine row="0" column="0" />
<document-processor processes="12" />
  </host>

  <host name="fs4sp3.contoso.com">
    <content-distributor />
    <indexing-dispatcher />
    <searchengine row="0" column="1" />
<document-processor processes="12" />
  </host>
  
  <host name="fs4sp4.contoso.com">
    <indexing-dispatcher />
    <searchengine row="0" column="2" />
<document-processor processes="12" />
  </host>

  <host name="fs4sp5.contoso.com">
    <query />
    <searchengine row="1" column="0" />
  </host>

  <host name="fs4sp6.contoso.com">
    <query />
    <searchengine row="1" column="1" />
  </host>
  
  <host name="fs4sp7.contoso.com">
    <query />
    <searchengine row="1" column="2" />
  </host>
   
  <searchcluster>
      <row id="0" index="primary" search="true" />
      <row id="1" index="none" search="true" />
  </searchcluster>

</deployment>

Large deployment

The following deployment.xml configuration file may be used:

<?xml version="1.0" encoding="utf-8" ?>
  <deployment version="14" modifiedBy="contoso\user"
    modifiedTime="2009-03-14T14:39:17+01:00" comment="L1"
    xmlns=”https://www.microsoft.com/enterprisesearch”
    xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
    xsi:schemaLocation="https://www.microsoft.com/enterprisesearch deployment.xsd">
  
  <instanceid>L1</instanceid>
  
  <connector-databaseconnectionstring>
  [<![CDATA[jdbc:sqlserver://sqlbox.contoso.com\sql:1433;DatabaseName=L1.jdbc]]>
  </connector-databaseconnectionstring>

  <host name="fs4sp1.contoso.com">
   <admin />
 <query />
 <webanalyzer server="true" link-processing="true" lookup-db="true" max-targets="4"/>
<document-processor processes="12" />
  </host>

  <host name="fs4sp2.contoso.com">
    <query />
    <searchengine row="0" column="0" />
<document-processor processes="12" />
  </host>

  <host name="fs4sp3.contoso.com">
    <content-distributor />
    <searchengine row="0" column="1" />
<document-processor processes="12" />
  </host>
  
  <host name="fs4sp4.contoso.com">
    <content-distributor />
    <searchengine row="0" column="2" />
<document-processor processes="12" />
  </host>
  
  <host name="fs4sp5.contoso.com">
    <content-distributor />
    <searchengine row="0" column="3" />
<document-processor processes="12" />
  </host>
  
  <host name="fs4sp6.contoso.com">
    <indexing-dispatcher />
    <searchengine row="0" column="4" />
<document-processor processes="12" />
  </host>
  
  <host name="fs4sp7.contoso.com">
    <indexing-dispatcher />
    <searchengine row="0" column="5" />
<document-processor processes="12" />
  </host>
   
  <searchcluster>
      <row id="0" index="primary" search="true" />
  </searchcluster>

</deployment>

Vedere anche

Concetti

Plan search topology (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Plan FAST Search Server farm topology (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Plan for redundancy and availability (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Plan for performance and capacity (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Configure a stand-alone deployment or a multiple server deployment (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Cronologia delle modifiche