Repair isn’t a backup, and it’s also not:
I was wondering if you did that, then I saw that you listed a bunch of things (including those), then the:
What happens? I only find the word “restore” in the first and last lines here. Need some details about it.
is going to need a longer look. There are a few mentions of it in the forum. Most of them are in this topic.
EDIT 1:
I’m losing the chronology, but some history here is:
Just to be 100% sure, I retested with the exactly same command line with the canary version and it fails saying:
2024-01-15 08.44.53 +02 - [Warning-Duplicati.Library.Main.Operation.RecreateDatabaseHandler-UpdatingTables]: Unexpected changes caused by block duplicati-b0366966e93db4129b6ce9f5798fbe9d2.dblock.zip.aes
This is good, really good.
That reaction puzzles me, but I don’t have all the context. Regardless, available developers have changed. Probably I’ll ask if the current ones can dig in a little further. I might try to as well, but it won’t likely be fast…
EDIT 2:
Experiment/rebuildfaster
duplicati:master
← duplicati:experiment/rebuildfaster
was probably the change (this developer has left, unfortunately), and the discussion behind it might be at
Running 2.0.7.1_beta_2023-05-25 Had an issue with the machine I run Duplicati on I have a backup of the Backup Config from when I set up the job,and the files to date,but when importing the job and connecting it to the folder it gives an Out of Sync warning and repairing doesn’t want to proceed Recreating the database is running for days now with no end in sight on 2 different test machines
I’m hoping some of the devs can help to reconstruct what was going on here, and what current situation is.