The LifeKeeper Microsoft IIS Recovery Kit protects Internet servers from the following problems:
- System failure or server shutdown
- Network Interface Card (NIC) failures
- Communication failures (Web server is running but stops responding)
- Startup failures (Web server aborts on startup)
The LifeKeeper Microsoft IIS Recovery Kit has two recovery procedures. For system or NIC failures, the Recovery Kit transfers the affected web server’s IP address to a standby system, and then starts up the standby web server. If there is a communication or startup failure, and local recovery is enabled, the LifeKeeper Microsoft IIS Recovery Kit will first stop and restart the affected web server locally to see if that corrects the problem. If the restart is unsuccessful, then the Recovery Kit transfers service to the backup web server.
To detect communication failures, LifeKeeper Microsoft IIS Recovery Kit checks connectivity to websites and/or FTP sites at resource startup and when running deep checks. If you did not set the URL when creating the resource, the IP address and port number set for the IIS site are used for the connectivity check. If the connection is successful, it is considered successful regardless of the response code. If you set a URL when creating a resource, LifeKeeper Microsoft IIS Recovery Kit checks connectivity by specifying the URL. The LifeKeeper Microsoft IIS Recovery Kit considers it a failure not only when a connection fails, but also when a connection is successful yet returns an abnormal response code. It then performs local recovery or failover. For secure websites, a deficiency in the server certificate is not considered a failure.
The LifeKeeper Microsoft IIS Recovery Kit manages the dependencies between the IIS application, IP and volume resources. First, you create the IP and volume resources to be used by your web servers. Then, when you create the IIS resource, the LifeKeeper Microsoft IIS Recovery Kit reads the Microsoft IIS configuration and automatically creates the required dependencies between the IIS resource and the IP and volume resources.
The following is a sample IIS hierarchy as shown in the LifeKeeper GUI. The Web site has dependencies on both the IP address “Switchable113”, and on the volume “WEB.Vol.X”, where the home directory containing the Web site’s content resides. Both the IP and volume resources were created prior to the web site creation.
Post your comment on this topic.