Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide - Manual (Page 86)

UniInt Failover Configuration
80
Step Description
defined by the /UFO_ID startup command-line parameter.

The Heartbeat control tags for both copies of the interface on the
Historian Server must be changing values at a rate specified by the
/UFO_Interval startup command-line parameter or the scan class
which the points have been built against.
13. Test Failover by stopping the primary interface.
14. Verify the backup interface has assumed the role of primary by searching the
pipc.log file for a message indicating the backup interface has changed to
the “UniInt failover: Interface in the “Primary” state and
actively sending data to Historian. Backup interface not
available
.” The backup interface is now considered primary and the
previous primary interface is now backup.
15. Verify no loss of data in Historian. There may be an overlap of data due to
the queuing of data. However, there must be no data loss.
16. Start the backup interface. Once the primary interface detects a backup
interfa ce, the primary interface will now change state indicating “UniInt
failover: Interface in the “Primary” state and actively
sending data to Historian. Backup interface available.
” In
the pipc.log file.
17. Verify the backup interface starts and assumes the role of backup. A
successful start of the backup interface will be indicated by an informational
message stating “UniInt failover: Interface in “Backup
state.” Since this is the initial state of the interface, the informational
message will be near the beginning of the start sequence of the pipc.log
file.
18. Test failover with different failure scenarios (e.g. loss of Historian connection
for a single interface copy). UniInt failover guarantees no data loss with a
single point of failure. Verify no data loss by checking the data in Historian
and on the data source.
19. Stop both copies of the interface, start buffering, start each interface as a
service.
20. Verify data as stated above.
21. To designate a specific interface as primary. Set the Active ID point on the
Data Source Server of the desired primary interface as defined by the
/UFO_ID startup command-line parameter.