Welcome to the forum @Django43
Can you explain “ran out” any further?
You tried the direct restore twice the same way, and got different results? Or was there a run difference?
I don’t know how hard it is to trace what’s where, but does that include the drive Duplicati’s DB was on?
If the Recreate isn’t working well for some reason (and a few reasons might be below), is old DB there?
If you have the backup files, it should be possible to recreate the DB. Ordinarily a direct restore builds a “partial temporary” database, so is faster, if you asked for all the files, I’m not sure if that would benefit…
Do you recall how far right progress bar moved? The 70% - 100% range (especially 90% - 100%) range mean Duplicati is doing more than usual. You could also watch About → Show log → Live → Verbose.
For larger backups, increasing blocksize helps performance. The default 100 KB is a whole lot of blocks. Unfortunately, this can’t be changed on an existing backup, so your DB Recreate might run more slowly.
or ramdisk would also help. There are also some tools that don’t use an SQLite DB, but a flat file instead.
Duplicati.CommandLine.RecoveryTool.exe is that way. You can use URL from Export As Command-line.
Or a regular Recreate might work, and life will be good. You have some things to watch while waiting too.
If it winds up giving an error, look around well, e.g. <job> → Show log and About → Show log → Stored.