I'm trying to move my Roon Core from a Windows 10 computer to a server running UnRaid and I've followed the steps outlined in the Roon Knowledge Base under "Moving Roon to a new Server". This means that the latest version of Roon is installed on the Windows 10 computer and on the UnRaid server. I've copied all my local music files to the server and I've correctly added the storage location of the music under settings -> storage on the server version of Roon. I've just completed a full backup of Roon and that backup is located in folder on the server. I stopped the version of Roon running on the Windows 10 computer and started the version of Roon on the server. So far so good. In the Roon running on the server I've located the newly created backup under Settings -> Backups -> Find Backups and pressed "Restore". The backup restore runs until it reaches about 30% and then the "Backup Restore Failed" message appears. How do I fix this issue so that the version of Roon running on the UnRaid is fully restored? Thank you
Describe your network setup
The UnRaid server is connected to the network via Ethernet and is directly connected to one of the Ethernet ports on a Verizon CR1000A router.
I’ve also logged into both Tidal and Qobuz on the Roon Core running on the UnRaid server.
Does the same issue happen if you try to create a new manual backup to a different location (compared to where you usually have backups stored)? I’ve also activated diagnostics for your UniRaid server but it doesn’t appear online at the moment, when you have a chance let us know your results from the different directory backup test and we’ll check logs for clues, thanks!
Hi @Jazzfan_NJ,
Thank you for doing that test and letting us know the results. Looking at the backup failure in logs we see these traces.
01/13 10:47:59 Error: [Broker:Misc] [backup] failed to restore: getfile by hash, dirs: AttachedDir:/backup/RoonBackups/5878d1bb-d88c-ba70-a7f3-2f63d789e438/a2/65, file hash: a265f999ef1d17b13d086ca0d1e8515596d8747c5246f2ff82e5d245b5364374, status: Result[Status=NotFound]
01/13 10:47:59 Warn: [Broker:Misc] [broker/backups] restore first half failed on FileBrowser.Entry: / : /backup/RoonBackups: NotAvailable
This NotFound status has a few possible causes.
A permissions issue. Can you please make sure that Roon is allowed to access the backup location?
Storage space. Ensure that the device where the backup is being restored has enough free storage space. Also, check the integrity of the storage device.
File structure issue: Navigate to the backup location and verify that the folder structure and files exist as expected. Specifically, check if the file mentioned in the logs (a265f999ef1d17b13d086ca0d1e8515596d8747c5246f2ff82e5d245b5364374 ) is present in the /a2/65 directory.
Please let us know the result of checking these potential causes.
Yes Roon has permission to access the backup location.
There is plenty of storage space available on the drive within the UnRaid which will hold the Roon database, even for my very large library (over 900GB available on a 1TB nvme drive)
The file does not exist in the /a2/65 directory or in any other sub-directory of ```
5878d1bb-d88c-ba70-a7f3-2f63d789e438
So what’s next? Please let me know if and when you would like me to start Roon on the UnRaid server. At the moment is Roon is running on a Windows 10 PC.
Well I tried to restore using each of the 10 backups shown in the backup folder and they all failed. I never received any messages saying that the backups were not completed correctly, in other words, I was under the assumption that the backups would work properly and restore without any issues. I guess that I should never have assumed that to be the case.
To say that I am disappointed and extremely upset would a massive understatement. Ove the five years that I have been using Roon I have put in hundreds of hours grooming my music library - identifying albums, grouping, and merging albums etc. - and to think that all time is now lost is unfathomable. I really expect software that costs as much as Roon does to work as advertised. Hopefully Team Roon can find a way to compensate me for the failure of their product, perhaps a few years added to my current subscription. I await your response.
If I understand correctly, it sounds like the main issue is with the process of restoring one of your backups, not that the backups themselves are lost or corrupted—does that sound right? Based on what you’ve described so far, there’s no indication that all of your backups are affected, so I’m confident we can help figure out why the restore process isn’t working as expected!
As a simple test if you haven’t yet, safely stop all instances of Roon Server, and then give everything including your router a reboot.
To confirm, your backup location is different from where your local library lives, correct? What if you attempt a fresh backup to an external drive, and attempt to restore from the drive?
I’m confident we can get this sorted out, and have you back up and running with your usual Roon database soon.
Thank you for your response and for looking deeper into this issue.
Now I must offer Team Roon an apology.
The main reason that I was moving Roon Server, aka Roon Core, from my Windows 10 computer and onto a dedicated server was that the size of music library (over one million tracks) was causing Roon to behave rather erratically, with slow response times and frequent playback issues. There was just too much stress being put on the computer with Windows constant background processes and Roon’s demands on the CPU and the network.
Add in the fact that the computer was getting a little long in the tooth, as were the external USB hard drive where the music files are stored, and the need to get the server up and running as soon as possible became a top priority. I had just finished copying all the music files onto the server when one of the USB drives and shortly after that the CPU cooling system on the Windows computer failed, leaving me with a nonworking computer.
Which is a long winded way of saying that I decided to just start fresh and have Roon build a fresh database. At the moment Roon has scanned about 70% of the music files and is working great. All the playback issues are now gone and the response times are vastly improved. I still believe that the Qobuz/Tidal/Roon integration causes response time problems, particularly on Thursdays and Fridays, but that’s an issue for different support topic.
So while I’m willing to bare part of the blame for the backup and restore issues, I’m still upset that Roon never reported any issues when making the backups, as this would let me know that a backup restore would have issues.
One of the upshots of this exchange is that now Team Roon knows that there is at least one user with a very large library with Tidal and Qobuz subscriptions now running Roon via Docker on an UnRaid server. If you would like for me to keep you informed of how Roon is working on this new server just let me know.
