This image shows a deployment for the Historical database with three-node redundant clusters.

Other Unified Assurance servers are represented, sending log data and flow data to the Historical database.

On the left is a container representing the primary Historical database cluster, which includes three primary nodes, each with their own log ingestion application (Fluentd).

On the right is a container representing the secondary Historical database cluster, which, parallel to the primary cluster, includes three secondary nodes, each with their own log ingestion application (Fluentd).

Above the Historical database clusters are the primary and secondary Event databases, connected by multi-source replication, and each sending event data to the MySQL Replication Data Importer on the primary or secondary Historical database servers, respectively, which insert the data into the primary or secondary Historical database.

Below the Historical database clusters is a box representing a different Unified Assurance server, such as a collection server. It contains a primary and secondary instance of the log collection application (Fluentbit). The primary sends log data to each of the log ingestion instances on the primary Historical database cluster, and the secondary sends log data to each of the log ingestion instances on the secondary Historical database cluster. This log data transfer is represented by connecting arrows.

The collection server also contains the Flow Collector microservice, which sends data to the primary Historical database, and uses the secondary Historical database as a backup in case the primary is down. This backup relationship is represented by a dotted line.