Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Data rearchiving

  • Last UpdatedApr 24, 2025
  • 1 minute read

If Historical data that has already been archived is edited, it is automatically scheduled for rearchiving. Rearchive is triggered after each regular archive is performed by rts_archive.csc. The Archive program checks the rearchive table. If there are any entries in the table, the Archive program collects information from the schedule and catalog tables as required for rearchiving (for example, rearchive format and device). After the information is collected, the rearchive is performed.

The archive file name for rearchived data is identical to the original file name, except that the version number suffix is incremented each time the data is required. Therefore, the file name with the highest version number reflects the most current state of the data.

Rearchive Troubleshooting

If rearchiving cannot be scheduled in the rearchive table after data is modified or inserted, the reason may be one of the following:

  • The data being modified or inserted has not been previously archived.

  • The database and table in which the data was modified or inserted are not scheduled for archive in the schedule table.

  • The archive function is disabled in the RealTime Databases (RTDB) Job Scheduler (JSH) table.

  • The data being modified or inserted corresponds to the same period defined by the Start and End Times of an entry already in the rearchive table, which was created previously due to modification or insertion of the data in the same time interval in the same database and table.

If you need help to troubleshoot data rearchiving concerns, please contact your Service manager.

Related Links