Has anyone managed to restore a very large Roon database? (~33GB)

I’ve never had it work. I’m moving to a new Roon Server machine, and I’d rather not lose everything (playlists, hearts, ratings, etc.)

If keeping the old DB isn’t possible, I’ve figured out workarounds for the other stuff, but they’re a PITA because Roon doesn’t export M3U files that point at the Library.

It’s very easy to use Roon to export files that can be used to build .m3u playlists. An export of a set of tracks in an Excel file format has everything you need in column M. You just need to remove the initial part of the path (e.g., /var/packages/RoonServer/target/roonmnt/) using search and replace in a text editor to make things into relative paths.

Roon never did fix this.

There’s a cap to the amount of tracks at any given time during an export, otherwise the process fails. IIRC it’s around ~20K tracks.

Admittedly it’s been over a year since I last did a huge export, so YMMV.

Do you have an idea at what point/why it fails?
What has Roon Support got to say about it?

I should clarify. I mean a track list in Excel format. There is no limit for that.

1 Like

And you did write that, I didn’t read it correctly :man_facepalming:

You’re being too nice to me.

Roon support had me upload my DB April 2025, and then they closed the support request with no comment or solution: Roon locks up overnight and fails to load backups (ref#4EU4DS)

There was an earlier Support interaction, with no results. Back in 2021, I think, but I can’t find it now.

1 Like

Yes. I said I had workarounds, but they are a PITA and take hours. That’s not cool at all.

@daniel @connor @benjamin @noris @Jeff_P

Please can the above mentioned support thread be reopened and investigated for a better response for @Andrew_Webb

Your customer focused commitment is appreciated :folded_hands::innocent:

1 Like

I can reopen* the ticket for you, and give support a nudge.

For future reference, if a support thread auto closes, flag the last post as “something else”, and the moderators will assist.


*Done

2 Likes

My database is 64GB, and I just did a restore from a backup yesterday. I am on debian (32GB RAM, CPU I5 10th gen, app on internal NVMe/SSD) using the latest 2.64/build 1646. It took a while but it works.

Hope you’ll get this sorted. I would analyze with roon support what is wrong in your case. On the new server, just start from scratch. You don’t have so many albums IMO.

Thank you, and thanks for the tip.

1 Like

I will start from scratch on the new server if a restore fails. First I have to get all my playlists out and into a useful format. i also have a bunch of mixed file/qobuz playlists that I have to figure out (I have a plan).

You must have an enormous library. Judging from your DB, you’ve got twice as many albums as I do. That must be what, 16TB of FLAC?

It’s more. And they are all FLACs and DSFs. I deleted all mp3 long time ago. But at some point, I need to start deleting all the duplicates and most of the vinyls. Most of them are useless, they have just a sentimental value for me.

Size of my database is too big anyway. Audio analysis is in charge for the biggest part. Probably I will need to start from scratch, without any audio analysis as I don’t use any DSP. I even don’t use volume leveling, which might be a good idea though.

At the beginning, when I start to scani my library without audio analysis, the database was under 10 GB. It was much smaller, anyway. And I said: hm, how small it is. what if I press this button to make an audio analyze for everything? I have enough resources. OMG! It took days or weeks, whatever… Anyway a lot.

Bottom line, whatever I’ll decide, it would be easy to revert back to what I have right now. A restore from backup worked even for a 64GB database. And the backup for the library without audio analysis will be in a different location, so I can switch easily from one type to another, if I wish.

1 Like

I’m sorry to hear this is still a problem but also encouraging that @Chris_B has got it working. I have various threads on here, over the years, trying to get to a solution that works. I never managed it. From memory, my Roon install back up works but I could never get it to restore and function afterwards. My library is ~70GB too.

I gave up using the built in backup. @Piero_Olmeda very kindly wrote a script and built a scheduled backup into audiolinux. Now, every day at 3am, audiolinux shuts down Roon, the library is backed up onto my NAS box and then restarted. I then prune the files down every now and then. This is a straight copy of all the library files.

It’s great that the ticket is being re-opened and we might get some traction on this - one can never have too many backups :slight_smile:

1 Like