Ignacio Aguirre
My feedback
-
9 votesIgnacio Aguirre
supported this idea
·
-
2 votesIgnacio Aguirre
shared this idea
·
-
2 votesIgnacio Aguirre
shared this idea
·
-
24 votes4 comments · PI Integrators » PI Integrator for Business Analytics · Flag idea as inappropriate… · Admin →
Please specify what kind of high availability is requested. For PI Integrator for BA to run in a highly available fashion?
To support other applications that are highly available? If so, which ones?
An error occurred while saving the comment Ignacio Aguirre
supported this idea
·
-
23 votesIgnacio Aguirre
supported this idea
·
-
5 votes
An error occurred while saving the comment Ignacio Aguirre
commented
The problem here is that although you delete archived events through Recalculation (mode: RangeDelete), PI Buffer will preserve its own snapshot value in memory.
If you have pibufss on the machine which you are sending data from, then pibufss is responsible for doing compression. PI Buffer Subsystem keeps the information about the most recent value it sent (i.e. local snapshot) and it performs compression only for events which has timestamp more recent than the local snapshot. So even if you delete all events on PIDA and from PIDA point of view events are coming in-order, from pibufss these events are out of order and won't be compressed (if they are older than the pibufss snapshot event).
You can check buffer-local snapshot by running the command pibufss -sd ptid where ptid is the Point ID for the tag you are interested in.
-
104 votesIgnacio Aguirre
supported this idea
·
-
18 votesIgnacio Aguirre
supported this idea
·
It might not be extremely necessary to have integrator level HA as it supports History Recovery. But it should be able to support SQL Backend HA.
For the Integrator, a SQL Server Standard or SQL Server Enterprise is recommended.
Most of the time this is a company SQL (non-only for PI purposes) which is built-in HA. This pushes our customers to acquire more SQL licenses.