Migration of Roon server core

Hi,

I am currently using roon trial and I do like it so far… So I am going to continue to use it (and pay).

However I have been doing testing with my computer and that is not the way to go with Roon. As Roon is “server softer” it needs to be alway available and on… I need to sometimes to shutdown my computer and take it with me.

Therefore I plan to get small “server” and install Debian stable to it.
As far I have understood correct Roon server core runs nicely with it on headless.

Question to migration… If I just install new roon core and then restore backup from Roon backup system will it have all as it have been in my computer?
You know, setting, liked song, play statistics, library info and so on?

If there is good guide how to migrate server core to other device I would like to know if someone is so nice and could link it.

Yes, the Linux binary is headless. The installation is straightforward, and all you need to do when first connecting is select restore from backup.

This will inherit the name of the server currently used, so go to settings → general to rename.

Since this is a supported config, I’ve moved your post feom Tinkering.

1 Like

Thanks that is great to hear!

1 Like

Read this thread for suggestions on low cost Roon servers MOCK Success Report - GMKtec Mini PC N97 - #53 by Johnny_Ooooops

2 Likes

yes, you just need to restore the backup. the one subtlety is that after restore, if the restored path to your file location isn’t the same on the new computer or isn’t valid (for whatever reason), you need to go to settings / storage and then click on the three dots next to the storage location and edit it. If you add a new location you’ll be re-importing all your library again, and losing play counts etc etc.

Good luck!

PS, those GMKtec boxes are cheap and great. I’m pro installing ROCK/MOCK on them vs. linux, but everyone here is different!

2 Likes

Ok thanks for instructions.

Ok than is not nice. It is bad that statistics are done based on file location and not metadata of file.
Like using ISRC code. Technically it would not be even hard to build DB of played songs and those count what could be migrated over.

Well at least I don’t care what file I played… I am more interested what songs I have listen.

I am pro Linux :wink:
I actually run my home recording studio fully on Linux… So that feels natural to me and I love stable releases I’d Debian when I want my systems be online 24/7 and always running smoothly. :blush:

GMKtec boxes looks great tough!
I am considering those or I actually could get locally here used mini PC cheap and maybe with better specs.

I have been running my Roon Server on 3 different Mac’s before going down the Linux route. I’ve used LMDE 6 for half a year on a Lenovo Ideapad. Only updated Linux every few weeks and then gave the system a reboot.

Since yesterday I am now running ROCK on a brand new little computer. The same GMKtec one as listed earlier in this thread.

It is running great so far.

I didn’t use a backup as I don’t only have a handful of local playlists. The Qobuz ones are automatically retrieved.

Roon itself keeps track of your listening habits. So daily mixes remain the same.

Okay… Does this mean that server itself do not know anything of listening habits of user?
I am thinking if I have Roon on iPad, Win PC, Android phone… Those all haves different data?

I see I can control playback and playing on all… But that OS most likely as those contact server and that handles audio stream.

Your Roon Server handles everything. Your phone, iPad and PC just use controlling software. They don’t have separate data.

I’m pretty sure that Roon stores your habits in its cloud. And that your server just retrieves them. Started with a clean slate basically. And already Roon’s offered daily mixes and recommendations match my listening habits.

1 Like

Right okay. Then I misunderstood. Thanks for clarifying. :blush:

I’m pretty sure this isn’t true. Now here I am out over my skis, but I’m fairly sure I recall that this is part of what Roon backup contains.

No, the core (the Roon server as you put it, but it’s easier here if you call it the core so people know what you’re talking about since a core can run in so many different settings) has all this data.

Again, I’m really a guy here - there’s folks who know far far more than I do so don’t take this as absolute truth - but I think that actually knowing at the song not the recording level is really hard. Because there are different recordings, different pressings different masters different remixes and different releases (which someone wants to consider the same and someone else doesn’t based on context). @SandsOfArrakis you may be doing a lot of streaming listening, which makes it different from someone who also has lots of local media.

So I’m not positive exactly what is in the backup - but I do know if you don’t repoint the existing file location you have to at a minimum do all your audio analysis again, manually identify any albums you previously identified, etc. there may be more stuff. Anyways, do that easy step.

1 Like

I’m not sure to be honest about audio analysis. I’ve moved my USB hard drive over from my old Server to my new Rock box. And my local files were all analyzed as far as I can tell.

This is incorrect. Roon stores something like a hash of the album/track, so you can change storage locations without loosing this data.

The important thing is to preserve file modification times when copying and editing outside of Roon. You can also set IMPORTDATE in metadata; I run a recursive script with metaflac to update this on my collection

1 Like

Depending on how you refer to your USB drive in settings / storage, you may not have needed to update the file location. I’m saying that I and others have definitely run afoul of this before, not that you necessarily will.

Looks like I haven’t cause Roon started importing right after booting up.

When I moved Roon server from a NUC with USB attached storage, to a new server with local storage, after copying my media across to entirley different storage location, Roon found my music and was updated within minutes. I’ve been doing this for years without issue.

As I said, you will only run into difficulty if you modify the content of files in some way. Copy will create a new file with new creation date, but file modification date should be unaffected. Likewise, moving alters neither.

Adding the IMPORTDATE tag is a safeguard as this is preserved even after, for example, reencoding a track. In addition, adding MusicBrainz IDs will preserve file references.

1 Like