Added a new tool for offsite backup was the announcement. At least for this, more docs sound expected. Help text is often concise (try some). Manual can say more.
So there’s an example of plans for directions on how to use a tool in a certain way, which makes lots of sense when a tool might be inspired by a specific usage need.
It sounds like you encountered those
so I wouldn’t immediately blame sync, however at a higher level it would be a migration issue to a different storage. Migrating Duplicati to a new machine is covered in the manual. Maybe the new docs will cover storage migration too?
Generally it’s easy – just move all the files and change job Destination setting, however if you’ve been making new jobs, any new jobs will have no database describing expected Destination contents, so may be surprised to see the files.
If you’re not sure if your database is the last working one (although I’m unsure whether it was working all that well), check your job logs to see signs of history.
If it looks too empty, maybe it’s useless, so you use Database screen to run a Recreate (delete and repair), which maybe you already did, since you got warnings and errors talking about recreate problems. For the error, the error is probably a dindex file intending to index a non-existent (it should exist) dblock.
Sometimes dindex/dblock pairs break, due to either extra dindex or lost dblock. Recreate notices these. Normal operations don’t. I’d just delete that dindex file. You have a local copy anyway (that it uploaded from) in case it needs checking.
I’m guessing that the warnings are related to the error, as dindex implied dblock, possibly leading to an unsuccessful attempt to work around the lack of its blocks.
Regardless, next step is probably to remove that unhelpful dindex, and Recreate.