FactoryTalk Historian Site Edition: Configuring Redundancy and High Availability
-
Upload
rockwell-automation -
Category
Technology
-
view
1.502 -
download
20
description
Transcript of FactoryTalk Historian Site Edition: Configuring Redundancy and High Availability
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
PUBLIC INFORMATION
FactoryTalk® Historian Site EditionMI14 Configuring Redundancy and High Availability (Session ID XYZ)
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Agenda
Interface Redundancy
Collectives (Server Redundancy)
Introduction
Related Sessions
2
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
2014 FactoryTalk Historian Sessions
3
Session Title Type
MI09 Introduction to FactoryTalk Historian: Overview Strategies for Collecting and Analyzing Data Discussion
MI10 FactoryTalk Historian Site Edition: Architectures and Design Considerations Discussion
MI11 FactoryTalk Historian Machine Edition: Basic Configuration in ControlLogix® Rack Lab
MI12 FactoryTalk Historian Site Edition: Basic Lab on Data Collection and Reporting Lab
MI13 FactoryTalk Historian Site Edition: Advanced Lab Lab
MI14 FactoryTalk Historian Site Edition: Configuring Redundancy and High Availability Discussion& Demo
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Introduction
This session will discuss and demonstrate FactoryTalk Historian Site Edition: Collectives (for data access) Interface Redundancy (for data collection)
This presentation is based upon KnowledgeBase Answer ID 59354 -FactoryTalk Historian Site Edition: Using the Administration Console with Redundant Interfaces and Collectives.
A frequently asked questions format will be used…
4
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Site Edition Security has Changed!
V2.x used FactoryTalk Security: Users: FT Historian installation created 4 “FTH’ Groups in FactoryTalk
Directory Computers: Were required to join the FactoryTalk Directory PI Connections: Were relatively automatic
V3.x (and higher) uses Windows Authentication and FactoryTalk Security Users: Now managed with Windows (Domain preferred) Computers: Still required to join the FactoryTalk Directory PI Connections: Require mapping Windows Users/Groups to
FactoryTalk Historian Users/Groups using System Management Tools > Security > Mappings & Trusts > Mappings
For more information, refer to the Configuring FactoryTalk Historian Site Edition Security Guide located on the distribution media.
5
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Building a FactoryTalk Historian SE System
What are the software components required to create a FactoryTalk Historian Site Edition system?
Every FactoryTalk Historian Site Edition v4.00 system includes the following software components:1. Network FactoryTalk Directory (FTD) and FactoryTalk Activation Server2. Data Server(s) - e.g., RSLinx Enterprise3. FactoryTalk Live Data Interface (FTLD)4. FactoryTalk Historian Site Edition Server5. FactoryTalk Historian Asset Framework/SQL Server6. FactoryTalk Historian Clients - e.g. FactoryTalk VantagePoint, FactoryTalk
View, FactoryTalk Historian DataLink, FactoryTalk Historian ProcessBook
6
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Architectural Recommendations
Are all of these FactoryTalk Historian Site Edition components supported on a single host computer?
Yes, but only for very small systems. For more information, refer to KB Answer ID 62869 - FT Historian SE and FT VantagePoint on a Single Host Computer.The recommended Historian Site Edition architecture consists of at least three host computers:1. Network FactoryTalk Directory & Asset Framework/SQL Server2. FactoryTalk Historian Server3. Data Server and FactoryTalk Live Data Interface
Using three host computers facilitates: - Data Collection Buffering- Adding High Availability later
7
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Building a Redundant FactoryTalkHistorian SE System
Which software components used to create a FactoryTalk Historian Site Edition system can be redundant?
1. Data Server(s) - e.g., RSLinx® Enterprise2. FactoryTalk Live Data Interface (FTLD)3. FactoryTalk Historian Site Edition Server*
* The designated primary Site Edition Server must be available in order to make configuration changes to the Collective.
8
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Agenda
Interface Redundancy
Server Redundancy
Introduction
Related Sessions
9
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
The FactoryTalk Historian SE Server
What is the role of the FactoryTalk Historian Site Edition Server?
The role of the FactoryTalk Historian Site Edition Server is to: receive the data from the FactoryTalk Live Data Interface nodes compress the data for efficient storage calculate ‘derived tags’ (totalizers and performance equations) serve the data to clients for reporting purposes
10
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Server Collective
Why use a FT Historian Server Collective?
To ensure uninterrupted availability of data for reporting: If the primary FactoryTalk Historian server fails during maintenance or upgrade of either FactoryTalk Historian
server
11
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Server Collective
Is there an additional licensing cost associated with FactoryTalk Historian Server Collective?
Yes, you must purchase 1 license for each server in the Collective. For example, to license a Collective for 500 FactoryTalk Live Data points and 500 third-party points, use must purchase two of each license (four licenses must be installed on the FactoryTalk Activation Server).
12
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Server Collective
Are totalizers, performance equations and other “derived tags" synchronized between Primary and Secondary servers in a Collective?
No. They are evaluated asynchronously on each server and therefore these tags could contain different values at any given time.
13
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Configuring FactoryTalk Historian Server High Availability
Is FactoryTalk Historian Server Collective implemented in the same manner as HMI Server Redundancy?
No, additional steps are required. Refer to the FactoryTalk Historian Site Edition v4.00 Installation & Configuration Guide (Appendix A).
14
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Server Collective
If firewall(s) exist between the two members of a Collective, what port(s) must be opened?
TCP 445
15
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk AF Server Collective
Are FT Asset Framework Server (FTAF) collectives supported by Rockwell Software like they are by OSIsoft?
Not at this time. Each member of the FactoryTalk Historian Site EditionServer Collective will point to the non-redundant FactoryTalk Asset Framework Server.
16
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Server Collective
Is the Collective creation procedure identical for both a new system and an existing system (with valuable archived data)?
No. There are minor differences. The Collective Manager demonstration will be for a new system
installation.
17
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Demonstration: Creating a Collective
Creating a Collective:
1. Using FactoryTalk Administration Console, create the initial (primary) Historian Server in the FactoryTalk Directory.
2.Using FactoryTalk Administration Console, delete the FTLD1 Interface that was automatically created on the Historian Server.
3.Using the Collective Manager, create the Collective and accept the new ID.
4. Using FactoryTalk Administration Console, make a new connection to the Collective.
5.Using FactoryTalk Administration Console, assign activation to the Historian Collective (and restart the servers).
COLLECTIVE
18
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Agenda
Interface Redundancy
Server Redundancy
Introduction
Related Sessions
19
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
The FactoryTalk Live Data Interface
What is the role of the FactoryTalk Historian Site Edition Live Data Interface?
The role of FactoryTalk Live Data Interface is to: collect the data from the data server(s) perform exception filtering deliver the data to the FactoryTalk Historian Site Edition Server for
long-term storage
20
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
FactoryTalk Historian Live Data Interface Redundancy
Why use Live Data Interface Redundancy?
To ensure uninterrupted data collection: If the primary Interface fails during maintenance or upgrade of either Live Data interface
While and additional computer is required, there is no addition FactoryTalk Historian Site Edition licensing cost associated with implementing interface redundancy!
21
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Live Data Phase 1 vs. Phase 2 Interface Redundancy
Are there two versions of Live Data Interface Redundancy?
Yes. v2.0 supported ‘Phase 1’ Live Data Interface Redundancy. v2.1 introduced support for ‘Phase 2’ Interface Redundancy. V3.0 (and higher) continues to supports both
‘Phase 2’ Interface Redundancy is recommended because it eliminates the need to write back to the control system for coordination (a file share is used instead).
22
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Configuring FactoryTalk Live DataInterface Redundancy
Is FactoryTalk Live Data Interface Redundancy implemented in the same manner as Data Server Redundancy?
No, currently additional steps are required. Refer to 59932 -FactoryTalk Historian Redundant Interface Configuration Guide (linked from 59354).
23
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Demo: Creating Redundant Interfaces
Creating Redundant Interfaces:1. Create the shared folder on a file server.
2. Using FactoryTalk Administration Console, create the primary FactoryTalk Live Data Interface (FTLD1).
3. Using the Interface Configuration Utility (ICU), enable buffering on the primary FTLD1 interface.
4. Using the Interface Configuration Utility (ICU), create the backup FTLD1 interface (and Create the Service).
5. Using the Interface Configuration Utility (ICU), enable buffering on the backup FTLD1 interface.
6. Using the ICU, configure the primary FTLD1 interface for Phase 2 Failover.
7. Using the ICU, configure the backup FTLD1 interface for Phase 2 Failover.
8. Using the ICU, configure primary FTLD1 interface service properties for file share access.
9. Using the ICU, configure backup FTLD1 interface service properties for file share access.
COLLECTIVE
24
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Interface Redundancy States
What are the possible States a Redundant Interface?
25
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Redundancy Synchronization
Are Data Server and Live Data Interface redundancy synchronized?
No. They are completely independent of each other.
26
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Monitoring Redundancy via HMI
Can Data Server, Live Data Interface and HMI redundancy be monitored via FactoryTalk View Site Edition?
Yes. Refer to 64501 - Determining the FactoryTalk Historian Site Edition Redundant Interface Status in a FactoryTalk View Site Edition Display.
27
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
Summary
To ensure against the loss of data visibility, use a Collective Doubles the server licensing requirements Configured with the FactoryTalk Administration Console and the
OSIsoft Collective Manager To ensure against the loss of data collection, use Interface Redundancy
No additional software cost Configured with the FactoryTalk Administration Console and the
OSIsoft Interface Configuration Utility They are mutually exclusive, but using Collective typically always includes
Interface Redundancy.
28
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
PUBLIC INFORMATION
Questions?
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.
www.rsteched.com
Follow RSTechED on Facebook & Twitter.Connect with us on LinkedIn.
PUBLIC INFORMATION
Thanks for Attending!Please complete the survey (Session ID XYZ)