Figure HA-4 · Standard design
rConfig active/passive pair
Two identical nodes, one VIP, every data tier redundant
rConfig
Client traffic
Replication
Heartbeat
Failover action
Active node connection
Connects after failover
01 · TRAFFIC
One address
DNS points at the VIP
02 · APPLICATION
rConfig V8 pair
Identical installs. One runs, one waits
03 · DATABASE
Database cluster
One primary, two replicas, own VIP
04 · QUEUE
Redis or Valkey
Sentinel picks the primary, own VIP
05 · STORAGE
Shared storage
Same files on both nodes
Users, integrations, Vector agents
VIP 192.0.2.10 · rconfig.example.com
VIP after failover
moves on failover
Node A · rConfig V8
ACTIVE
rconfig-a.example.com
Web and APIrunning
Schedulerrunning
Horizonrunning
Trap handlerrunning
Node B · rConfig V8
PASSIVE
rconfig-b.example.com
Web and APIstopped
Schedulerstopped
Horizonstopped
Trap handlerstopped
keepalived
unicast VRRP
VIP 192.0.2.30
db1
PRIMARY
PostgreSQL
db2
REPLICA
streaming replica
db3
REPLICA
streaming replica
Patroni + etcd,
or MariaDB/MySQL
equivalent
VIP 192.0.2.40
Primary
Redis or Valkey
Replica
Redis or Valkey
Sentinel 1
Sentinel 2
Sentinel 3
Shared storage · NFS HA, GlusterFS, EFS, Azure Files
Mounted on both nodes at /var/www/html/rconfig8/current/storage