Page Comparison

Introduction

This section covers the use of Redundancy to increase reliability of the system.

...

• Management Servers: Each Management Server is duplicated, and so has a back-up Management Server. Between the primary Management Sever and the alternate Management Server, a heartbeart pings back and forth every two seconds. If a heartbeat does not return within 10 seconds, the receiving Management Server marks the other as 'down'. If the primary Management Server goes down, the back-up Management Server swiftly takes control of the primary's Track Engines and Radar, ensuring no break or failure in the system.

• Track Engines: Track Engines back-up one another. Under Topology, you can configure which Track Engines back up which. In this example, the Track Engines back-up one another cyclically, which is probably the most logical back up configuration. If one Track Engine fails, the designated back-up Track Engine takes control of the failed Track Engine's Radar to ensure no break or failure in the system. However, a Track Engine is only able to support double its allocated number of Radar: it cannot back-up two 'downed' Track Engine. 

• Topology Manager: This is the software that constantly manages the heartbeat, and initiates a back-up Management Server take-over if the primary Management Serve fails. 

...

• Database Replica Set: The database is triplicated and backed up using MongoDB software. For more information, go to Database Replication.

• Onboard Tracker: The software inside the radar which analyses raw radar data and generates unique target data.

• Track Engine:- 

  • AID Rule Engine: The rule engine analyses all incoming tracks, looking for behaviours that would indicate an incident had occurred. For example, a stopped vehicle, or a pedestrian in the wrong area. 

  • Track Recorder: This records all tracks processed by a Track Engine for posterity. These recorded tracks are not analysed as Live data. Each Track Engine has its own Track Recorder. 

...