Core Historian enterprise features

Ignition
1

Thanks in advance for your suggestions, Ignition friends! With the new year, I’m looking to consider upgrading our enterprise to 8.3 from 8.1

One major concern I know the higher-ups will have is regarding the Core Historian. Is it true that currently, there’s no support for redundancy? I know the higher ups are going to insist that our primary enterprise historian be as resilient as is practical.

The main issue we have currently with 8.1 historian is that our teams occasionally need huge datasets out of the historian, and sometimes that causes issues in the app.

Is it possible to split incoming tag history to the core historian and then to a traditional database historian?

What is the current failover behavior of the core historian in a redundant pair?

2

If its current features don't fit your requirements, don't use it. All of the 8.1 historian mechanisms still work and will remain in place for any upgrade of Standard Ignition. If you are using Edge with redundancy, you may need to wait.

1 Like