Connector-level Failover - OPC UA 2.x
Support connector-level failover in PI Connector for OPC UA 2.x (relay-enabled version). Similar to UniInt failover (interfaces), failover should be data source specific and always favor the data source in the better state.
We need this feature! Please implement this important feature. This is essential for a meaningful use in the production area.
Please give feedback on that. Fail-over is also very important for us !!!
High Availability is critical for our business. Particular in regulated industries like pharma it is a must have. I would like to know if fail-over functionality is on the OPC-UA 2.x road map?
We invested in HA solution at server side,
as data capture process needs to be secured end to end OPC UA failover is required.
Redundancy should be available for our mission critical data. End users are expecting high availability.
This is a dealbreaker for us. We won't be using the connector because it's lacking client redundancy.
Right now it seems to be the better solution for us to have an OPC UA to OPC DA bridge and the legacy OPC DA interface, adding another hop but redundancy makes up for that.
Balu (Balasubramaniam) Karthikeyan commented
The legacy SCADA systems are getting replaced by UA servers out-of-the-box. So OPC UA Connector is the preferred route.
Echoing what others have shared already, I think we can all agree with these two points:
1) Failover is a key pillar for the "critical infrastructure" very frequently present in all OSIsoft pitches; and
2) OPC UA is probably the most common standard in industrial communication.
Seeing that the OPC UA connector dropped the connector level failover feature in the new version (plus not having a clear roadmap for this) conveys a not so reassuring message to your customers who decided/take into consideration to engage a long strategic journey with you.
I hope to see this implemented very soon, thanks!
Hi OSIsoft, as others have pointed out, I'm baffled by the apparent backwards step in v2.x (i.e. no HA / failover support at the interface-level).
However I notice that OPC UA has native support for something called "Client Failover" (see the 'OPC UA Online Reference' here: https://reference.opcfoundation.org/v104/Core/docs/Part4/6.6.1/ )
I'm wondering if your intent is to support native OPC "Client Failover" under the new v2.x connector fork?
• You have two diverse PI OPC UA connectors (OPC UA 'clients') – both Active/Active – but one is operating in ‘backup’ mode
• The OPC UA ‘server’ maintains information on it’s active client sessions
• The ‘backup’ UA client monitors the client-session information on the UA server – and detects when the ‘active’ UA client has “failed”
• The ‘backup’ UA client then instructs the UA server to redirect all future traffic to itself
Is that on the cards for support in a future version of v2.x?
From Case:00812539, I need a Failover at the Connector Level just the same as we have for the OPC-DA Interface.
I learned that none of the "new" Connectors are able to have a redundancy on the Connector Level, so every Connector of a current Version is not useable for a Productive Environment in the chemical Production Environment.
Gabriel Verreault commented
FYI - OPC UA 2.x connector does support OPC UA Server redundancy. It does not support client-side (connector) redundancy, which is what this 'Idea' is about.
In this Case, both redundant OPC UA Service work in a mode (Active-Active), but this modality could change ...
Please, see a image with our needs.
2 PI Gateways connect a Redundant OPC UA Service for a Full Failover Scheme
The main Idea is if the "Connector Model" will be replace the "Interface Model", this components must have at least, the same functionalities and improve performance on its purpose. So, a upgrade version of a connector should improve the last version and not minimize it.