Hi @anon3351567,
Sure no problem. This article will show you how to perform a migration https://help.roonlabs.com/portal/en/kb/articles/migration. Please let us know if you run into any trouble!
I tested backup retrieval using a Windows PC. The recovered backup was missing a lot of covers that I had added in addition to some album groupings. Is this normal? I would have thought it would have been a perfect match. I connected the Core sofware on my PC to my music library and Roon data via mapped network drives on my NAS. Better recommendation? I want to ensure I can pull a proper backup, before I purchase a Nucleus.
Hi @anon3351567,
Sorry you’ve run into this issue. Missing cover art isn’t expected behavior when restoring a backup, so we’d like to dig a little deeper. Are you using artwork provided by Roon, or artwork embedded in your local files? Also, have you noticed any problems playing music from your local library since the restore?
Let us know and we’ll be happy to investigate further.
The missing artwork is all the custom additions I made. I’m not sure where that artwork “lives” when I drop it into an albums metadata. Performance is somewhat slow, but the PC I’m temporarily using is dated, hence the planned move to a Nucleus. I have noticed that the “spinning wheel” indicating file analysis hasn’t stopped spinning despit all the music having been added.
Hi @anon3351567,
I activated diagnostics on your account so we can investigate further. When you get a chance, please turn on your Roon Server for a few minutes. This should allow us to see what analysis the server is still working on. Let us know once it’s been powered on and we’ll take it from there.
Rebooted the Core. Analysis is complete. Only remaining issue is missing artwork that was added manually.
Hello @anon3351567,
Could you please clarify how your album covers were added — were they embedded in the file metadata, or manually added through Roon’s album edit function?
This will help us understand where the issue may lie.
The latter - album edit function.
Hi @anon3351567,
Can you try either deleting and reimporting one of the albums or adding a new album to your local files? I’d like to see if that triggers the album image to appear. The results of that test will help us better understand where the issue might be.
I just ordered a Nucleus and will retry the process on it. Attached to my NAS drive is an SSD drive that stores my Roon Data and Roon Backups. I had planned to attach it to the Nucleus. During what part of the migration process should I do this? Or should I first restore Roon using the existing infrastructure and move the SSD afterwards? Will all of this information now live on the Nucleus itself? I’d still want to duplicate the data on a secondary drive for safety purposes.
Hi @anon3351567,
Have you checked out the article about migrating to a Nucleus?
https://help.roonlabs.com/portal/en/kb/articles/nucleus-migration-guide
The section on storage should help clarify when to attach your SSD during the process. If anything in the article isn’t clear or if you run into any issues, don’t hesitate to reach out. We’re happy to help!
1 Like
Restoring a backup using a new Nucleus One did not bring back all of the images I had imported into Roon. And several box sets were broken out into single discs. Metadata was changed for many albums. I.E. the restore does not represent the fully edited status of my library.
I have attached the SSD holding my RoonData directly to the Nucleus. I’d like to migrate all my RoonData onto the Nucleus and use the SSD as a secondary backup location. But I don’t want to proceed with this until the metadata is corrected.
Possible, probable answer to my own question. I was using a different account with this database. Are my changes associated with that account?
Secondary question still remains. Can I use the Nucleus to store my RoonData/Roon Backups instead of my outboard SSD? Is it as simple as installing the SSD inside the Nucleus?
Hi @anon3351567 ,
No, you cannot store Roon backups inside the internal SSD, as this would cause a scanning loop, where Roon would store the backup, and then scan the backup itself for media. Our suggestion is to store backups on an attached USB drive, or a network location.
By RoonData, is this referring to your media files? I’ve activated diagnostics for your Nucleus and looking over the diagnostics, I do see quite a lot of network-related errors, and an error about mounting your NAS due to network conditions. Assuming that the RoonData you mentioned is the actual media files themselves, please just keep in mind that if Roon sees two copies of media files at the same time, it will mark the newest duplicate as a “new” file, and it would not have associated metadata edits. Could this kind of situation have happened on your end at any point during the migration process?
Okay, I’ll keep the current SSD setup (connected to USB port) for storing RoonData and Roon Backups.
I’ve had to turn my VPN on and off to accomplish accessing the NAS where my media files are stored. And I’ve made some changes to networked folders. I’ll reboot my network for any potential errors. But no, the Roon Server would never have seen duplicate files.
My album data and artwork does not reflect the many changes I made to all my media. Is this because I am using a new account? I still have access to my old account. Is there a way to migrate all of my old metadata over to my new account? All the correct information is present when I restored a backup and logged back into my old account.
Hi @anon3351567,
Yes, the issue you’re experiencing is very likely due to using a new Roon account without fully restoring the environment from your old account. Roon stores all your custom metadata, edits, artwork, playlists, tags, etc. in your Roon database, which is backed up when you use Roon’s built-in backup tools.
However, when you log in with a different Roon account and don’t properly restore the backup from your original account, Roon treats your music collection as brand new, it will re-scan your files and apply default metadata from its own cloud sources, not the edited data you carefully curated.
Since you still have access to your old account, you can migrate everything over by following these steps:
1. Restore the Backup Under Your Old Account
- On your Roon Server, log into your original account.
- Go to Settings > Backups > Find Backups, and restore the most recent backup you made that includes your edits.
- Confirm that all your album data, artwork, playlists, and tags look correct.
2. Switch to the New Account
- After verifying that everything looks right, go to Settings > General > Roon Account and log out.
- Then log in using your new Roon account.
- Roon will ask you to reauthorize the Server, go ahead and do that.
- Your database (with all edits and custom info) will be preserved. You may need to re-link streaming services and reconfigure some integrations, but the core metadata should remain intact.
Let me know if this helps! 
Excellent, I’m glad that there’s a solution! I’ll give it a try.
Unfortunately, this did not work. After signing out, I am asked to reconnect (“reauthorize”?) to my Nucleus. I do this and am taken to a browser page for login. I login with my new account, and it wants to run me through the process of setting up my library, etc. There’s no data at all showing at this point. Should I bypass and open up a backup at this point? Is this any different from restoring a backup before logging in to the new account?
Thank you for the additional clairty @anon3351567, and you have my apologies as I believe I have mis-spoken on my prior response.
The problem is that Roon’s database is cryptographically tied to the account that created it, meaning restoring a backup made under Account A while logged in with Account B won’t work, Roon will wipe the database and start fresh.
When you sign in with a new account, Roon will invalidate the restored database and start from scratch. That’s why you’re seeing a fresh setup screen after logging in with the new account the system wipes the old data to protect integrity.
To preserve your full database (edits, playlists, artwork, etc.), you’ll need to stay logged in under the same account that created the backup, unfortunately.
If you must move to a new account, there’s no supported way to transfer the database between accounts at this time.
You have my apologies for the confusion here.