Data Archiving Overview

Business data of huge size and with lower access frequency can be archived. EnOS Data Archiving supports archiving data and synchronizing the archived data to target database and in specified directories, thus achieving data backup.

Features

Features of the Data Archiving service are as follows:

Archiving real-time data and offline data

EnOS Data Archiving support archiving both real-time data ingested from devices or generated by stream processing jobs of specified models and data integrated from the offline message channel.

Archiving real-time alert records

EnOS Data Archiving also supports archiving the specified fields of real-time alert records (both history and active alert records) of specified models.

Setting properties of archived files

You can set properties of archived files, including file type, encoding, column delimiter, compression, and size limit, based on your data usage scenarios. In this way, the archived files will be ready for future development and analysis.

Setting storage system and path

The archived files will be synchronized to the specified storage system (BLOB or HDFS) and stored in the configured path, thus achieving data backup.

Usage Limit

When using Data Archiving, the following usage limit should be noted:

Data archiving resource

Before configuring data archiving jobs, ensure that your OU has requested Data Archiving resource through the EnOS Consle > Resource Management page. For more information about requesting resources, see Resource Management on EnOS.

Number of supported archiving jobs

At most 5 data archiving jobs can be created for an organization.

Start time of data archiving

When a data archiving job is submitted, the system starts reading data from the specified message channel. However, if no data is cached in the archiving cycle when the archiving job is submitted, no archived file will be generated.

Data retention in case of job failure

The data retention time of the current message channel is 3 days by default. In case of job failure, data archiving jobs must be troubleshooted and restarted in time to avoid data loss.