Shulou(Shulou.com)05/31 Report--

How to choose the topology of Sharepoint 2010 reasonably? in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

SharePoint has always been praised for its flexibility and rich features. For example, when planning, we can choose different topologies according to the scale of the application to meet the performance and functional needs of users. Here, the author takes SharePoint 2010 as an example to talk about how to choose the appropriate topology according to the size of the application.

1. Key factors of server topology planning

For SharePoint applications, what type of server topology should be adopted is mainly determined by the scale of enterprise applications. The larger the scale, the more complex the topology may be. Because of the simple topology, it can not meet the performance and functional needs of users. While considering scale, you may need to take into account factors such as enterprise security, network deployment, server configuration, and so on.

In addition, after the server topology is determined, the subsequent adjustment will be more troublesome. This is the same as the topology of the network. For this reason, when planning for SharePoint, we must weigh various factors and reasonably determine the server topology that needs to be adopted. Although the plan is not changing as quickly as possible, you still need to avoid changing the server topology in a short period of time (such as 5 or 8 years).

Second, the application of small topology

A large topology is generally composed of a database, an Web application server, and an application server. Sometimes the application server is even deployed on the same server as the Web application. This is shown in the following figure. In a small server topology, the front-end server is typically configured as a Web server and another is used as an application server (or you can combine the two into one). The application server here is mainly used to host the management center website and handle other maintenance and management tasks related to the server environment.

As shown in the figure above, the most important feature of this small topology is that all of them are equipped with servers. Such as database applications, application services, Web application services and so on are independent servers without load balancing function. This kind of scheme has both advantages and disadvantages. The advantages are mainly reflected in cost and management. For small and medium-sized enterprises, the number of users is not very large, and the applications implemented in SharePoint are not very complex. For this reason, the performance requirements will not be very high. At this time, the use of a separate server can basically meet the requirements. And this topology is relatively simple and convenient to maintain.

The disadvantage of this topology is mainly reflected in the stability. It uses a single server, but there is a server failure, such as Web application server or database server problems, then users will no longer be able to use this application. And in this case, the access pressure is concentrated on a single server. There is no load balancing function. Therefore, under this topology, it is necessary to make an immediate backup of the data, especially the remote backup of the data. This helps not to lose data when the server fails.

It can be seen that the advantages and disadvantages of small topology are quite obvious. As a manager, we should have a clear understanding of these advantages and disadvantages. Only in this way can we judge whether it is necessary to adopt this small topology according to the actual situation of the enterprise. In general, this topology is mainly suitable for small businesses and can tolerate a certain amount of downtime.

III. Application of medium-sized topology

The medium server topology mainly consists of one database server, one application server, and one or two Web servers. Compared with the small topology, the medium topology is mainly reflected in two aspects. One is that in a small topology, the application server and the Web server can be implemented on the same server. In medium-sized topologies, they are often required to be independent. Second, the number of Web servers is also different. In a small topology, there is usually only one Web server, or even deployed on the same server as the application server. In a medium-sized topology, Web servers are generally independent. Sometimes to improve performance, you can even use two Web servers to achieve load balancing. In this configuration, the application server is mainly used to manage the central website and server environment management and maintenance. The front-end Web server handles tasks such as searching queries and responding to client requests.

In this topology, the author thinks that we should pay attention to the following two points.

One is the choice of the number of Web servers. When the number of users visited is relatively large, the performance of SharePoint may degrade. Because a typical SharePoint application is composed of database, application service and WEB service. At this point, the administrator needs to analyze where the performance bottleneck lies. According to past experience, in the case of the same configuration, there is usually a problem with the Web server. This is mainly because the Web server is used to handle queries and respond to client requests and other related work. Compared with other servers, these workloads are relatively large. For this reason, when the performance of this application degrades, the administrator should first think about whether there is a performance bottleneck on the Web server. This is an experience. This experience is valid in most cases.

Second, when the bottleneck of the application appears on the Web server, how to optimize it? There are three general optimizations. The first is to optimize the application, the second is to optimize the server configuration, and the third is to achieve load balancing for the Web server. These three optimization methods are not in order, but need to choose different ways according to different situations. If the administrator analyzes and finds that the design of an application is unreasonable, even by improving the configuration of the server or increasing the number of Web servers, the final effect is not very obvious. On the contrary, the related application itself is more reasonable, when the number of users is relatively large, the use of Web server load balancing can achieve better results. For another example, if the trace finds that the bottleneck of its performance is mainly due to the disk's I _ max O conflicts, it is a bit of a mountain out of a molehill by increasing the number of Web servers. Implementing a disk array on the original Web server can solve the problem.

Generally speaking, this medium-sized topology can accommodate applications of about 500 people. If there are more stringent requirements for performance or a large number of concurrent visits by users, we can appropriately add a Web server to improve the performance of the application. At the same time, this topology gives us a hint. In general, when optimizing the performance of SharePoint applications, we often look for a breakthrough from the Web server. This server is a key point in the whole chain.

IV. Application of large-scale topological structure

In a large topology, there are often two or more servers consisting of a clustered database server, an application server (which can also be increased as appropriate), and multiple front-end Web servers. In this configuration, all application servers are configured to support specific service applications or service application components. The query and other work is still on the Web server.

As shown in the figure above, the main change in this large topology is on the database server compared to the medium-sized topology. At this time, multiple database servers are also used on the database server to achieve load balancing. While improving the performance of the application, it also improves the stability and redundancy of the application. However, in the implementation of database load balancing, the author puts forward a small suggestion. The administrator can divide the database into two categories: querying the database and changing the database as needed. Because according to past experience, most of the operations of users in SharePoint are queries, not data updates. At this point, if there are three databases that form a clustered server, you can set one database to updatable and the other two databases to readable. When a user is only a query operation, he or she accesses a readable database. On the contrary, when an update operation is performed, it accesses the update database. Of course, this is transparent to users. The application system will automatically determine which database the user should connect to according to the user's operation. The main purpose of this operation is to improve the security of data. At the same time, the division of work between query and update can improve the performance of the application.

This is the answer to the question on how to reasonably choose the topology of Sharepoint 2010. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.