Failover Cluster

Iotellect has built-in support for building a failover cluster to ensure high availability of provided services.

High availability is a system design approach and associated service implementation that ensures a prearranged level of operational performance will be met during a contractual measurement period.

The failover cluster includes two separate levels of ensuring high availability service:

• Two or more installations of Iotellect Server (Iotellect Server failover cluster)

• One or more installations of the underlying database engine (storage system failover cluster)

Application and database level clusters are fully separated. Iotellect Master server may run on the same physical/virtual server with the "first part" of clustered/replicated database installation, while Failover server may share physical/virtual hardware with the second database engine installation. This allows to build a complete failover solution using just two physical servers. There can also be a clustered application working with a non-clustered database or, vice versa, a non-clustered application running over a clustered database.

Documentation provided in this section is applicable only to on-premise and edge Iotellect server instances. Cloud server users get Iotellect as a managed service, so its uptime and reliability is ensured by the service provider.

The objective of a failover cluster is to maintain 100% availability of the provided services. The cluster consists of a Master Node and one or more Failover Nodes. During normal operation, the master node is providing all services. All failover nodes are running in standby mode and monitoring the state of the master node.

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

• Network or power outage affecting the master node

• Major hardware or software failure of the master node

Both master and failover nodes are full installations of Iotellect Server that can work on their own. However, the master and all failover nodes share the same database.

The integrated failover clustering engine has some unique features:

• No dependencies to third-party software or operating system services, such as Linux Heartbeat or Microsoft Cluster Service

• Storage-level failover (database mirroring) is fully separated from application-level failover

• Cluster nodes may run on different operating systems and hardware

Was this page helpful?

Tell us more

Send

Thank you!