Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status Completed
Categories Notifications
Created by Guest
Created on Aug 20, 2022

Future Plans for Notifications High Availability?

General Query: What are the future plans for High Availability of PI Notifications. To my understanding, the only option providing seamless failover is to utilise a Windows Server Failover Cluster, with high performance Shared Storage to hold the Notifications RunTime files. Are there any plans to make Notifications stateless, and store all data in SQL, where SQL AlwaysOn Availability groups can be utilised? Feedback much appreciated.
  • ADMIN RESPONSE
    Aug 20, 2022
    Marking this as completed as the original question has been answered.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    For PI Notifications, similar to AF and Analytics, high availability requires that you provide a failover for the service itself and the SQL backend. The recommended HA solution for PI Notifications using Windows Server Failover Cluster (WSFC) is solely for PI Notifications Service. The assumption is that some kind of HA solution is already implemented for AF Application Service and the SQL backend, with SQL Server Always On being the current recommended HA solution.
  • Guest
    Reply
    |
    Aug 20, 2022
    Making the Notifications Service Stateless or storing the State information in SQL Server is a good first step. I would to make the service run as a redundant pair in the way the interfaces work and remove all WSFC requirements.