|  Home  |  Products  |  Solutions  |  Downloads  |  Support  |  How to Buy  |  Partner  |  Press  |  Contact  | 

Your objective:

1. To keep your web server available for internet browsers at all time
2. To speed up clients' server access speed

Solution: ClusterBalancer

You bought another Windows 2000 system (either server or professional model will work) and configured it just like that of your original web server system. Connected it with the original web server system using a HUB, and install ClusterBalancer on both systems.

This is your new web server now :   Notice that the service requests are split between the servers (Load Balance), and the new date is copied between the two systems (File Synchronization).



1. Above picture shows how the cluster server works when both Primary and Secondary servers are running normally.
   
   
2. The next picture shows the situation when the Primary server is down.
   

   Your web server is now in Failover state:   Notice now 100% of service requests are going to the Secondary system, and there is no data updating between the servers.

   

   
   
   
3. After five hours of hard work, you fixed the problem on the Primary server, and reconnected it to the Secondary server.
   

   Your Web server is now back in normal condition :   Everything is working again as your original configured

   

   
   
   

   Please notice that in all three situations described above, the failure and rework of the Primary server did not affect the internet clients access to your web server.