Broker Redundancy¶
Configure primary and secondary MQTT brokers for automatic failover.
Screenshot placeholder: Broker redundancy configuration
How It Works¶
- Gateway connects to primary broker
- Publishes all data normally
- If primary fails → automatic failover to secondary
- Background monitor checks primary availability
- Auto-reconnect to primary when recovered
Configuration¶
Set Up Brokers¶
- Create primary broker (see MQTT Brokers)
- Create secondary broker
- Test both connections
Configure Edge Node¶
Screenshot placeholder: Node broker selection
- Edit edge node
- Select Primary Broker
- Select Secondary Broker
- Save
Failover Behavior¶
Detection¶
- Primary connection lost
- Keep-alive timeout
- Write failure
Switchover¶
- Disconnect from primary
- Connect to secondary
- Publish NBIRTH to secondary
- Resume normal operation
Recovery¶
- Background task monitors primary
- When available, reconnect to primary
- Publish NBIRTH to primary
- Resume normal operation
Best Practices¶
- Use different servers for redundancy
- Test failover scenarios
- Monitor both brokers
- Keep credentials synchronized