Data Replicator
HA Products
For Windows
For Linux
For Windows
For Linux
Related Links
Customer's feedback
The best choice for High Availability Cluster!
This complex work mode can be achieved only by the series of LanderCluster-MN, which is the solution of high performance-price ratio and propagable future. With the development and popularization of storage technology such as SAN, ISCSI, NAS, overall high availability is able to achieved in users’ complex servers environment by multi-notes cluster.
Most industries and consumers have faced a vexing problem.
  1. The issues about the reliability of key business
  2. The issues about the difficulty of maintenance among several key business in system
  3. The issues about the security of application data
  4. The issues about the huge losses because of service-stop of business system
The advantages of using LanderCluster
LanderCluster multi-notes cluster product is a leading one in the series of LanderCluster products. Support the complex applications with eight nodes. Support the platform of Windows/Linux/UNIX and etc. Stability & reliability, easy management, Clusters work in various ways and nodes and scalable tasks. It can automatically detect and isolate faults, transfer the original mainframe’s application systems to another mainframe in the cluster continuous to operate, achieve the continuous operation of the entire system.
    ● Easy-config, easy-maintain;
    ● Own proprietary software products, support special enviroment, function customization;
    ● Achieve shift of applications automatically. Easy-manipulating of graphic interface;
    ● Verification of administrator & password, high-level factor for security;
    ● Assure that the standby thread works normally;
    ● Monitor on the numbers of thread and special application;
    ● Load balancing for tasks;
    ● Managed and monitored by graphic remote model through management platform;
    ● Supported nodes:2-64(or above);
    ● Rules based on tasks could be configged neatly;
    ● Node configurations:Active/Active;Active/Passive(Standby);N+1;N+M;N-to-1;N-to-N;
    ● Perfect log record and error alarm, serving to error tracking;
    ● Application of independence, the support of almost all database environment;
    ● Support the smooth expansion,eg:FROM N-to-1 TO N-to-N;
    ● Support for IP-based enterprise storage networks, such as SAN,NAS;
    ● Support common storage:FC,SAS,ISCSI,SCSI;
    ● Support common database:oracle,SQL,DB2,Sybase;
    ● Supported language: English and Chinese;
    ● Support shared storage and MirrorHA model;
    ● Cluster management platform could be switched between or among different OS.
Node configurations
    The most common size for LanderCluster HA cluster is a two-node cluster, since that's the minimum required to provide redundancy, but many clusters consist of many more, sometimes dozens of nodes. Such configurations can sometimes be categorized into one of the following models:
    Active/Active — Traffic intended for the failed node is either passed onto an existing node or load balanced across the remaining nodes. This is usually only possible when the nodes utilize a homogeneous software configuration.
    Active/Passive — Provides a fully redundant instance of each node, which is only brought online when its associated primary node fails. This configuration typically requires the most extra hardware.
    N+1 — Provides a single extra node that is brought online to take over the role of the node that has failed. In the case of heterogeneous software configuration on each primary node, the extra node must be universally capable of assuming any of the roles of the primary nodes it is responsible for. This normally refers to clusters which have multiple services running simultaneously; in the single service case, this degenerates to Active/Passive.
    N+M — In cases where a single cluster is managing many services, having only one dedicated failover node may not offer sufficient redundancy. In such cases, more than one (M) standby servers are included and available. The number of standby servers is a tradeoff between cost and reliability requirements.
    N-to-1 — Allows the failover standby node to become the active one temporarily, until the original node can be restored or brought back online, at which point the services or instances must be failed-back to it in order to restore High Availability.
    N-to-N — A combination of Active/Active and N+M clusters, N to N clusters redistribute the services or instances from the failed node among the remaining active nodes, thus eliminating (as with Active/Active) the need for a 'standby' node, but introducing a need for extra capacity on all active nodes.