That makes sense because the filelist isn’t uploaded until the backup is done, as it contains the results of the backup. The file list information was in the database, except that got deleted in step 6, leaving no clue about what files got processed so far. What you might have is some of their blocks and dblock index files.
How the backup process works gets into this more, and B2 web UI can show what you actually uploaded.
Although B2 has free uploads so you might prefer taking advantage of that, what I noticed is that Recreate appears able to put dblock and dindex information into the database, even if it’s seemingly not in any files. What this would achieve is upload avoidance of the same information when the same files are backed up again in another backup try. Duplicati won’t upload blocks of data that it records as already on the remote.
The trick is to trick Recreate into pulling the dblock and dindex info in (it may need complete download) by manual upload of a dummy dlist taken from some other backup done specifically to make this starter dlist. You don’t care that Recreate doesn’t like it, provided it runs, and then lets you continue backup as desired.
If you like, I can try to test this out a little more and supply steps, but B2 download charges might kick in…
Things like pause, cancel, and stop have some issues. I don’t recall all the specifics, but a repair effort is:
Fix pausing and stopping after upload #3712
It does simplify things a bit because it gives you the option of deleting the remote files. On the other hand it complicates things because you have to take it up on its offer to export the job, then import it back in again. Probably the best path though unless you’re in the ill-advised habit of deleting the backup parts by hand.
The easy way to avoid no-filelists-at-all is to start with a small backup, perhaps doing most important files. After getting at least one backup up, you won’t be subject to Recreate complaining it can’t find any filelists.