Applies To:
  • CitectSCADA 5.xx, 6.00
Summary:
I am having problems getting my Alarm redundancy working correctly. When I shut down one server, alarms are retriggered. It also crashes or hangs on startup occasionally. What is wrong, and how do you fix it?
 

Solution:
The most common problem with Alarm redundancy is the use of the Alarm Save path parameters:

SavePrimary The path to the primary save file.
SaveSecondary The path to the secondary save file.

Logically this means:

SavePrimary The path to the local copy of the Almsave.dat file.
SaveSecondary The path to the remote copy of the Almsave.dat file.

Confusion is caused when the computer setup wizard asks you for the Primary and Standby paths. This information is saved to the SavePrimary and SaveSecondary parameters, respectively, regardless of whether the current computer is the primary or standby server.

Take for example you have a Primary and Standby server both with mapped drives to the other server, then the settings would be similar to this:

Primary Citect.ini:
[Alarm]
SavePrimary=C:\citect\data\Alarm
SaveSecondary=G:\Alarm
!(G drive is mapped to the Standby servers C:\citect\data directory)

Standby Citect.ini:
[Alarm]
SavePrimary=C:\citect\data\Alarm
SaveSecondary=G:\Alarm
!(G drive is mapped to the Primary servers C:\citect\data directory)
 
Keywords:
Alarm, SavePrimary, SaveSecondary, startup hang  

Attachments