NextGen Archiver (NGA) - FAQ

Is it recommended to add all data points to archive to only one group or is it better to add them to different groups?

If data point elements have different change rates and also different time periods for how long they should be available for online queries, it should be considered to create several groups, e.g. for "unsolicited values" and "compressed values" etc.

The more data point elements a project has, the more important this grouping becomes.

What is the record size per database?

The following table shows the record size per database:

How can a backup of the segments be made?

The backup of segments can be done in several ways:

• Backup before deletion: If the option Backup segments whose retention period is exceeded) is enabled, each segment is backed up before it is deleted from the database (reaching the maximum retention period).
• Periodic Backup: If the (option: Backup Interval) is used, those segments that are older than the configured value are backed up (Option: Backup Segments older than).
• Manual Backup: See chapter Segments and chapter Database-specific Configuration.
• Full DB Backup: See chapter a full backup .

Which amount of data should be available online in the database?

The amount of data available in the database (online data) should preferably be small (total size of online data). The retention period should be chosen accordingly, depending on the data needed for the ongoing operation of the system. Backed up archives can be restored at any time if needed.

Is there a limit to the number of "backed up segments"?

How much data can be backed up depends on the size of the backup medium.

The location for the backup must be configured as follows:

• InfluxDB®: in the Database-specific settings.
• PostgreSQL®: in the file db.windows.config file / db.linux.config file/dbBackupPath(dbBackupPath=c:/postgresql_backend/backups)
• MS SQL®: in the file db.windows.config file /dbBackupPath (dbBackupPath="d:\mssql\backups").