Could you please give the exact message for below? I can’t find that exact one.
Was this the first sign of trouble, or is this where you are now after having tried various things?
Please give any history you recall on what the very first problem was before attempting any fix.
Do you by any chance have any separate log, or a copy of the database before you deleted it?
Are you coming back to an old backup after a long break, or was backup current but just broke?
You wrote “errors” in the plural. Is xys just a placeholder for various ones? How many are there?
Although I hope it’s not needed, an even better tool for worst case scenario doesn’t use such files:
Duplicati.CommandLine.RecoveryTool.exe
This tool can be used in very specific situations, where you have to restore data from a corrupted backup. The procedure for recovering from this scenario is covered in Disaster Recovery.
Please watch a live log at About → Show log → Verbose and post the top few lines at freeze point.
Ordinarily I think it goes through the dlist files, the dindex files, then (if still needed) the dblock files.
The dblock files are on the final 30% on progress bar, and the final 10% can take a very long time, depending on backup size, download rate, etc. Easiest evidence of non-freeze is probably live log.
What storage type is your destination, and can you easily examine and obtain its files, if need be?
If you can conveniently sort by date, what sorts of files (if any) are the newest? Any near fail date?
Generally a backup will upload 50 MB dblock files and much smaller dindex, with a dlist at the end.