Skip to main content

XProtect Management Server Failover

Failover steps

Last Updated: 1 minute read
Version2026r1
LanguageEnglish

In a typical scenario, you install these components on both nodes:

  • XProtect management server

  • XProtect event server

  • OpenTelemetry bundle

  • XProtect Management Server Failover

  • XProtect API Gateway

  • XProtect recording server (optional)

  • SQL Server (optional)

The failover steps in a typical scenario are:

  1. The management server, event server, and SQL Server run on Node 1 (in PRIM state). If you have installed SQL Server on the nodes, XProtect Management Server Failover replicates the data from these system components on Node 2 (in SECOND state).

    Standard failover cluster configuration where data is replicated from the PRIM node to the SECOND node.

    Every second, the nodes exchange heartbeats.

  2. If the management server on Node 1 becomes unavailable for 30 seconds, Node 2 takes over.

    The failover time depends on the startup time of the Management Server service.

    1. Node 2 comes into ALONE state, and the data replication stops.

    2. The Management Server, Event Server, and OpenTelemetry Collector services, and the SQL Server instance start running on Node 2.

    3. Management Server, Event Server, and OpenTelemetry Collector services store data on the SQL Server instance on Node 2.

    Failed node scenario with no data replication.

  3. You identify and fix the issue that caused the failover and start Node 1 from the failover web console. The data that was modified on Node 2 replicates to Node 1.

    Data replication after failback. The states of the nodes are swapped.

    The VMS system components still run on Node 2 (in PRIM state), and the data replicates on Node 1 (in SECOND state). If needed, you can swap the states of the nodes from the failover web console.