With release 880, Roon announced improved database integrity checking, so that it is supposed to be less likely to keep corrupted database backups.
Unfortunately, this is just less likely, since I‘m currently having an open support thread, where database corruption is the claimed source of my intermittent troubles and
I‘m able to restore an allegedly corrupted database without warnings,
I‘m able to back up an allegedly corrupted database.
So, seemingly no real safeguard, unfortunately.
My hope is, that support can improve database backup integrity for the community by investigating my case.
You are aware i’m sure, but i have been adviced by the Roon crew previously that a DB restore to a different Server is unsupported and could cause discrepancies. (Same serial etc)
Maybe you are not actually licensing the Test-PC and just making sure the restore goes well, but i figured it would be worth mentioning.
This isn’t a correct interpretation. Restoring a backup to another computer is perfectly fine. The restored backup will retain the old Roon server name, but this can be changed in settings. It’s also assigned to the same Roon account, which cannot be changed.
For instance, I have my core on a NUC, but also keep a copy of Roon Server on my laptop (inactive), and use NUC backups to refresh this. It is my “plan B” for running Roon if my NUC fails.
What you refer to, is most likely a comment relating to Apple Time Machine. This should not be used to restore Roon to another computer since this will inherit hardware information associated with the originating machine.
When it comes to MacOS and moving a Roon installation via a migration tool, that will cause issues. Also, Roon cannot restore backups between servers’ linked to different accounts; but, if certainly can restore backups to different Roon servers on the same account.