Notes Regarding Hot Backup Pairs

• You can use a hot backup only for InTouch 7.11 and later clients.

• If the Distributed Alarm Display object queries a hot backup pair and then queries the primary provider again separately, the Distributed Alarm Display object shows duplicate records.

• If a record at the primary provider is acknowledged and the secondary provider (which was down when the acknowledgment took place) starts up at a later time, the time stamp of the acknowledged record is identical with the record in the primary provider.

• The alarm consumer querying a hot backup pair shows the individual node name as the provider.

• You can choose any combination of design-time and run-time alarm record fields for mapping.

• When mapping the Value and Limit key fields, the values are rounded off to the fourth decimal place and then mapped.

• An alarm record that does not have the specific combination of design-time and run-time mapping uses the default runtime mapping.

• The Hotbackup Utility allows multiple hotbackup pairs with the exact same node names. This is only allowed for provider types Galaxy and Galaxy_<name>.

  For example, it is now allowed to add these two pairs in the utility:

Example 1

Pair Name: Pair1

Primary Node:Node1

Primary Provider:Galaxy

Primary Group:A01/

Backup Node:Node2

Backup Provider:Galaxy

Backup Group:A01

Example 2

Pair Name: Pair2

Primary Node:Node1

Primary Provider:Galaxy

Primary Group:A02/

Backup Node:Node2

Backup Provider:Galaxy

Backup Group:A02

Error reporting in the utility has been extended to provide the user feedback on any potential issues when trying to add pairs in this manner.

Note: You cannot enter a pair with the same node names and group name as a previous pair when using non-InTouch pairs. It will cause an error if you try to add the second pair with the same node name. For example:

Pair1: Node1: n1 node2: n2 group: a1

Pair 2: Node1: n1 node2: n2 group: a1