General Discussions
Tiered Historian

Does VTSCADA have a tiered or second level historian that receives unsolicited data from level one historians?

Does VTSCADA have a tiered or second level historian that receives unsolicited data from level one historians?

Hi, thanks for your question. After looking online it looks like the "Tiered" terminology comes from the Wonderware/Aveva model. What I think you are asking might be, "Does VTScada automatically synchronize historical data across multiple backup historians?" Is that correct?

As you may know, VTScada has a built-in Enterprise Historian that makes it simple to configure any number of geographically distributed Historians the bi-directionally synchronize with one another. In its simplest form, you could, for example, set up four distributed servers in redundant fashion with hot backup failover. The primary server would poll and log the data and the other three would sync with the primary. You can also set up one server to be the primary historian for site A and the secondary for site B. And vice versa. There are lots of ways to set up more sophisticated scenarios that provide load sharing and distributed redundancy.

The important thing to understand about all of these options is that they do not involve any custom coding and can be set up in minutes. Our historian is not licensed separately and does not require a completely separate backup strategy. Many other SCADA products require that the one backup historian must be at the same site as the primary with a physical patch cable. VTScada does not have any of these limitations.

Or... you may be asking if VTScada also logs to redundant third-party relational database products like PI or Oracle. The answer is yes, we do but we would ask why you need to do this since this will incur separate licensing and support costs and add unnecessary complexity.

Do either of these answer your question? If not, please describe what you are hoping to achieve.

Hi, thanks for your question. After looking online it looks like the "Tiered" terminology comes from the Wonderware/Aveva model. What I think you are asking might be, "Does VTScada automatically synchronize historical data across multiple backup historians?" Is that correct? As you may know, VTScada has a built-in Enterprise Historian that makes it simple to configure any number of geographically distributed Historians the bi-directionally synchronize with one another. In its simplest form, you could, for example, set up four distributed servers in redundant fashion with hot backup failover. The primary server would poll and log the data and the other three would sync with the primary. You can also set up one server to be the primary historian for site A and the secondary for site B. And vice versa. There are lots of ways to set up more sophisticated scenarios that provide load sharing and distributed redundancy. The important thing to understand about all of these options is that they do not involve any custom coding and can be set up in minutes. Our historian is not licensed separately and does not require a completely separate backup strategy. Many other SCADA products require that the one backup historian must be at the same site as the primary with a physical patch cable. VTScada does not have any of these limitations. Or... you may be asking if VTScada also logs to redundant third-party relational database products like PI or Oracle. The answer is yes, we do but we would ask why you need to do this since this will incur separate licensing and support costs and add unnecessary complexity. Do either of these answer your question? If not, please describe what you are hoping to achieve.
27
1
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft