PI-HA (High Availability)

Apresentação em tema: "PI-HA (High Availability)"— Transcrição da apresentação:

1 PI-HA (High Availability)
Vitoria Agra – OSIsoft do Brasil

2 O que devemos fazer?

3 O que acontece quando? PI-SDK PI Server Bufferização dos dados
Interface do PI

4 PI Replication Architecture
System Management Tools Módulos clientes: RtPortal, RtWebParts, Rich Clients: ProcessBook, DataLink, Custom Application… PI-SDK PI Server Data Buffering Services PI Interfaces Define – Collective, Primary, Secondary Server Discuss configuration flow Interface Buffering fanning data Client Applications conversation with collective is mediated by SDK to provide automatic failover capabilities. Bufferização dos dados Interface do PI

5 Replicação do sistema PI
What you will get: Ability for clients (ProcessBook) to select among replicated servers Changes to configuration data (points, modules) regularly synchronized between replicated servers Near-Identical time-series data between replicated archives (within compression specs) Apologies for not delivering exactly what customers asked for…

6 PI Replication Architecture
System Management Tools Modulos Clientes: RtPortal, RtWebParts, Rich Clients: ProcessBook, DataLink, Custom Application… PI-SDK Servidor Secundário do PI Servidor Primário do PI Servidor N do PI Alterações nas configurações PI Server Coletivo Define – Collective, Primary, Secondary Server Discuss configuration flow Interface Buffering fanning data Client Applications conversation with collective is mediated by SDK to provide automatic failover capabilities. Identical Time-Series Bufferização Dos dados Interface do PI Bufferização dos dados Interface do PI Failover Mechanism

7 PI Server Replication What you will get: automatically
Ability for clients (ProcessBook) to select among replicated servers Changes to configuration data (points, modules) regularly synchronized between replicated servers Near-Identical time-series data between replicated archives (within compression specs) automatically + load balancing any PI-SDK based in real-time Apologies for not delivering exactly what customers asked for… (+ no changes to your displays)

8 PI - HA Características Importante Sincronização da configuração
Faiolver transparente para as aplicações clientes Entrega de dados múltiplas para diversos servidores Importante Alta disponibilidade do PI Tranquilidade para os administradores Simples.. Direct support No changes to displays or spreadsheets. New SDK provides Failover even with older apps Scalable architecture: Support for systems of all sizes No specialized hardware requirement Geographic Availability Disaster Recovery

9 Limitações Dados advindos de outros sistemas, não automticamente (entrada de dados) Dados de bateladas PI-ACE WORKAROUNDS exist for these and other minor issues. Non Interface PItoPI – configure app to go one node only, primary. PItoPI goes between primary and other secondaries. Data is eventually moved but is not “highly available”. Future: Server side buffering See Denis’ talk (PR2- D1) API apps will automatically use buffering and work (e.g. OPC HDA server) and participate in N way buffering BatchRun pibagen on each server (different guids generated) Periodically apply archive backups from the primary Future – server side buffering will automatically replicate batch records (PR2-D1). Post Process PE’s, Totalizer, Alarms, Recalculator, SQC Run independently on each server, schedule not synchronized, results may vary slightly (scan based PE’s can differ the most) Future – PI Analytics (PR 3) ACE – new calcs, stopping calcs requires primary

10 PI – HA Futuro… … Data Mining, Business Intelligence Services
Aggregated, Federated PI Server Enterprise Data Center PI Server Node … Data Mining, Business Intelligence Services PI Clients Client Access Layer PI Caching Server Regional Center 2 Regional Center 1 Aggregated PI Server Near term Replication of Non Interface data Server side buffering Archive and Snapshot Mirroring – copy of data without PItoPI (no arbitration – static replication paths (from this server to that server) Mid term Load balancing Arbitration (dynamic replication path based on node availability) First cut at an Aggregated PI Server Aggregation unit is an Archive set (point partitition) (granularity) Long Term More refined aggregated servers Federated servers – Grid computing – Storage and processing is virtualized across multiple machines. data storage and collection is distributed PI Interfaces Site A Secondary PI Server Primary PI Interfaces Site B Secondary PI Server Primary Archive Mirroring Primary PI Server