Cold (Active machine only):In this mode, the application
will only connect to one underlying server at a time. On startup, a connection
to the primary server will be made and all client related requests will be
forwarded onto the primary. In the event that the connection to the primary
fails, or communications to the primary is lost, a connection to the secondary
will be made. If the redundancy application is unable to obtain a connection to
the secondary, it will continue to ping-pong between the two servers until it
makes a successful connection.

Warm (Both machines, subscribe to items on active
machine):In this mode, the application will attempt to maintain a
connection to both the primary and secondary servers at all times. Only items in
the primary server will be active and polled. In the event that the connection
to the primary fails, or communications to the primary is lost, the identical
items in the primary server will be set to active in secondary server.
Periodically, both servers will be pinged to determine if the connection is
still valid.

Hot (Both machines, subscribe to items on both machines):In
this mode, the application will attempt to maintain a connection to both the
primary and secondary servers at all times. On startup, the application will
initialize data callbacks for both primary and secondary servers so that both
servers will send data change notifications. The data received from the primary
server will be forwarded onto the client. In the event that the connection to
the primary fails, or communications to the primary is lost, data received for
the secondary will immediately be forwarded onto the client.

OPC Server Aliasing:This feature will allow you to
configure multiple pairs of OPC Servers with the same ProgID
(KEPware.KEPServerEX.V5). This feature permits you to use one OPC Server vendor
if you have multiple OPC Server nodes on your network. This will allow OPC
clients to connect to a specific redundant pair by referring to the aliased
ProgID of that redundant pair.Always connect to primary machine
upon availabilityThis setting enables RedundancyMaster to
automatically promote communications back to the primary machine when the OPC
server becomes available.

Query Server Status
IntervalThis interval (specified in milliseconds) determines how
often RedundancyMaster will ping the underlying servers to determine if there
has been a loss of communications. By querying at a faster rate, you can
minimize fail-over time since failure detection occurs more
frequently.

Query Server Status TimeoutThis interval
(specified in milliseconds) determines how long the redundancy application will
wait for a ping response from the underlying servers before considering there to
be a loss of communications.

Monitoring Settings: This
feature allows you to configure certain conditions which will initiate a
fail-over to the inactive server. These conditions allow you to monitor server
items for specific states to determine the health of the underlying
servers/devices, above and beyond the automatic fail-over that will occur due to
the loss of communications.

Multiple OPC Server Pair RedundancyRedundancyMaster can
be configured to have multiple OPC Server Pairs. In this diagram there are two
pairs of OPC Servers which are gathering data from two separate device networks.
If the multiple OPC Server Pairs are all of the same ProgID
(KEPware.KEPServerEX.V4), then you will need to use the Aliasing feature; if the
two pairs have different OPC Servers with different ProgIDs then you will not
need the Aliasing feature.