3.2.30         Backup SCADA Node

A Redundant SCADA node consists of SCADA node and a Backup SCADA node, each with SCADA node software, license control file and Hardkey installed (i.e. two licenses and two hardkeys).  The Project Manager will download an identical run-time database to both primary and backup SCADA nodes (assuming both are on-line).  The primary and Backup will communicate with each other when the kernel is started, but only one will communicate to automation hardware.  If the Primary fails, the Backup will begin communications to the automation devices.  The Web Browser clients will be redirected to the Backup automatically if the primary node fails.  The redundant SCADA node requires the purchase of two SCADA node licenses.

Specifying a Node Name and IP address will create a backup of the Primary SCADA Node.  The communications protocols used by field devices, and your communications network must support redundant Masters or Redundant Communications from multiple PCs.

The Backup SCADA node uses the same database as the primary (e.g. devices, communication ports, tags, alarms, trends, groups, scripts and graphic displays).  However, the IP Address will be different.  The TCP Ports and Remote Access code may also be different.

Data in the Primary and Backup nodes of a redundant system are synchronized. This includes real-time data, datalog trend data, alarm/action log data, saved recipes and tag-field data.