Hey @Mikael_Ollars,
Thanks for the report!
We took a closer look at a fresh Roon Server diagnostic report, but unfortunately, it contains no bookmark, backup, or restore events in the recent block, no database corruption, and the schema stayed at version 8→8 across the 1462→1661 upgrade.
The files cover two separate periods, an older block from Oct 1–9 (build 1442/1462) and a recent block from May 19 and June 10–11. The June 10 sequence captures an in-place upgrade from build 1462 to the current 1661. Across that upgrade, every database opened cleanly with no schema change: the music database reports migration version = 8, current version = 8, the playlist database stayed at version 2, and the profile database at version 1. No corruption, no rebuild, no reset, no “fresh database” events anywhere in the set. A version-matched, clean open like that is the normal, healthy case, it means the upgrade did not migrate away or discard your existing data.
Critically, there is no backup-restore event at all. The only backup-related lines are routine startup messages, the backup subsystem initializing ([broker/backups] initializing), which happens on every launch. There is no “restore from backup” operation recorded on June 10/11, and none in the older October block either. So whatever restore you did “a few months back” predates everything captured here; these logs don’t reach it.
The most reliable recovery path is a backup from before the restore that you suspect caused this. If you have scheduled backups, look for one dated before that restore, restoring it would bring the bookmarks back (along with everything else from that point, so weigh what else you’d lose). If your only backups are post-restore, the bookmarks won’t be in them.
Since you mention you lean on focus and tags rather than bookmarks, and there are about 20 of them, manual recreation may end up being faster than hunting for an old backup, especially as several (“albums by artist X,” “samplers”) are quick to rebuild as focus presets you re-bookmark.
Sorry, I can’t provide deeper insight here, @Mikael_Ollars. Let me know if there’s anything else we might be able to help with. 