What is the difference to the database files for duplicati?
DZEUKKAGTZ.sqlite (the database file used in the “live” backup?)
DZEUKKAGTZ.backup (a backup of the file or?)
DZEUKKAGTZ.backup-1 (a backup of the backup or?)
DZEUKKAGTZ.sqlite-journal (a what?)
backup 20190110120730.sqlite (one more backup of what??)
I know DZEUKKAGTZ.sqlite is used for the backup, but what about all the “.backup” files and so on, are they save to move to save some space, because I have 131GB backup files, and 65GB “live” sqlite files, so I will like to move them to a save place.
The file DZEUKKAGTZ.sqlite is the main database file, and used for active backups. While running, the database needs to update, and to do this in a way that is safe from crashes (i.e. the database can still be read if the machine crashes during an update) it uses a journal, in the file DZEUKKAGTZ.sqlite-journal.
I do not recall any files being made with a .backup extensions, and certainly not the .backup-1.
It should just take the database name and add a timestamp:
Which should give something like DZEUKKAGTZ 20190110120730.sqlite as the file name.
The other names sound more like something Finder or Explorer would make.
on my systems running 18.104.22.168, the automatic backups are called “backup timestamp.sqlite” - the original filename is nowhere in the backup filename. Was that fixed after 22.214.171.124 to work as you describe?
The posted source link is in master, so I think it still drops the original name (which is maybe not good). BackupFilenamePrefix in the code quote seems to be “backup”, resulting in the names you’re seeing.
Correct me if I’m wrong, but I’m thinking the whole “try for 10 times at 1.5 second increments” is because the original part of the database filename is NOT included in the backup. So when you first install a newer version, there are at least 2 databases (main and one backup set) that need to be backed up.
So if we fix the backup filename so that it includes the original database filename, we won’t need that kludge.