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

UniInt Failover Configuration
82
Parameter
Required/
Optional
Description Value/Default
exist, the first interface to start
attempts to create the file.
Note:
If using the optional
filename, do not supply a
terminating slash or backslash
character.
If there are any spaces in the path
or filename, the entire path and
filename must be enclosed in
quotes.
Note:
If you use the backslash
and path separators and enclose
the path in double quotes, the final
backslash must be a double
backslash (
\\ ). Otherwise the
closing double quote becomes
part of the parameter instead of a
parameter separator.
Each node in the failover
configuration must specify the
same path and filename and must
have read, write, and file creation
rights to the shared directory
specified by the path parameter.
The service that the interface runs
against must specify a valid logon
user account under the
“Log On”
tab for the service properties.
/UFO_Type=type Required The Failover Type indicates which
type of failover configuration the
interface will run. The valid types
for failover are HOT, WARM, and
COLD configurations.
If an interface does not supported
the requested type of failover, the
interface will shutdown and log an
error to the
pipc.log file stating
the requested failover type is not
supported.
COLD|WARM|HOT /
COLD
/UFO_Interval=# Optional Failover Update Interval
Specifies the heartbeat Update
Interval in milliseconds and must
be the same on both interface
computers.
This is the rate at which UniInt
updates the Failover Heartbeat
tags as well as how often UniInt
checks on the status of the other
copy of the interface. 50 - 20000 / 1000