40.17 Backups
40.17.1 Overview ¶
In the Backups area you configure the automatic data backup of the program configuration. All relevant configuration files are backed up - profiles, email accounts, database connections, printers, options and more. The log databases (processing and error log) and the Transfer folder are deliberately excluded, because they would be rebuilt on a new system anyway - this keeps the backup small.
The manual backup via File - Back up application data… is unaffected - the schedule configured here is an additional, automatic variant.
40.17.2 Activation ¶
| Field |
Description |
| Create backups |
Enables automatic backup. As long as this option is disabled, all other inputs in this area are locked |
40.17.3 Schedule ¶
| Field |
Description |
| Back up regularly |
Enables interval mode |
| Every X hours |
Hour interval (1 to 168) between two backups |
| Back up after profile changes |
Creates an additional backup after profile changes. To avoid creating a separate backup for every single save, the program waits 15 minutes of quiet before creating the backup. With consecutive saves, the waiting time is pushed back each time - so an edit session produces exactly one backup with the final state, instead of ten backups for ten saves. |
Both triggers are combinable. A typical configuration: every 4 hours in the background + additional backup after manual changes.
40.17.4 Backup Directory ¶
| Field |
Description |
| Backup directory |
Target path in which the ZIP backups are stored. Required field as soon as Create backups is active |
| … |
Opens a folder selection dialog |
Note: If Create backups is active but the directory remains empty, an orange inline warning appears as well as a confirmation dialog on OK/Apply - a missing path entry would make all backup attempts fail.
40.17.5 Retention ¶
| Field |
Description |
| Maximum number of backups |
How many backup ZIPs are kept at most. If exceeded, the oldest are deleted |
A ZIP backup is small - typically a few MB, because the log databases are deliberately excluded (see 40.17.7). Even a generous count therefore does not consume any noticeable disk space.
40.17.6 Last Backup ¶
Above the directory field the program shows the date of the last successful backup (e.g. “Last backup: 10.05.2026 14:32”). This way you can see at a glance whether the backup mechanism is actually running. On a fresh installation or after a backup directory change, “No backup yet” is shown initially - once the first backup has run, the value is updated the next time the program options are opened.
40.17.7 Contents of a Backup ¶
A backup ZIP contains all files from the AppData directory relevant for program operation:
Options.json - program optionsProfiles.json - all profilesEmailAccounts.json - account definitions (passwords encrypted)DatabaseConnections.json - database connectionsPrinters.json - printer definitionsFilterlists.json, LookupTables.json, MappingTables.json - lists and tables- Various status files
Deliberately excluded are:
- the log databases due to their size.
A backup is portable and can be restored on another PC or under another Windows user - see Chapter 60.
40.17.8 Restore ¶
A backup is restored via File - Restore application data… (see Chapter 60.4). Since the log databases are not part of the backup due to their size, a restore always triggers a re-indexing of the emails in the monitored folders. This protects against double processing of emails that arrived between the time of the backup and the restore.
40.17.9 Use Case ¶
Backups every 4 hours + after changes
Directory: D:\AEP-Backups. Interval: 4 hours. Back up after profile changes: on. Maximum: 50. This produces a backup every 4 hours plus one after each manual change - after 200 hours (approx. 8 days) of continuous operation the rotation begins.
40.17.10 Tip ¶
- NEVER choose a subfolder of the AEP program directory or AppData as the directory - in a system restore the backups would be gone with it