Thanks for the screenshot, @Carlos_Olmedo , we’ve forwarded it to the the team to look into this.
Hi, guys. Any news? Were you able to reproduce the problem?
Hey @Carlos_Olmedo,
There has not been any new information to share from our development team yet - the investigation is still ongoing.
My apologies if this has been glazed over, but have you temporarily tested any of your backups on a different machine? If you have any other computers or machines available to run Roon Server, it may be worth giving it a try - if anything, to allow you access to your local library even if only temporarily. 
I tried that (running off some other computer) and the result was the same: server does not connect after restoring backup. So… I guess I’ll wait. Very frustrating, to be honest.
Hello @Carlos_Olmedo,
In the meantime, our R&D team is actively working on this issue. However, we do have a workaround that has helped other users in similar situations.
The root cause appears to be a mismatch in the date format used on your PC. For example, when the backup was created, your system might have used the format 01/01/2025, but when trying to restore it, the format may have changed to 01.01.2025 or 01,01,2025.
To resolve this, please try switching your system’s date format back to the one used at the time of the backup, then attempt the restore again.
Let us know if that helps or if you continue to experience issues.
Thank you, I will try that. To be clear: we are talking about date format from the BIOS or at Windows level?
Hello @Carlos_Olmedo,
We are speaking about the operating system date format.
Great. Will try.
Hello @Carlos_Olmedo,
We are waiting for future updates from your side.
I’ve tried with the three date format options I have available, none of them worked.
I still don’t know if you were able to reproduce the problem or not.
Anyway, guys. I’ve decided not to renew on October so all this discussion will be academic. Would be good to know what happened, thou; I will hardly consider come back to Roon at the risk to losing all of my collection at any time.
Hi @Carlos_Olmedo,
Thanks for giving that a try, and sorry it didn’t solve the issue!
If you’re able to, it might be worth testing one more thing: try saving a second copy of the backup from your previous server using the same date format, and restoring it to your current setup.
That said, the good news is that our team has been able to reproduce the problem, and we’ve opened a development ticket to investigate and release a fix. We’ll keep you updated as soon as we have more to share.
Hi @Carlos_Olmedo,
We understand. Sorry to hear that Roon doesn’t meet your needs. We’ll go ahead and close this thread now.
Hello @Carlos_Olmedo ,
We wanted to reach out to you and let you know that the issue discussed in this thread is undergoing a fix from our dev team, and the fix is scheduled for our next Roon release. I realize this thread is closed, but if you’d like to give Roon another try after the release, please feel free to do so. Should you still have the same issue with the new release, please open a new support ticket to let us know. Thank you!