SharePoint 2013 Instance 1-building a three-tier server farm 2-Scenario Design

1. Server Load Design

In the previous section, we saw that the servers were made up, with the basic design of redundancy for each of the SharePoint Server (hereinafter referred to as SPS) servers, not just high availability requirements. Because a single server is constrained by processing power, the ability to provide is limited, while multiple servers can balance the load, the performance of the whole system will be greatly improved. But how many servers do we need to serve, we can estimate it beforehand.

1) calculated from the number of users, the design is as follows:

Internal staff: 22000 people, at the same time at peak time on-line ratio 80%, peak hours per hour 36, peak at the same time to access the ratio of 50%

External: 100000 people, at the same time at peak time online ratio 30%, peak hours per hour 18, peak at the same time to access the ratio of 30%

This can roughly calculate the number of requests per second at peak (RPS, requests per second) for

(22000*80%*36*50%+100000*30%*18*30%)/3600= 133

According to Microsoft test data, a 8-core 16G memory front-end server processing requests up to 80RPS, so that 2 front-end servers can basically meet the requirements.

Similarly, the application server does 2 configurations.

2) from the business data to calculate, the design is as follows:

Business Data 1200GB, average document size 200KB

This calculates the number of document items that need to be processed:

1200gb/200kb=600 million items

The list data has 200 items, each item counts 20 columns, each column counts 1000 items

This calculates the number of items that need to be processed for the list:

200*20*1000=400 million items

So light documents and list items have 10 million items

Because you include documents, Web pages, list items, and images, each entry in a SharePoint list can be listed as an item, and the actual number of items may be more than 1.5 times times the calculated value.

Based on the Microsoft Search Architecture Example:

Content Volume	Sample Search Architecture
10 million item (+)	Small Search server farm
10 million-40 million items	Medium Search Server farm
40 million-100 million items	Large Search server farm

Based on the table above, it is better to build a medium Search server farm here. Due to some conditions and objective reasons, this project only demonstrates the use of a search dedicated server to provide search services.

According to Microsoft test data, a small search farm can crawl 50 documents per second and serve 10 queries per second. So for the first full crawl, 10 million items take 55 hours to crawl.

2. Account Security Design

We often use the same administrator account to complete all configurations in an experimental environment, but doing so in a production environment poses a variety of risks.

By giving each account the least privilege, not only can effectively limit the non-prospective personnel to obtain the account after the attack damage to the system, and different services account management can make the account of the scope of use clearer, reduce system risk.

The account is designed as follows (all accounts are domain accounts):

Name	Role	Permissions
Sql_install	SQL Server Installation Account	Members of the SQL Server local Administrators group
Sql_service	SQL Server service Account	No
Sp_install	SPS Installation and Configuration account	Members of the SPS server local Administrators group SQL Server securityadmin and dbcreator permissions
Sp_farm	Farm Admin Account .	SQL Server securityadmin and dbcreator permissions (SPS will automatically add this permission at configuration time if no append is in advance)
Sp_pool	Application pool Account	No
Sp_service	SPS Service Account	No
Sp_profile	Synchronizing the user profile account with AD	AD Replication Directory Change permissions

3. Port Security Design

A specific port is used to communicate between servers in an SPS farm and to provide specific services.

This allows the following ports to be configured on the SPS server's firewall

Service	Open ports
SharePoint Web Services	TCP 80, TCP 443
SharePoint Central Administration	Custom ports
Communication between Web servers and service applications	TCP 32843~32845
User Code Service	TCP 32846
File sharing	TCP 137,udp 138,tcp 139,tcp 445
Search Index Component Service	TCP 16500~16519
AppFabric Caching Service	TCP 22233~22236
Windows Communication Foundation Communication port	TCP 808
Mail SMTP	TCP 25
User Account Synchronization	TCP&UDP 389,tcp&udp 53,tcp 5725

This article is from the "Iron Fist of the Invincible Speaker" blog, please be sure to keep this source http://yaojiwei.blog.51cto.com/762134/1630549

SharePoint 2013 Instance 1-building a three-tier server farm 2-Scenario Design