Rockwell Automation FactoryTalk Historian SE 4.0 Installation and Configuration Guide - Manual (Page 135)

Configuring Historian Servers in High Availability Mode Appendix A
Rockwell Automation Publication HSE-IN025A-EN-E–September 2013 135
NOTE
The following license activations are excluded from the point
limit check: AVIEW, FTBAInt, FHSE.H2H, FHSE.Advanced,
FHSE.OLEDB, and FHSE.OPC.
7. Click Apply.
If you have an insufficient number of the license activations
that need to be assigned to the primary and secondary server in
a collective, you are prompted to reassign the licenses:
Reassign the licenses, and then click Apply again.
To implement HA, configure interfaces to support failover and
n-way buffering. Failover ensures that time-series data reaches the
Historian server even if one interface fails; n-way buffering ensures
that identical time-series data reaches each Historian server in a
collective.
To support failover, install a redundant copy of an interface on a
separate computer. When one interface is unavailable, the
redundant interface automatically starts collecting, buffering, and
sending data to the Historian server. To support n-way buffering,
configure the buffering service on interface computers to queue data
independently to each Historian server in a collective.
In some deployments, interfaces send outputs (that is, data from the
Historian server) to the data source. With a proper configuration,
failover considers the availability of the Historian server for outputs
in addition to the availability of the interface.
NOTE
For more information, refer to the FT Historian High Availability
Administrator Guide, chapter "Interfaces".
Configuring Interfaces and
Buffering Services for
Historian Server Collectives