@noris -
Thanks, but QA’s response completely misses the point.
Roon’s backup told me the backup was successful when it wasn’t or it subsequently couldn’t be found and that’s the real problem here.
So we have a trifecta of Backup problems -
- Roon Backup will blithely backup a corrupted library.
- Roon Backup will say that it has successfully performed a backup when, in fact, it can’t find the backup it supposedly just successfully performed.
- The only way to backup Roon’s library is thru Roon’s Backup, i.e. one can’t use a different software backup program and be assured of a successful restore.
Couple these problems with the fragility of Roon’s database as evidenced by the recent increase in user’s encountering a corrupted library and there is a real festering problem.
I can see by QA’s response to this problem and the original response to the fact that Roon will back up a corrupted database, that there is little interest in addressing these errors.
The first time someone who has invested much time in curating their library runs into problems with a corrupted library that can’t be restored, there will be so much gnashing of teeth that the blow backs about increasing the lifetime subscription rate or the change to the way Roon handles un-certified devices will seem like so many quaint memories.
This problem is not resolved.
As we discussed in my previous PM to you, I have only been waiting to hear that QA has all the information they need before I delete and recreate folder.