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

Web www.xlink.com
 

 
 

IsaStor Products
ClusterReplica
EzOpenBackup
EzOpenBackupPlus!
   
   
   
 
Try free demo of  Disk- Based File Backup, Data Replication and Cluster solutions software  today 

 

 

 

Feature listing of
ClusterBalancer and ClusterReplica

 

Features

 ClusterBalancer

ClusterReplica

Remarks

Load Balance

  The clustered systems must be 
connected with a HUB to apply 
Load Balance

Failover/Failback

(3 situations may apply)

  1. Service/Application failure
  2. Network Application failure
  3. Entire server fails

(2,3)

(1,3)

 1. The entire system failover will take place when any one of the Data Replication defined service fails.
2. Only Load-Balance-defined  services will carry out  network application Failover when the service on either Primary or Secondary  system fails.
3. When the Primary system fails
or  is completely shutdown
 

One-way
Data Replication

  

Support open file backup. Only updated portion of a file is to be replicated on the Secondary server of both Database and File system files.

Two-way
File Synchronization

 

 The entire file is to be updated when there is a change in the file of Windows File System on either Primary or Secondary server.

Firewall

 
 

Network Utilities

 

Network Application Scanner

 

Port Reference Table

 

XLink Easy Backup Utility

 

Cluster Messenger

  

 

Here are some real world examples to show you
how ClusterBalancer and ClusterReplica can work for you.

Case One:




You are running a web server which services a web site of a hundred html files in the "inetpub\wwwroot" folder.




When one day your server failed. Both you and people who are trying to view your site are not happy with the situation.


Click here for solution




Case Two:


You are running a web server which services a web site of a hundred html files in the "inetpub\wwwroot" folder to sell auto parts. There is also a SQL database on the web server for detailed product information.




When one day your server failed. Both you and you internet customers are not happy with the situation.


Click here for solution




Case Three:



You are running a web server which services a web site of a hundred html files in the "inetpub\wwwroot" folder. You also have a separate system to run the SQL database server.




When one day your web server failed. Now your online customers cannot see the web site at all.



OR

that your SQL database server is down, that your network Customers cannot get to see the detailed product information when trying to buy them.


Click here for solution