Well, it looks like the only ‘supported’ path at this time is to use a Container.
Where do I find the current DB and Config file that defines what the current Music, Backup and DB location are?
I am comfortable going fishing around the native QNAP file system in bash. The DB location the QNAP UI claims seems to be the entire Roon folder, where the app and everything resides not just a DB.
Do I point my Docker Compose here?
cd /share/CACHEDEV2_DATA/Roon/Roon
[/share/CACHEDEV2_DATA/Roon/Roon] # ls
RoonOnNAS/ ROONSERVER_QNAP_LOG.txt
Looking at the Docker compose file, it seems to just create volumes that will be mounted into the container. How does Roon then determine which is which?
I have to say Roon handled this very poorly, did they even test on QNAP? Why does it even let us upgrade to a version that would brick?
Change to the location where the old App Roon Database was installed, you will see a number of files in it but you only need the folder RAATSserver RoonGoer and RoonServer. In my case it was /share/Roon/Roon/RoonOnNas
Tar these up to move to the archive to the new Container location [/share/Roon/Roon/RoonOnNAS] # ls bin/ RAATServer/ RoonGoer/ RoonOnNAS.log.txt RoonServer/ [/share/Roon/Roon/RoonOnNAS] # tar cf db.tar RAATServer/ RoonGoer/ RoonServer/ [/share/Roon/Roon/RoonOnNAS] # mv db.tar /share/Container/roon/database/ [/share/Roon/Roon/RoonOnNAS] # cd /share/Container/roon/database/
Now we need to extract these into the new location after stashing the current files just in case.
If you are lucky and have a recent backup, you can do the above by restoring a backup, but as Roon released this without warning, it would brick. I did not have anything that recent. (about a month old).
In my case, I also had to make two additional changes in the Roon UI.
I had to update my Music Path. In my old Roon I was mounting it from an NFS share. I just had to browse to the Music path defined in the Container.
My Linn DSMs (great Audiophile streamers BTW) were not getting detected. There is a setting in Roon to select what subnet they are on. This was using the private container subnet by default. It needed to be changed to the host network 192.168.1.0 in my case not the 10. default.
Finally, we can clean up by deleting the old App and the old App folders.
It’s easy to say, but really , you should always have a regular backup rotation setup in Roon. It’s very easy with the built in tool. Setup once and leave it.
It’s not luck if you have a backup available. I have mine setup for every 3 days and keep 4 versions.
I guess quite many QNAP users have that same need, usage-scenario - and like myself I also intend to use the new version on a container and use old DB & config. Do you know is there a guide or tutorial from Roon or someone else available somewhere? @Suedkiez might know
Roon Labs have provided manual database transplant instructions in specific support cases where people had to move their QNAP Roon to Docker and (foolishly) had no backup although they put great value on their database. However, as far as I can tell, they might not want this in the documentation because it’s dicey and having a backup is far better.
One of these cases is in the below link, if you search for recent posts by Vadim and with QNAP in the text, you should find a few more.
I wasn’t referring to you. In the other cases, people had not even tried to set up backups (despite Roon‘s constant nagging) and then got very upset when they lost access. That’s just asking for trouble and could have happened at any time.
