Failovers

When a primary or secondary high-availability (HA) host fails, IBM QRadar maintains data consistency.

The following scenarios cause failover:

A power supply failure.
A network failure that is detected by network connectivity tests.
An operating system malfunction that delays or stops the heartbeat ping tests.
A complete Redundant Array of Independent Disks (RAID) failure on the primary HA host.
A manual failover.
NFS volumes that become read-only or not writable.

The following scenarios do not cause an automatic HA failover:

If a QRadar process develops an error, stops functioning, or exits with an error.
If a disk on your primary HA host reaches 95% capacity, QRadar data collection stops, but the primary HA host continues to function.