Migration failure from NAS to Windows 10, version 1272

[Tigo]

Roon Core Machine

Synology DS1821+, AMD Ryzen V1500B, 32GB RAM

Migrating to
Surface Pro 7, i-7 Intel 2.5Ghz with 16GB RAM

Networking Gear & Setup Details

Connected Audio Devices

Number of Tracks in Library

Approx. 34K tracks.

Description of Issue

• Successfully backed up the database on the NAS.
• Stopped the Roon Service on the NAS
• Installed the Roon server on the Surface Pro, and it’s running fine.
• Loaded up the Roon Client on my Mac and proceeded with restoring the database onto the Surface Pro Core Server.
• Message received indicating Restore successful, and to relaunch the Application.
• After Relaunching the App, at first it shows that there’s no Core. Wait a couple of minutes and it prompts to have found the Core Server.
• Selecting it - I get the Login / sign up / restore Window again.

Attempt 2. On the Surface Pro, I have uninstalled the server, and just installed the Windows Roon Client - opting to set it up as Core, and similarly successfully restored the core database. Then, upon relaunching the Application. The same thing happens - I am prompted to login / sign up / restore again.

What am I doing wrong? Or is there a problem with the database restore in 1272?

[Graeme_Finlayson (The Mad Scientist)]

Did you unauthorise Roon on the previous core? You won’t be able to set up a new core if the account is still associated with the old core.

[Tigo]

So that was the mistake. An absent step. After restoring the database, and the application starting - when being prompted to login - I should have just logged in. After logging in, to deauthorize the previous Core. The application will then load the music library and all settings. Afterwards, it was simply to amend the library folder to the new path.

Everything is now perfectly fine again with everything working.

Many thanks for your reply. I think the KB about migrating should be updated with a note to advise the user to login - to deauthorize / authorize the new core.