Can someone please explain how runtime alarm property (e.g. delay, category) changes are best retained, and how UseConfigLimits is best utilised?
In the case of a Local Engineering Environment, running a single alarm server, compilation of a changed project alarm database seems to overwrite all runtime value changes on an alarm server restart (although not on a reload).
I don't yet have a redundant pair of servers in operation, so I'm not sure how it behaves on a staggered restart (I assume runtime values are synched server to server). However, if both servers are restarted or go offline at the same time, I would think they are going to load from the project database, and all online changes will be lost once again.
UseConfigLimits is not recommended setting to 1 for Run/Copy. If this is how the servers are setup, what it is best way to use this parameter? Would UseConfigLimits = 1 only really work if the project is developed on and distributed from a client, so the project database is updated from runtime changes on this computer only? On the other hand, is this parameter only used by the alarm server, and so only affects the databases on PCs hosting alarm servers?
Cheers,
Dane
