Thanks for that update. Situation is clearer now. You’ll have to recreate the local database.
meaning:
You didn’t save Export and didn’t save any database, but you can manually add job as best you can.
After that, click job on home page, click Database, look at Local database path
to see where it is.
Wherever Arch put them is what you could save if you want to avoid having to recreate backup data.
After saving, don’t run Duplicati until you’re back, so destination and its database will remain in sync.
Push buttons.
If you’re doing this from scratch, only the Repair button would be enabled (blue). If you’ve tried some
things that didn’t work, then there might be a wrong database, so Recreate (delete and repair)
.
If backup data is missing, Duplicati will have to download dblock files, so if you want to reduce costs
(which will be small dlist and dindex files, and maybe large dblock files), you can create or edit job to
point to the local folder of your full B2 download. You would make database and move job back to B2.
If you already have a B2 job, clear the B2 Application ID and B2 Application Key before changing to a
Local folder or drive
, as those options don’t apply. If you leave them, it’s just a warning though.