Redundant Databases for the AlarmWorX64 Logger

With AlarmWorX64 Logger, you can specify a second, stand-by (redundant) database for logging alarm data if the database is not centralized and is not already made redundant via clusters or other means. An additional store-and-forward feature that caches data when a database becomes unavailable, and synchronizes data when the database comes back online. This ensures that the logger can always write alarm data to a database, and significantly reduces the risk that alarm events will be lost due to loss of database availability.

 

Note:  While this approach ensures that a database is always available for the logger to write to, it does not help if the logger itself becomes unavailable. To set up redundancy so that the logger is always available, refer to Redundancy in GENESIS64.

 

To set up redundant database for the AlarmWorX64 Logger to write to, use the Redundancy sub-tab of the Database Logging tab accessed from the AlarmWorX64 Logger Alarm Log Configuration Form. (For additional information about this form, refer to Configuring the Logger.)

 

Fields on the Redundancy sub-tab are:

See also:

AlarmWorX64 Logger

Database Logging Tab