How does High Availability (HA) work with Orion/NPM, and what components are involved?

How does High Availability (HA) work with Orion/NPM, and what components are involved?

• A. A single Orion server with mirrored storage and automatic failback.
• B. A SQL-only cluster with no shared storage.
• C. Multiple Orion servers with a common SQL database and shared storage; one node is active while the other members are synchronized; failover occurs for API/Web/UI/data retrieval with minimal downtime.
• D. DNS load-balanced resolution handles failover automatically.

Answer: (C)

High Availability for Orion/NPM relies on a cluster of Orion servers that share the same database and storage, with one node currently handling requests while others stay in sync and ready to take over. The common SQL database holds all configuration, monitoring data, and historical records, so any node can access the same information. Shared storage keeps the Orion data and files consistent across nodes. If the active node fails, the system moves the active role to a standby node, and API, Web UI, and data retrieval keep running with only minimal downtime. This setup provides true redundancy and quick recovery, rather than relying on a single server or a DNS-based switch.

High Availability for Orion/NPM relies on a cluster of Orion servers that share the same database and storage, with one node currently handling requests while others stay in sync and ready to take over. The common SQL database holds all configuration, monitoring data, and historical records, so any node can access the same information. Shared storage keeps the Orion data and files consistent across nodes. If the active node fails, the system moves the active role to a standby node, and API, Web UI, and data retrieval keep running with only minimal downtime. This setup provides true redundancy and quick recovery, rather than relying on a single server or a DNS-based switch.