Hi @noris, and other members of Roon staff,
(I apologize in advance for my clumsiness, as English is not my first language).
I sincerely thank you for finally coming back to me.
However, I must admit that I was expecting a little more support from the Roon Q.A. Team. Since you have my library on your servers, is there no way for the staff to repair the code and fix the supposedly missing file?
In the last couple of years, I invested hundreds of hours into my library, tagging, organizing, correcting information and so on, because I was relying on the backup system when I purchased a lifelong licence. I understand that few others have lost their work due to backup inconsistencies; this is very likely to happen again unless we understand what went wrong. Roon users have a right to better understand how the backup system works, and how it fails.
So, if I may ask, there are a few things that remain unclear to me, and that I would like to investigate (if anyone could shed light on these matters, it would be greatly appreciated).
-
First, you mention that “Since this file is missing, this indicates that there was an issue with Roon creating the backup.” Does that mean that the corruption occurred at the moment of backup creation and not afterwards? If so, is there no way for Roon in a future update, to check the integrity of the backup and confirm that it was successful?
-
As for the other “environmental factors”, we can exclude hard drive failures because I used three different types in three different locations (internal and external HDD, and one SSD). There are all working perfectly well. If it was a power loss preventing the backup from completing itself, shouldn’t the next attempt be successful? Also, in my case, it can’t be a sync program issue because the backup I sent you was done directly by Roon without any other program interfering into Roon’s folders.
-
You write that “Sometimes, database corruption can be “latent”, meaning that part of the database is corrupted, but the database can still load and future backups preserve the current state of the Roon database. […] This is likely the case here — The backup was made after the latent corruption existed.” In that case I would very much like to understand what is latent corruption, what causes it, how to prevent it, how to check that the library is free of it.
-
Perhaps we could also ask other questions. I think I do things that a typical Roon user does not, I use Roon functions that appear to be still buggy, like tagging Classical Composers on the Composer’s page and not on the artist’s page (see: Classical composers tagging not working / dead links). Could this be the reason why a library gets corrupted? Are there any other know factors that can create latent corruption in a library?
From what I understand, latent corruption is an urgent matter for many users, and I hope that Roon will do something to improve the backup system in the next version.
Thank you for your time, and please let me know what you think. If I am to continue to use Roon and start a new library, I absolutely need to know how to prevent it from failing again in a year or two.
Thank you again for your time and help.