Figure HA-9 · Vector
Vector high availability
Each component is its own active/passive pair; RabbitMQ is optional to cluster
rConfig
Agent connection
Central Manager and RabbitMQ links
VIP
Virtual IP
Heartbeat
01 · CENTRAL
Control plane
Central Manager pair and RabbitMQ
02 · REGIONAL
Vector Servers
One pair per region, each with its own data tier
03 · PORTAL
Vector Prism
Its own pair and VIP
04 · EDGE
Vector Agents
Connect outbound to a VIP
Vector Central Manager
Node A
ACTIVE
Node B
PASSIVE
VIP 192.0.2.50
MQ
RabbitMQ
Cluster of 3, or single node
messages short-lived · days, not weeks
EU
rConfig V8 Vector Server
Node A
ACTIVE
Node B
PASSIVE
VIP 198.51.100.10
Own data tier
DB
Redis/Valkey
Storage
US
rConfig V8 Vector Server
Node A
ACTIVE
Node B
PASSIVE
VIP 198.51.100.20
Own data tier
DB
Redis/Valkey
Storage
Vector Prism
Node A
ACTIVE
Node B
PASSIVE
VIP 198.51.100.30
Users reach Prism on its own VIP.
Prism reads from each Vector Server.
Vector Agent
Customer A · EU
Vector Agent
Customer B · EU
Vector Agent
Customer C · US
Vector Agent
Customer D · US
to the server VIP, never to a node