Deletion Fails - "Database file does not exist"

I’m trying to manually delete a “duplicate” backup in the hopes of fixing my problems from the DST bug. I ran

Duplicati.CommandLine.exe delete file://H:\<backupTargetDirectory>\ --dry-run --version=167 --passphrase=""

and the response given is

Database file does not exist: C:\Users\<me>\AppData\Local\Duplicati\AHPYZOVKMF.sqlite

I manually confirmed that sqlite database file does not exist. At this point I’m not sure if it’s looking for the wrong sqlite file or if I’m missing a file I ought to have. I’ve run recreate and repair on the backup in question, so I assume all the db files it needs exist locally, but I’m not sure how to verify that.

Has anyone come across this before?

Also: I got the version number from the Backup > ‘Restore Files’ > ‘Restore from’ dropdown menu’s entry for the date/time I want to get rid of. Please let me know if that’s not the correct way to determine the version number for the set I want to delete.

OS: Windows 7 SP1
Duplicati -
Backup source is local HDD
Backup target is a network drive, no encryption (it’s just a test to make sure I understand the settings)

“List of backup timestamps contains duplicates” due to DST change describes the DST failure, why deleting versions is seemingly impossible without source edits, and a possible workaround of database editing which hasn’t yet been proven (maybe you’ll be the first?). Regarding your current message though, you might just need to go over to job Database option to check “Local database path” so the command knows where to go using your addition of –dbpath. I’m not sure how Duplicati generated what you saw, but just give it the path…

Two easy methods that also pick up other parameters you might want (but didn’t give) are the Commandline option of the job, and the job Export --> As Command-line. Either way, you get to turn a backup into a delete then possibly run into the problem described in the link above (assuming yours has the symptom those had).