When you damage the backup files, typically all bets are off as to whether the backup is recoverable. There is no redundant storage of the data. Best practice is to have multiple backups, done differently.
Software can also have bugs. This is a different issue than hurting the files that contain the backup…
Duplicati.CommandLine.RecoveryTool.exe
This tool can be used in very specific situations, where you have to restore data from a corrupted backup.
would have been an option if we couldn’t get back to normal use, and history was critical to maintain. Basically keep the damaged backup for special recovery of old stuff, while starting fresh to keep new.
Hopefully we won’t need to do that here, but we don’t yet know what success we will be able to have.
I doubt it. If you see any source file names, what table are they in? Destination names aren’t sensitive.
EDIT:
The File view in your original database is full of source paths. In bug report, they wind up looking like:
