The settings for file management on the hard disk can be found on the Clean up tab.

Clean ups are intended to make the best possible use of the available disk space and to automatically ensure that sufficient space is always available for the most recent data. This clean up task is performed daily.

There is a preset clean up for the respective data types. These entries cannot be deleted and apply to all measurement conditions for which no specific clean up settings have been made. Therefore, no measurement condition can be selected in these preset clean ups.

Various settings can be made for cleaning up the file archive in the “Clean up task” table.

The Time range start and Time range end columns define the time range for which the data is to be thinned out. The Time span parameter specifies the intervals that the files should cover after the clean up (data file/time span). Any number of time ranges can be defined here. The clean up uses these time ranges to thin out the data. The time ranges are considered relative to the server time, e.g. "15d" means current server time minus 15 days.

To enable specific scenarios to be easily excluded from the clean up, it is possible to define blocked time ranges. They are not cleaned up and all data is retained.

Parameter overview:

Parameter

Description

Active

Only clean ups that are enabled will be performed. This setting is useful if you need to temporarily disable clean ups.

Path

The path to the clean up target is specified here. This path must be specified relative to the configured plant archive, e.g. CMU-103-200006\DAT\fft

Hard disk monitoring

Checks the freely available storage capacity. If this reaches a critical level, the oldest data is deleted until the storage capacity is back within a normal range.

Clean ups

This table contains the settings for the time spans for the clean ups and the time ranges that are not to be cleaned up. The “blocked time ranges” can be configured as required and are not included in the clean up.

The option of setting “blocked time ranges” is not available for ibaCMC V1.8.x plants.

Details of the clean up function:

The server cleans up all CMUs in turn. Starting from the current server time and working backwards into the past, it goes through them in the specified increments (time spans) and always retains only the most recent file from the relevant time span. The creation time of the file, which the CMU flags with the relevant local time, is taken as the reference. To ensure that the set time span (file/time span) is always achieved, it is possible that the next file chronologically after a blocked time range will be retained, and the set time interval from this file to the next will be temporarily shortened. The reason for this is that all files during these increments that fall within a blocked time range are ignored. It is thus possible that the most recent file in the time increment is in the blocked time range. As a result, the most recent file from this set is the one that follows directly after that time range.