EOS SCADA Archiving Architecture

The EOS SCADA data archiving structure is not limited to simply writing data to a database. The archiving architecture can be designed by considering permanent SQL archiving, high-volume Big Data storage, high-speed In-Memory access, and, when required, redundant main/additional archives together.

Core roles of the archiving layers:

  • SQL: Storing permanent and structured process data together with historical records.
  • Big Data: Managing high-volume and long-term data archives.
  • In-Memory: Providing very fast access to recent data and accelerating live monitoring and graphing operations.
  • Main and Additional Archives: Meeting data continuity, redundancy, and different data retention requirements.

Therefore, the selection of ArchiveType is not merely a technical database choice. It is a fundamental architectural decision that should be evaluated together with the SCADA system's data storage capacity, access speed, historical analysis requirements, and redundancy strategy.

EOS SCADA Data Archiving Structure

EOS SCADA can permanently archive process data in SQL and Big Data environments permanently archive; In-Memory veri tabanı ile particularly for liand monitoring, fast data retrieval, and graphing operations.

Database environments:

  • Firebird: SQL database.
  • MongoDB: Big Data database.
  • REDIS: In-Memory database.

In addition to this architecture, multiple main and additional databases can be defined according to the redundancy approach used. This helps reduce the risk of data loss, implement different archiving policies, and expand the archiving infrastructure when required.

Using the In-Memory Database

In-Memory veri tabanı, by keeping data in the computer's main memory, removing disk access from the data query path. This approach can be used for very fast retrieval of recent process data, feeding live trends, and accelerating graphing operations on SCADA screens.

CAUTION: Temporary data held in RAM may be lost in the event of a power failure. Bu nedenle SCADA uygulamalarında bellek içi veri databases that use disk storage is beneficial for data safety.

Opening the Main Database Menu

In the SCADA tree menu, left-click VERİ TABANI. It contains SİSTEM VERİ TABANI, ANA VERİ TABANI and YEREL VERİ TABANI.

To edit the general settings, select the ANA VERİ TABANI submenu. The settings table on the right opens.

Main Database General Settings

Property Name Property Description Default Value
LiveDBActive Live Database Active false
DBMultiThreadMode Database Multi-Threading Mode false
TimeStampType Timestamp Type Packetmedian (Packet Send/Receive Median)
TimeStampPosition Timestamp Position Last (Last Table Column)
ArchiveType Archive Type Sql (SQL)
InMemortyResetType In-Memory Reset Type Day (Day)
InMemortyStorageInterval In-Memory Storage Interval Oneday (1 Day)
DBRecordingMode Database Recording Mode Periodic (Periyodik)
DBStorageInterval Retention Period for Data Archived on Disk Threemonths (3 Months)
VirtualTableMethod Virtual Table Method Taglist (Tag List)

Archive Type

ArchiveType, the archiving approach used by the main database. It is a fundamental parameter that determines how the main database operates. When making a selection, data volume, retention period, access speed, and redundancy requirements should be considered together.

  • Sql: SQL
  • Bigdata: Big Data
  • Inmemory: In-Memory Database
  • Sqlandinmemory: SQL and In-Memory Database
  • Bigdataandinmemory: Big Data and In-Memory Database

CAUTION: The amount of data that can be stored in the In-Memory database is limited by RAM capacity. A disk-based architecture should be preferred for large archives.

Role of Big Data Archiving

Big Data approach provides an important option for managing large volumes of process data accumulated over long periods. It is particularly useful in large SCADA systems with many tags that continuously generate data; using a Big Data infrastructure alongside the conventional archiving structure can increase archiving capacity.

Important: Big Data archives should be considered in scenarios requiring long-term data retention and analysis of large data sets. In-Memory architecture, in contrast, can be used primarily for speed-focused access to recent data. can be used.

Timestamp Settings

Option Description
Packetsent Time when the packet was sent
Packetreceive Time when the packet was received
Packetmedian Median of packet send and receive times
Databasewritepc PC time when the data was written to the database
Databasewritedb DB time when the data was written to the database

TimeStampPosition, determines whether the timestamp is located in the first or last column in SQL archive tables.

CAUTION: If the source device or protocol already provides a timestamp for the data, this parameter may not need to be used.

In-Memory Storage and Reset

InMemortyStorageInterval; the period for which data is kept in the In-Memory database. For example, when Oneday is selected, data from the last 1 day is retained.

InMemortyResetType options are None (None), Day (Day) ve Full (Full) olarak can be used.

None is selected, data remaining from the previous session may be preserved after the first connection.

Data Recording and Retention Settings

DBRecordingMode can use Periodic or Aschanged (Değiştikçe) yöntemleri can be used.

DBStorageInterval options include None, 1 Month, 3 Months, 6 Months, 1 Year, 2 Years, 5 Years, 10 Years, and Harddiskquota (Hard Disk Quota).

Creating the Main Archive Database List

After the general settings, connection information must be entered for each main archive database. Right-clicking ANA VERİ TABANI opens the Main Database Status Menu.

This menu can be used to add, copy, cut, paste, delete, and reorder main databases.

Main Database Connection Properties

Property Name Property Description Default Value
MainDBId Main Database ID 0
MainDBActive Main Database Active false
MainDBTitle Main Database Title MAINDB
MainDBHostName Main Database Computer Name (IP Address) localhost
MainDBPort Main Database Connection Port 3050
MainDBPath Main Database Path C:\DataLogger\FDB
MainDBName Main Database Name eosdb
MainDBSID Main Database Session ID (SID) DataLogger
MainDBTimeOut Main Database Timeout 1000
MainDBUserName Main Database User Name sysdba
MainDBPassword Main Database Password masterkey
MainDBWriteFrequency Main Database Write Frequency 1

CAUTION: Connection information such as user names and passwords must be stored securely in the actual system. The default values shown here are example values from the source documentation.

Main Archive Database Configuration Workflow

  1. Open the DATABASE menu.
  2. Select the MAIN DATABASE submenu.
  3. Configure the general archiving settings.
  4. Right-click ANA VERİ TABANI.
  5. Add a new Main Database.
  6. Enter the connection information.
  7. Add backup databases if required.
  8. Check the archiving and retention settings.

Conclusion

EOS SCADA Editor settings for MAIN DATABASE allow you to define the archive type, timestamp method, In-Memory retention period, data recording behavior, and disk-based retention period.

Firebird based SQL archiving, MongoDB-based Big Data archiving, and REDIS-based In-Memory access can be used together to support SCADA archiving architectures suited to different capacity, performance, and data access requirements.

With proper planning of main and additional data archives, permanent data retention, fast live access, management of high-volume historical data, and redundancy requirements can be addressed within a single integrated data archiving approach.

← Back to Previous Content