This type of saving is suitable first of all for a local alarm/event group (server), when the alarm/event group represents a place in the application where alarm/event items really arise and they are saved to the disk for needs of viewing. The window serves for the definition of backup parameters of a filled data file (alarm, event). Always when the file is filled by the specified number of records or when the defined time interval elapsed, it is closed and a new file is created with the name consisting of the backups list file name, the time when the file was created and an extension. This process proceeds so long until the specified number of backup files is created. If next backup has to be created but the number of backups is already spent, the oldest backup (file) is removed.
At application launch, a time sorted list of all data files is created in the memory based on the current data files with corresponding prefixes present in the specified folder. The sorting is done based on the time information contained in the file name (if the filename time identification fails then the first record is used, or the file modification time is used). Therefore it is acceptable to remove (backup) or add some data files while the application is not running.
In case of a remote alarm/event group (see the configurator "Remote group (client)"), it sets the way of getting the data for the history viewer by file sharing . The current alarm state is not transferred by this way. The alarm states have to be transferred somehow between groups and to set the states by a script. The simplest way, in this case, is to use the data sharing of the alarm/event group by means of the Remote connection over Web setting where both the state viewer (including the alarm confirmation)and the history viewer are active.
|Folder for files||Path to the folder with data files (text files *.al, *.ev). It is recommended to use the PROMOTIC path syntax - see PROMOTIC path to files and folders. For example #data:Alarm/. |
Caution!For each alarm/event object (the PmAlarmEvent object) different folder should be used. If the backup files of multiple groups are stored in a single shared folder, then at least the prefixes of such files must differ. This means that the individual groups must differ by the defined folder or file prefix (or both).
|File name prefix||The prefix - first part of the filename, for example alarm_. The whole filename consists of this prefix followed by time string, displaying the time of backup creation, and extension. For examplealarm_2007-01-15_18-45-43.al. |
Macro expression can be used for input (it is evaluated while the application is launching).
Note! In the past, there was a complete path to the backup configuraton file (*.alc, *.evc) here. In this case, the name prefix is taken from the file name in the complete path.
|Backup creation is defined by records count||If checked, the backup (creating new file) is performed on achievement of specified record number.|
|Backup creation is defined by time interval||If checked, the backup (creating new file) is performed periodically with the defined period (Every year, month, week, day, hour, minute, second).|
|Backup count is limited||Maximum number of backup files. If this number of files is achieved, the oldest backup file is replaced by the newest one.|
|Text data saved as||Defines the text data coding for saving into the files. It concerns primarily diacritic characters saving method.|
ANSI - dependent on OS Windows code page - The texts are saved using the national code page based on OS Windows setting. This method does not allow saving multilingual texts coded by different language code pages simultaneously (e.g. German and Czech).
UTF8 (Unicode) - independent on OS Windows code page - The text are saved using the universal UTF8 Unicode coding. This method is independent on OS Windows codepage setting, and also on the application main language setting. This method allows saving multilingual texts coded by differnt code pages simultaneously (e.g. German and Russian).