Redundancy
- 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:
Schematic
- Database Replica Set: the database is triplicated and backed up using MongoDB software. For more information, go to Database Replication.
- Onboard Tracker:
- AID Rule Engine:
- Track Recorder:
Related information
-
ClearWay™ System Design (Witness 4.0)
-
ICD-001 System Profile Command (Witness 4.0)
-
Assigning a Camera (Witness 4.0)
-
AdvanceGuard® System Design (Witness 4.0)
-
System Design (Witness 4.0)
-
Camera Controllers (Witness 4.0)
-
Management Server Configuration (Witness 4.0)
-
Track Engine Configuration (Witness 4.0)
-
ClearWay™ Alarm Panel (Witness 4.0)
-
Notes (Witness 4.0)
-
Database Configuration (Witness 4.0)
-
System Alarm Queries (Witness 4.0)
-
Navigating AdvanceGuard® (Witness 4.0)
-
Configuration (Witness 4.0)
-
Redundancy (Witness 4.0)