Add option to also backup current database file on save

[cgku]

Summary

The current option to 'Backup database file before saving' is not truly a backup, but appears to act as a restore point for the "as-was" state of the database before changes were saved. This is perfect if the recent changes need to be rolled back for some reason. However, if something happens to the current database, this backup copy will not have any of the changes just saved, so data loss is guaranteed. The current workaround is to manually make another copy after each database save, or use another tool to create additional copies.

Suggestion

Change the backup process to create and sustain at least two, but possibly more, backup files. The first would be an identical copy of the current database state. The other file(s) would be the previous X versions, where X is a user-configured setting.

Context

This removes the need for a manual copy, or external solution, to create an identical copy of the currently saved database.

[droidmonkey]

Technically, the "backup" created is a direct copy of a known working database. To make another copy of the current database doesn't really make sense based on what we are trying to protect against. The point of corruption is on writing, not when stored (unless you use a USB thumb drive, don't do that)

I do agree that if you are looking to store a copy backup to a different location, on save, then we don't have that capability.