IIS Web Service Settings failover

IIS setting failover 1, overview

IIS failover is a redundant backup of Web sites under IIS, enabling high availability of Web services, where failover uses Microsoft's failover cluster, which is a high-availability infrastructure layer consisting of multiple computers, each of which is equivalent to a redundant node, and the entire cluster system allows a portion of the node to be dropped, Failure or damage without affecting the operation of the entire system. A server that takes over a failed server is typically a "failover".
If one server becomes unavailable, another server automatically takes over the failed server and continues processing the task. Each server in the cluster has at least one standby server in the cluster, so the relationship of each node server to the clusters is an alternate server.
The environment described in this article is Windows Server R2.

2. Implementation process 2, 1 install IIS

Open "Server Management", open "roles", click "Add Roles", the Installation Wizard complete "Web server (IIS)".

2, 2 set the shared configuration

Note: If you do not need to use a shared disk, or share a configuration, skip this step.
A, under CMD, execute command (net stop apphostsvc), (SC privs apphostsvc sechangenotifyprivilege/setcbprivilege/ SeImpersonatePrivilege), (net start apphostsvc);
B. Open IIS Information Services Manager;
C, select the computer, in the right window click on "Shared Configuration";
D, on the right side of the popup shared configuration, select "Export Configuration";
E, store the exported configuration to the shared disk;
F, connected to use the domain's Super Administrator account and password, such as, administrator, the domain name is zonma.com, then the account is: [email protected], password is adminstrator password;
G, set the encryption key to remember, because the other nodes to import the configuration needed to use;
H, after exporting the shared configuration, enable the shared configuration on this node, the configuration location is the configuration path stored in the previous step, the user name and password is just connected to the account and password. Once you've finished typing, click "Apply" on the right to make the configuration work.

2.3 Web Service settings failover

A. Deploy a good website and deploy failover clustering;
B, save the script "Clusweb7.vbs" to "Windows\system32\inetsrv\clusweb7.vbs"
C, open "Failover Cluster", right-click "Services and Applications", configure the service or application, select through the script;
D. Enter the script directory "%systemroot%\system32\inetsrv\clusweb7.vbs"
E, enter the name and the Cluster service virtual IP (access to the service portal);
F, select Storage, if you do not need to share storage, you do not need to select a shared disk, each node has a separate storage;
G, click Next to complete the deployment, if you need to view the installation status, you can view the "report" after the installation is complete.

3. Implementation effect ip:http://192.168.0.232 and domain name: http://adwgenscript.zm.com/, IP and domain name are just configured when you enter the name and IP of the Cluster service. View effects in the browser input the deployed virtual IP can view the currently owned Web site:
Figure 1
After switching,
Figure 2
Access with Name:
Figure 34, implementation questions: Do you use scripting to fail over, and is the script reliable? A: The source of the script from Microsoft Official website, the source is reliable, for special needs, need to test to answer.

Q: Why are there no IIS services or Web services in the failover cluster? A: Because the IIS service does not require shared storage as the file service in a failover cluster, the IIS service can not require shared storage, and the IIS service can simply fail over, so it is only possible to distribute the task according to the script.

Q: Why can I use domain access? A: The use of domain name access is because the cluster is in the domain environment, the domain itself has a domain name resolution service exists, but for external use, you need to be able to access the domain controller can be used to resolve the domain domain name.

Q: What is the shared configuration used for? A: Shared configuration is shared configuration of the site under IIS, shared configuration is because it can be quickly failover, such as when node a server failure, then the IIS configuration of a server is shared in the cluster, the standby server needs to replace a server processing transactions, As long as you read the shared configuration within the cluster, you do not need to configure again, you do not need to stop the service, you can restore services in a timely manner.

Q: What are the special cases when using shared configuration? A: When using a shared configuration, because it is timely to update all IIS configuration, the file is locked, only the function of a single owner, because the shared configuration of the other server IIS is not available, so when using the shared configuration, as long as there is a normal use of a server configuration, Then IIS on the other standby server can be unavailable.

Q: What is the principle of failover clustering? A: The failover cluster must be deployed in a domain-based management mode to monitor the health of each node with a heartbeat mechanism, the standby server confirms that the active server is healthy with a heartbeat signal, and to make the standby server an Active server, it must confirm that the Active server is no longer functioning properly.

IIS Web Service Settings failover