Backup copies

In addition to the original of a decision table, LF‑ET also automatically saves up to 10 backup copies with consecutive numbering. The most recent backup copy always has the smallest number:

siteevaluation.lfet
siteevaluation.lfet.1.$bak
siteevaluation.lfet.2.$bak
siteevaluation.lfet.3.$bak

Once you have completed working on a decision table, backup copies are packed into a single ZIP file:

siteevaluation.lfet
siteevaluation.lfet.$bak.zip

Backup copies remain unpacked only as long as the deci­sion ta­ble is opened in LF‑ET.

If necessary, the settings for creating backups can be customized through keys in the Project.ini file.

1) BackupHistoryZip = true | false (default: true)

  • Packing of backup copies in a ZIP file can be suppressed with the false value.

2) BackupHistoryLength = n (default: 10)

  • The maximum number of backup files per decision table is between 0 and 50

  • The creation of backup files can be deactivated with the 0 value

  • If the number of backup files already saved for a decision table is greater than the value specified here, this number is used as the value

  • When the maximum number of backup files is reached, the oldest backup file is deleted

  • All backup files saved are sorted chronologically and, starting from number 2, renumbered again

  • At the end, the current original file is saved as a backup file with number 1

3) BackupHistoryFolder = xxx

  • The name of the folder, e.g. Backup, in which backup files are to be saved

  • It must be a direct subfolder of the decision table folder

  • If the folder does not exist yet, it is created auto­matic­ally, backup files already existing for the decision table are auto­matic­ally moved to the new folder

  • If problems arise, the user receives an exact error message and the folder information is ignored, i.e. backup files are stored in the deci­sion ta­ble folder

4) BackupHistoryRoot = x:/xxx/xxx/…​

  • The path to a "root directory" under which the backup files, including the respective folder structure, should be saved

  • This key overrides any BackupHistoryFolder that may be present, i.e. any existing BackupHistoryFolder specification is ignored

  • The path structure specified here must already exist

  • It must be a "minor branch" to the deci­sion ta­ble path, i.e.

    1. It must match at least the drive and optionally some folders

    2. It must be different in at least one directory "above" the decision table folder

  • The matching part is removed from the decision table path, the remainder "below" is added to the specified "root folder" so that the system-wide uniqueness of the folder structure (path + DT name) is ensured even with the backup files

  • If problems arise, the user receives an exact error message and the folder information is ignored, i.e. backup files are stored in the decision table folder

5) BackupHistoryVersion = V02

  • A new, higher-performance version of backup file management can be selected with the V02 value

  • If deci­sion ta­bles are located on network drives, in rare cases there may be disruptive delays while saving

  • Management of backup files can be specified as the cause, which led to the provision of this second version

Further information