Phase 2

UniInt Failover Phase 2 is supported on a per-interface basis for interfaces built with UniInt 4.4.0.0 and later. See the individual interface user guide for the type of failover supported by the interface.

If an interface supports UniInt Failover Phase 2, the Synchronization File Path field is populated and a UFO Type is selected from the drop down list.

If an interface supports both Phase 1 and Phase 2 UniInt Interface Level Failover, then two option buttons will appear at the top. You select the type of failover to enable. If the interface only supports Phase 2 this option button is automatically selected.

• Phase 1 / Phase 2

  If the interface supports both types of failover, you must choose which type to use. If it only supports one type, the other option is disabled. This must be the first item you select when configuring failover.

• Failover ID# for this instance

  In a failover interface installation, each copy of the interface has its own unique positive integer identifier. This identifier is referred to as the failover ID and is specified with the interface startup parameter /UFO_ID=n.

• Failover ID# of the other instance

  This is the failover ID assigned to the other interface in the failover pair. By default, the pairs are named 1 and 2.

  See Select the other interface of a failover pair.

• Do Not Failover when both interfaces lose connection to PI

  This option can only be used with interfaces built with UniInt 4.5.1.0 and later. It is used to prevent the primary and the backup failover pair from both buffering data when they have lost connection to PI Server. /UFO_DNFBPI is the equivalent startup parameter.

• Failover control tags are unsolicited (not scan based)

  The failover update interval determines the rate at which UniInt updates the heartbeat points, how long it takes for the interface to fail over, and how much overlapping data can be sent to PI Server. The optional /UFO_Interval=# startup parameter specifies the failover update interval for unsolicited failover control points.

  Both interface copies participating in failover must use the same failover update interval. The failover update interval, #, is specified in milliseconds with the default being 5000 milliseconds or 5 seconds. The minimum interval is 50 milliseconds.

  You can change the failover update interval in the Rate at which the heartbeat point is updated/checked field.

• UFO Type

  UniInt Interface Level Failover Phase 2 can be configured for one of three types: HOT, WARM or COLD. PI ICU will only allow you to choose types supported by the interface you are configuring. The default type is COLD.

  The command-line equivalent for this parameter is /UFO_Type=<type> where <type> is HOT, WARM or COLD.

• Synchronization File Path

  This identifier is referred to as the UniInt Failover synchronization path and filename. It is specified with the interface startup parameter, /UFO_Sync=<path_filename>.

  The default file name should be <exe_name>_<ps>_<id>.dat where <exe_name> is either the name of the executable or the short interface name, <ps> is the point source (/ps) and <id> is the interface id (/id).