Rockwell Automation FactoryTalk Historian SE 3.01 Installation and Configuration Guide - Manual (Page 118)

Appendix A Configuring Historian Servers in High Availability Mode
118 Rockwell Automation Publication HSE-IN024A-EN-E–December 2012
and write identical data on each server. Together, this set of
servers, called a
FactoryTalk Historian server collective, acts as
the logical FactoryTalk Historian server for your system. The
server collective receives data from one or more interfaces and
responds to requests for data from one or more clients. Because
more than one server contains your system data, system
reliability increases. When one server becomes unavailable, for
planned or unplanned reasons, another server contains the
same data and responds to requests for that data. Similarly,
when the demand for accessing data is high, you can spread
that demand among the servers.
• Redundant interfaces
To implement HA, configure interfaces to support failover
and n-way buffering:
• Failover ensures that time-series data reaches the
FactoryTalk Historian server even if one interface fails.
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 FactoryTalk Historian
server.
• N-way buffering ensures that identical time-series data
reaches each FactoryTalk Historian server in a collective.
To support n-way buffering, configure the buffering service
on interface computers to queue data independently to each
FactoryTalk Historian server in a collective.