Wrong work of long-term backups

[popovn]

Each time the backup saves files in the directories "yearly, monthly, weekly".
The old "today's" versions are being erased

To work better with the disk, the file must be created once. When the number of stored files exceeds the threshold and you need to delete the oldest one, then transfer it to the directories in turn "weekly-> monthly->yearly" if it meets their conditions.

The move operation is much less overhead for the file system than creating 4 files each time when starting a backup

The yearly, monthly, weekly config is also not saved.

[marvinweber]

Hi & thanks for your improvement suggestion.

You're right, the current long-term backup process is not optimal. This "caused" by the fact, that this started as a very simple plugin just creating copies of the database at every save and adding new features just on top of it.

As soon as I find the time, I'll refactor/rebuild the plugin and also consider the fact of the suboptimal backup/cleanup process.