Database Failover
Iotellect 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:
Native Database Replication (supported by most relational database engines as well as NoSQL database engines built into Iotellect Server)
Non-replicated Database (not recommended)
Iotellect Database Replication Engine
The common way of setting up database replication is using database replication engine integrated into Iotellect Server to write data into multiple independent databases and load-balance read operations.

Native Database Replication
The second way of Iotellect Server database replication is using native replication technology of the database server to build a database failover cluster.

Non-Replicated Database
Some Iotellect 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.

Preferred Database Failover Method
In most cases, database failover clustering should be implemented using Iotellect 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?