Email Us at info@n3uron.com

Download N3uron
Back to videos

N3uron Node/ N3uron Redundancy

Database Considerations

Description

In this video of our N3uron Academy, we will share how to use N3uron’s Historian in a redundant architecture.

  • [02:23]  How Redundancy Works

  • [04:25]  Setting Up Redundancy

  • [03:50]  Redundancy Agent

  • [01:34]  Database Considerations

Transcription

[00:00] In this video we are going to explain some of the precautions you need to take when using neurons historian in a redundant architecture by default neurons historian module uses an embedded MongoDB database that is provided within the installer for data storage given that the embedded MongoDB databases for two redundant nodes are not synchronized when deploying a redundant architecture it’s necessary to use an external database so that historical data can be accessed from both nodes at all times. In the event that an embedded database was used rather than an external one, there would be no consistency between the data stored on both databases and they would behave like two completely independent data storages. In order to use an external database, you’ll need to change the default configuration of your historian module in both nodes. To do so, go to config in the system section and select your historian instance under modules. Next disable the embedded db engine under database. Finally set the parameters as required by the external database you will be using such as host port authentication etcetera