Database Failover

AggreGate Master and Failover servers share the same database used to store configuration data and historical system events. This database should be protected from failures by replicating the data between several physical locations.

There are three ways of setting up the database in the failover cluster environment:

• AggreGate Database Replication Engine

• Native Database Replication (supported by most relational database engines as well as NoSQL database engines built into AggreGate Server)

• Non-replicated Database (not recommended)

The common way of setting up database replication is using database replication engine integrated into AggreGate Server to write data into multiple independent databases and load-balance read operations.

The second way of AggreGate Server database replication is using native replication technology of the database server to build a database failover cluster.

Some AggreGate Server installations may also share a single non-clustered database between Master and Failover servers. However, this method doesn't protect the whole system from database server failures.

In most cases, database failover clustering should be implemented using AggreGate built-in database replication method. Its configuration is as simple as setting up two or more separate database server instances and editing several global configuration options. However, this method guarantees database data integrity and ensures optimal performance.

Was this page helpful?

Tell us more

Send

Thank you!