Applies To:
  • CitectSCADA 1.00, 1.01, 1.10, 1.11, 1.20, 2.00, 2.01

Question: When I startup my second alarm server, it can take up to 5 minutes before it starts to process the alarms. Why does it take so long? 

When you startup the second alarm server in a primary/standby configuration, that alarm server will connect to the running alarm server. It will then request all the current alarm status and summary data. It does this so that it will be a mirror image of the other server when it starts to process the alarms. If your project is very large, the transfer of this data can take a long time (A system with 20,000 alarms can take 10min). The second alarm server will not start processing the alarms until all the data is transferred.

It is normal for the alarms not to start processing even if the rest of Citect is running.

Also note that there is a timeout for the data to be transfered from one server to the other. If the data is not transfered before the timeout period, then the alarms will start processing and some of the alarm states will be lost. If this timeout occurs you will see the message 'Timeout from Rnd Alarm Server' in the Citect kernel, and the alarm server will try to load the alarm save file. If you have a very large alarm database you may have to increase this timeout. The timeout is controlled by the parameter [ALARM] StartTimeout=120. The default is 120 seconds, see online help for full details.