There might not be a rebuild of the backup itself to do, depending on whether a backup was attempted after Duplicati’s mysterious update issue. You can check OneDrive file dates, and the date on ICBYVMIOZA.sqlite.
Configuration information is almost entirely in Duplicati-server.sqlite, not in the backup (or its own database).
You can’t let it continue on OneDrive (unless Microsoft brings it back), but you could downgrade then try the upgrade again, or at least downgrade and see if you can get Duplicati to output config info, e.g. from Export.
Downgrading / reverting to a lower version talks about sqlite backups made before database version upgrade (which you get with 2.0.4.5), how to downgrade by identifying and restoring the backup databases (which also raises consistency issues with the destination, if backups have been run, unknown to the restored database).
If you decide to downgrade temporarily by doing something like moving your update folder elsewhere (see the above document for where the upgrade might be), then your now-older Duplicati should refuse to operate with newer database formats. You can use this to your advantage because I think it will stop an actual backup run, while letting you look at the job configuration (which is in Duplicati-server.sqlite normally, and maybe in one of the smaller sqlite files with the backup name – anything big is probably from a former backup job, not server).
Basically, the 85 MB file is probably the job database, and if backup 20190116063617.sqlite is a few hundred KB, it might be your former Duplicati-server.sqlite which you could try using as that (after renaming current), if you decide to try to downgrade, start Duplicati Server or Tray Icon, and note (or maybe even export) your job.
Looking into the current Duplicati-server.sqlite (if there is one) might shed light on what went wrong, but would need --unencrypted-database set on the Server or TrayIcon before DB Browser for SQLite or similar can look.