The IIS Server Load balancer ARR routes requests to the ARR server and the processing server. The Server Load balancer arr

The IIS Server Load balancer ARR routes requests to the ARR server and the processing server. The Server Load balancer arr

. Net web uses the iis arr (Application Request Route) technology to achieve high web performance, high reliability, scalability, and load balancing. For more information about how to use ARR, seeIISServer Load balancer-Application Request Route

For general application scenarios, see the following figure. One server only serves as the ARR server and receives requests from the client. Based on the configured Server Load balancer algorithm, it forwards requests to the real request processing server, for example, server B or C in ServerFarm is used by server B or server C to process the request and return the processing result to ARR server A. the ARR server then returns the processing result to the client.

Problems and Solutions after using ARR:

The ARR server can be used as a web static resource (js, image, and so on) server. By configuring url rewriting rules, the static resource requests are processed by ARR and no longer forwarded to other servers.

After ARR is used, the Session should not be stored in the process. You must use StateServer or SqlServer for storage. If you stick to the storage in the process, you can choose to use the Client affinity (Client affinity), that is, all requests of the customer have the same server for response and will not be forwarded to other servers, this sacrifices reliability. When the server fails, the request cannot be forwarded to other servers for service. The result is that the client request has no response.

After ARR is used, the web application files on the server Load balancer are inconsistent (for example, some images are uploaded to the Upload folder on server B, server c uploads some images in its own Upload folder. However, when a user accesses server a, the requested images may be stored on server B, server a returns FileNotFound and other similar issues. Solution: upload files to a file server (for example, server ), web applications on each server point to a unified file server by configuring virtual directories. Currently, the upload and read operations are on the Unified File Service, there is no problem that each web application only has its own file and no other server files.

 

Who has done a large-scale IIS cluster?

Reply 4 # Suntrix well, ARR does have a health check mechanism and the http application layer can directly specify the page and match the response message information to determine whether the server is alive and the service is running normally. Why should we use ARR and NLB together? If only two servers are used as the webServer, does it make sense to configure ARR? In A typical WebFarm architecture, does server A with ARR only support load balancing and request distribution, and does not share the pressure like other IIS servers ??? Unless you add the server A yourself in the WebFarm server configuration option. Then, set the UrlRewrite rule and specify A specific type or directory to server A for processing based on the request URL. Is that true?

How does Server Load balancer work on multiple Windows servers? Hope to inform,

I am also a cainiao. I don't want to count on your ideas.
You can try to build a WEB and a database on one server, and a WEB. Both the WEB and the WEB are connected to that database, so that the two WEB contents are synchronized, then load the two WEB servers. below is my COPY
Network Load Balancing allows clients to access the cluster with a logical Internet Name and virtual IP address (also known as the cluster IP address), while keeping the names of each computer. Next, we will introduce the implementation and application of network Load balancer on two general computers with Windows Server 2003 installed.

Of the two computers, one is named A, the IP address is 192.168.0.7, and the other is named B, and the IP address is 192.168.0.8. Set the private virtual IP address of the Network Server Load balancer to 192.168.0.9. When the application is formal, the client only needs to use the IP address 192.168.0.9 to access the server. Network Service balancing automatically selects 192.168.0.7 or 192.168.0.8 to provide external services based on the load of each server. The specific implementation process is as follows:

Only TCP/IP protocols can be installed on each computer that implements network load balancing. Do not install any other protocols (such as IPX or NetBEUI ), this can be viewed from "Network Connection Properties.

Step 1: log on to server A and server B as administrators and open the local connection interface of the two machines, select the "Server Load balancer" option in "Use the following items for this connection" and enter the "properties" dialog box to set the IP addresses to 192.168.0.9 (that is, a dedicated IP address for Server Load balancer ), set the subnet mask to 255.255.255.0;

Step 2: Go to the "Internet Protocol (TCP/IP)" attribute settings page of server A and server B, and click "advanced, in the displayed "Advanced TCP/IP Settings" interface, set the IP address 192.168.0.9 and subnet mask to 255.255.255.0.

Step 3: exit the "Local Connection Properties" Window of the two computers and wait patiently for the system to complete the settings.

In the future, if the two servers cannot meet the requirements, you can add the third and fourth computers to the Network Load Balancing System in the above steps to meet the requirements.

Use IIS to verify network load balancing

After the network load balancing is configured, in order to implement a specific service, you need to install the corresponding service on the network load balancing computer. For example, to achieve Load Balancing for IIS websites, you need to install the IIS service on the corresponding network load balancing server. To allow each user to access consistent data when accessing different computers through network load balancing, data consistency must be maintained on each computer of network load balancing. For example, the network load balancing of IIS on two nodes is realized. To ensure the consistency of the content of the two websites, in addition to the same configuration of the two IIS servers, the corresponding website data must be consistent.

To verify the network load balancing, we can use IIS for verification. Other applications, such as terminal services, Windows Media Services, and IIS applications, are similar. In the IE browser of another computer, type 192.168.0.9. According to the network load, the network load balancing will automatically forward to machine A or machine B. To verify the effect, you can unplug the network cable of the first computer or the network cable of the second computer during browsing. Different contents may be displayed. Of course, during the test, in order to verify the effect of network load balancing, we set the two websites as inconsistent content, while in the formal application, the content of each node and computer in the network load balancing cluster will be consistent, so that no matter which node is used for response, the accessed content will be consistent.