Overview
High availability (HA) ensures that your Teramind deployment is spread out in multiple instances to eliminate any single point of failure. It enables the Teramind applications and service to continue to operate even if one of the IT components it depends on, such as a server, fails.
The native, built-in high availability can be fine tuned and adapted for different scenarios.
Option 1 – HA of Critical Components
Critical TM components are deployed to all node.
 |
Each node runs:
|
On top of that, the Master node runs some Master-only workloads:
|
Requires 2*N+1 nodes.
|
This includes Master node being down, with exception of Master-only workloads not being functional.
All core workload (reporting and data capture) expected to be operational.
Master node can be restored, or another node can be promoted to Master in case of a disaster via manual re-configuration. |
Relies on external storage & external DB. Does not cover automated DB failover, external service should be used. |
Key Requirements:
|
Option 2 – Active + Passive Standby
A set of similar nodes deployed to 2 DCs
|
Each DC is a “separate” deployment:
|
At each moment of time, only a single deployment is active. Information about active DC is stored in theshared DB. |
There is no automatic DB failover, app relies on the external DB and storage that should be replicated between DCs. |
Application switchover between DC’s is performed manually via script call. |
Key Requirements:
|