Failover Clustering for High Availability

AggreGate Database Clustering

Native Database Clustering

AggreGate has internal support for building a failover cluster to ensure high availability of provided services. The failover cluster consists of two or more installations of AggreGate Server and one or more installations of the underlying database engine.

The failover cluster's objective is reaching almost 100% availability of the server. The cluster consists of Master Node and one or more Failover Nodes. During normal operation, the master node is servicing all operations. All failover nodes are running in standby mode and monitoring the state of master node.

The failover nodes are automatically switched to Failover Master mode (i.e. activated) in the following cases:

• Network or power outage of the master node
• Major hardware or software failure of the master node

AggreGate Failover Cluster Features

The integrated failover clustering engine has some unique features:

• No dependencies on third-party software or operating system services, such as Linux Heartbeat or Microsoft Cluster Service
• Cluster nodes intercommunication is performed via the database, no additional setup of node-to-node IP communications is necessary
• Database mirroring is optional and may be implemented using DBMS native replication or AggreGate-based replication
• Cluster nodes benefit from database load balancing
• Cluster nodes may run on different operating systems and hardware
• 3+ nodes cluster remains redundant in the case of master node failure