data replication, registry repliation, cluster

 | XLink Home | Products | Downloads | Support | How to Buy  | Press  | Contact | Partners |
 
Google

Web www.xlink.com
 

 
 

IsaStor Products

ClusterReplica
ClusterBalancer
EzOpenBackup
EzRollBack
   
   
   
 
Try free demo of 
File Backup, Data Replication and Cluster solutions software  today 


 

 

Understand ClusterBalancer Status

For clustered systems, there are two ways to connect them: using a Hub or using a Switch. XLink's ClusterBalancer supports both connections. Click
here to learn more about the difference of Switch and Hub connected networks.

Following picture shows the load balance status of a Hub connected clustered system:

Following picture shows the load balance status of a switch connected clustered system:

In above pictures showing overall status of ClusterBalancer, two collective sections can be established in the display area: Load Balance Status and Firewall Status. Load Balance Status includes clustered system information and the load-balanced service information. The firewall Status shows the application standing of both local and remote systems (if you are looking at a Primary system, the Secondary system is the remote system, and vise versa).

Load Balance Status

1. Load Balance Status for Hub Connected Systems:

From the example showing below, we can see: in "Balance System Info" section, the ‘System Type’ displays ‘Primary Station’. This indicates that the local system is the primary system in the cluster, which also means the load balance setup can be done from this system.

The status showing ‘Active’ on both systems. This indicates both Primary and Secondary systems have ClusterBalancer installed and running properly, and Load Balance service is enabled.

When the Secondary system is marked with a red circle on the computer image and status shows ‘Inactive’, as shown in following picture, it means either the system is not up and running or it does not have ClusterBalancer (correctly) installed, or the IP address is not defined in the LAN.

The Load Balance service can be enabled/disabled by clicking the ‘Disable/Enable Load Balance’ button. Following picture shows the status of Load Balance being disabled.

Matching with the Balanced System info showing in the second of above picture, the "Balance Service info" indicating also the Load Balance service is disabled.

When Load Balance service is enabled, but with no user defined application/services for load balance, the "Balance Service Info" status will display as in next picture.

Following picture presents the settings of three load-balanced services when both Primary and Secondary systems are up and running without problem.

Following picture presents three services set to be balanced, but the last item with a little red flags flying next to the service name and the Primary system is taking up 100% of the workload. This indicates either the service on the secondary system is dead, or the Secondary system doesn’t have the same application/service activated. In this situation, Load Balance is not functioning.

With a forced failover (by click on button 'Manual Failover' in Load Balance Setup), the status is showing:

2. Load Balance Status for Switch Connected Systems:

The load balance feature is not functioning in the switch connected clustered system. As shown in following picture, all service load is on the Primary system. However, there is still benefit for setup load balance here: in the event that one of the services stopped working, failover will step in and assign all the service requests that has been setup in load balance to the secondary system.

The switch connection of a clustered system should not affect the normal function of File Synchronization and Firewall of the ClusterBalancer package.

Back to top

Firewall Status

In this section, the firewall status of both Primary and Secondary systems can be checked from either of the systems. Because firewall setup is done independently on each of the clustered systems, the Enable/Disable button is for the local system only.

Above picture shows the typical situation of firewall status. Both local and remote systems are having the firewall enabled and running normally.

Following picture indicates local firewall is disabled. Because firewall is running independently on each of the clustered systems, ‘Enable/Disable’ will only affect local system.

Following picture is an example of the firewall status showing the remote system is either disabled or having problem with firewall settings or that the whole system is down.

Lastly, for users’ convenience, the system type and service status are shown on the bottom of the dialog box frame. The green light indicates the active status of the application services. The red light means service is disabled. This frame of information will stay while the content of the dialog box changes.



 
 | About XLink | Privacy | Legal |                                                                                           © 1991-2004 XLink Technology, Inc.