60277 FAQ: FactoryTalk Historian SE Collectives

1 of 2

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60277

Rockwell Automation Support Center

60277 - FAQ: FactoryTalk Historian SE Collectives
Access Level: TechConnect
Date Created: 04/06/2009 03:56 PM
Last Updated: 01/27/2015 08:22 AM

Background
FactoryTalk Historian SE v2.1 added support for collectives (also known as 'high availability'). A collective consists of two FactoryTalk Historian SE servers that have the same
configuration database. This provides the same association between the key values in the FactoryTalk Historian SE table on both of the servers. This also ensures that the
data files have the same structure on both of the servers. For more information, refer to the Installation and Configuraiton Guide on the Historian media.

Frequently Asked Questions

Why use a collective?
Using a collective ensures that the FactoryTalk Historian SE data is always available to Historian clients as long as one of the servers is operational. A collective allows one
server to be taken offline for maintenance or upgrade without disrupting the availability of data to the clients. If a client is retrieving data from one of the servers and that server
becomes unavailable, the client will automatically switch to obtain the data it needs from the other server.
Can a single server FactoryTalk Historian SE v2.0 server be added to a collective without losing any existing historical data?
Yes. However, the FactoryTalk Historian SE system must first be upgraded to v2.1 to support the use of collectives. Then, the collective can be created using the existing
server option in the Collective Manager's Create New Collective wizard.
Is there an additional cost associated with creating a collective (vs. a single server)?
Yes, an additional server is required and two licenses must be purchased (one per server).
For example, if you are going to license your servers in the collective for 1000 FactoryTalk Live Data tags and 500 Third Party tags, quantity two of each of these licenses must
be purchased.
What is the minimum and maximum number of servers supported in a collective?
A FactoryTalk Historian SE Collective can consist of 1 or 2 servers.
With two Servers in a collective, one is identified as Primary and the other as Secondary. Any edits must be done to the Primary. The Primary then sends any configuration
changes to the Secondary automatically.
Why would I create a collective with only one server?
While the FactoryTalk Historian SE Installation and Configuration Guide indicates that this is possible, there is no practical reason for doing so.
Does a collective require a Windows Active Directory domain?
Contrary to what is indicated in the FactoryTalk Historian SE Installation and Configuration Guide, a collective does not require a domain. However, it does require fully
qualified domain names.
Therefore DNS must be properly configured on all Historian hosts using a DNS server (preferred) or Hosts files, and the Primary DNS suffix of this computer field must be
correct.
This field is accessed using Control Panel --> System --> Computer Name --> Change --> More.
The DNS name can be checked using NSLOOKUP. this is accessed by clicking Start --> Run to open the command line and then entering the command nslookup at the
prompt.
Does a collective require that buffering be enabled on the interface(s)?
Yes. Using the buffering feature is highly recommended in any situation, but it is required in order to get the data to both hosts in a collective. For more information, refer to
56721 - Things you should know about FactoryTalk Historian SE Buffering.
Is a collective created and monitored using the FactoryTalk Administration Console?
Not at the present time. Currently, a collective is created (and subsequently monitored) using the Collective Manager utility. This utility is only installed on a server (vs. an
interface) and launched using All Programs --> Rockwell Software --> FactoryTalk Historian SE --> FactoryTalk Historian SE System --> Collective Manager.
For more information, refer to 59354 - FactoryTalk Historian SE - Things you should know about using the Administration Console with Redundant Interfaces and Collectives.
Is there supplemental documentation available for creating a collective?
Yes, refer to 61952 - FactoryTalk Historian SE v2.1 (CPR9 SR1) Collective Configuration Guide.
For v3.00 and higher, this has been superceded with content in the Installation and Configuration Guide.
Are totalizers, performance equations and other "internal" values synchronized between Primary and Secondary servers in a collective?
No. Therefore these tags could contain different values at any given time.
How can the health of a Collective be monitored?
Typically the Collective Manager utility is used. However, two other options are available:
1. piconfig scripts located in %piserver%\adm
2. the Performance Monitor interface and OSISoft PI Server Collective.xml (located

in C:\Program Files (x86)\PIPC

\SMT3\PerfMonTagBuilder\Templates). For more information, refer to 59015 - FactoryTalk Historian SE and the PerfMon Interface.

Will the Advanced Computing Engine (ACE) work with a Collective?

Yes. However, there are some considerations for use with Collectives. For example, the ACE host computer must be separate from the Collective host computers.
In addition, the buffer subsystem should be installed on the ACE host.
Finally, ACE can only start when the collective's primary node is available.
For more information, refer to the ACE User's Guide and the High Availability User's Guide.
Can AuditViewer be used with a Collective?
Yes. For more information, refer to 459626 - FactoryTalk Historian SE: Using AuditViewer with a Collective.
Does a Collective work with Windows Firewall enabled on the Historian Servers?
Yes. For more information, refer to 335447 - FactoryTalk Historian SE: Windows Firewall settings for Collectives
Where can I find information on troubleshooting collectives?

19/3/2015 1:01 PM

60277 FAQ: FactoryTalk Historian SE Collectives

2 of 2

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60277

Refer to 524554 - FAQ - FactoryTalk Historian SE:Troubleshooting Collectives.

Comments (0)
This answer has no comments

Post a Comment

Product Tree for This Answer (expand/collapse)

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects.
Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services. Before making any
decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND
MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO
USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE)
PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that
certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

This page is best viewed in Internet Explorer 10, Firefox 31, Chrome 37, Safari 6 or newer.

19/3/2015 1:01 PM