So after having flagging that the B880 Update process caused the sudden and total halt of my Roon system, reported here Update to Roon 1.8 Build 880 corrupts my Roon Core database
I am now rebuilding the Roon Core database in B882 from fresh, as advised by Roon, who have no solution to recover, rebuild or do anything with a backup from B831 or earlier that has corruption.
There is no way of telling where the corruption in the database began, whether this year, last year, the year before, …… or whether was pre the 1.8, 1.7, 1.6, 1.5, 1.4, 1.3, 1.2 or 1.1 releases. The database I lost dated back to 1.0 Build 30, so impossible to maintain backups to return to any point during that timeframe.
Basically if you are able to recover from a past pre-B880 Backup, it is totally hit or miss on finding one that may work, given there is no indication of when the corruption occurred and when it entered in Roon’s unchecked Backup processes.
I can report that, on the same existing hardware platform, B882 is all working fine so far.
All Albums imported, Roon has identified what it can and the full audio analysis is complete. That only took 4-days. I now have hundreds of albums to re-identify again and my album count is all wrong, so a complete album-by-album analysis of the 7,000 albums in my library is required. Good job it is only 7,000 to do and not any bigger.
Checking the details of the RoonServer folder within Roon and comparing against a non-working corrupted one, they are virtually the same size and include the same number of files, so how the database is being used in terms of structure & operation seems to be very much the same.
Given that database integrity testing has only been introduced in B880, I would strongly recommend all users to rebuild a fresh database, after making exports or just manual records of any personal or individualised details such as Tags, Playlists, system settings etc.
Once you rebuild and recovered your library, ensure you make a fresh clean backup, as this only now includes integrity testing and have a rolling strategy going forward in case your new database gets corrupt and a restore is needed. Then you might as well purge all pre B880 backups, as they are essentially useless and can’t be used.