Configuration of Redundant servers in SharePoint-Summary

The redundancy configuration mentioned here refers to the configuration of multi-server Load balancer for the following purposes.

• Improve server farm Performance
• Scale up to accommodate more users
• Improve Reliability

Reliability is a special concept. It refers to the fact that in a multi-server environment, even if one or more servers cannot operate, the server farm can still accept requests and return results for the client. therefore, reliability implies redundancy, as well as a failure transfer mechanism and other features. however, redundant systems are not necessarily very reliable (reliability requires redundancy and other features ).

 

Define server redundancy requirements

============================

Office SharePoint Server 2007 supports Scalable Server farms, including functions, performance, and reliability. typically, functions are prioritized. after considering the performance, we will consider the reliability. Of course, reliability is also very important. it is an important consideration when you decide the number of servers in the server farm and the functions of different servers.

 

1 server farm

============================

If you do not need to establish additional capabilities and performance, a small number of users, simple functions, you can use a single server configuration.

 

2 server farm

============================

The simplest topology logic that does not contain any redundant server farm is two machines, one dedicated database server and the other SharePoint Application server.

 

3. server farm of the machine

============================

There is one more machine than the two machines. You have two options.

One is redundant Web Server roles, and both the Index role and Query role are installed on another machine.

Another option is to separate the index and query roles .:

 

Note: In this topology logic, the query role cannot be redundant on two web servers at the same time. this is because, if the query role and index role are installed on one machine, the machine of the index role will not forward the index Propagate to the server of other query roles. however, you can install the Index role and the database role server together so that you can have two query role servers. the disadvantage of this is that the database performance will be affected.

 

Despite the limited reliability, the performance of your Google web server role configuration is good. This configuration method can be used when performance requirements are important.

 

4. server farm

================================

This is the smallest redundant server farm.

Server 1 and 2: the Web server and query roles exist on both machines. other Application roles, such as Excel Calculation Server, can be installed on one or both servers.

Server 3 and 4: clustered or Mirrored Database server

 

In the server field of 4 machines, you must carefully select where to deploy the index server role. the query role cannot be deployed on the same machine as the index role, so Redundancy cannot be configured. this is because: when the index role is installed on a machine with the query role, the server of the index role will no longer index the propagate content to other query servers. therefore, if you install the Index server role to a web server, you will lose the ability to deploy the query role on both web servers. you can install the Index role and the database role server together so that you can have two query role servers. the disadvantage of doing so is that the database performance will be affected, especially when crawling and indexing.

Additional Application server roles, such as Excel Calculation Services, can be installed on one or two web servers, depending on the performance and reliability requirements. in the previous chart, the additional application role is only deployed on one web server, which is the same for A and B. in option A, the performance of the server without the query and index roles is optimized. in option B, the topology logic optimizes user requests and queries. the performance of other web servers can be managed by regular indexing jobs during off-peak hours, which will improve the performance of roles of other applications during peak hours.

 

5 servers

========================

This is the most common topology logic with redundant server farms, with an intermediate layer.

 

In this topology logic, the index server role must be on the application server on the middle layer.

The rest depends on whether you want to improve performance or reliability.

If you want better performance, you can install the excel services role and query role on the application server.

To ensure better reliability, you can install redundant server roles (Excel Calculation Services, Search query, and Microsoft Office Project Server 2007) on the two web servers)

 

6 servers

========================

The minimum number of servers and the maximum redundancy of the topology logic add an additional application server to the middle layer, used for Load Balancing requires redundant application server roles.

If you want to deploy the excel calculation services role or the office project 2007 role to the server farm, and the redundancy and reliability of these services are very important, we recommend that you use this configuration.

In this configuration, the application server is protected and cannot be accessed by end users. Compared with small-scale server farms, this configuration has good performance and performance.

 

Server roles that cannot be redundant

======================

Index

Windows SharePoint Services 3.0 search

In both cases, server roles will crawl content and generate indexes. If you deploy these roles on multiple servers, each server will crawl its own content.

 

In MOSS2007, the index role is associated with the Shared Services Provider (SSP.

The Index role creates an Index for each SSP.

An Index Server can be associated with multiple SSPS.

However, the indexes of multiple SSPS cannot be combined. you can deploy multiple index servers to improve your capabilities. in this case, each index Server is associated with different SSPS. the Content index created by the index role of MOSS2007 is continuously on all servers where the query role is installed. therefore, the output of the Index Server role of MOSS2007 is redundant and delivered to all query service computers with more than one query role.

 

From:

Plan for redundancy (Office SharePoint Server)

Http://technet.microsoft.com/en-us/library/cc263044.aspx