15.5. Redundant Peer Configuration

Despite the Multiple Redundancy is superior for scalability and reliability, but the configuration can be as simple as entering the IP for any peer PC that need to be participated.


Name of the peer server.


Additional information about the peer server.

Peer Address

List of IP addresses separated by comma for all peer servers.


The Ranking parameter specifies the priority of the peer server. The peer server with the lowest numerical value among all active peers will be promoted as the primary server. The allowed values range from 1, the highest priority. This value must be unique for all the peer servers in the cluster.

Only the the server being rank top as primary will be running at all time to ensure no conflit of script processing and to avoid network congestion with too much of run-time data exchange.

Connection String

ODBC connection string to connect to peer server databases. Additional database is needed for storing temporarily pending data before the synchronization is taking place.


Purge database to prevent overflow of accumulated pending data, in case the peer database is not available to be synchronized for too long.

Purge Freq.

Define how frequent old data are purged from this database. Normally setting it to wee hours like 1am to 4am shall be a good idea as it will be less busy moment for CPU.

Retain Type

Define whether old data is purged based on number of days or number of records. Data are purged in FIFO (First In First Out) basis.

Retain Count

Define how long (day) or how many entry (record) the database shall keep.

Once System Redundancy is enabled, look out the Watch List for the associated system tags that will be available for monitoring or further handling.

Configuring redundancy peer

Server is running with Redundancy task