Query about removing old Roon files after Docker update (ref#PN0AEU)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Update to docker, can I remove old Roon files?

Tell us about your home network

· Unify system all works fine

2

Hey @Peter_Schut,

Thanks for writing in, and excellent question! Yes, generally it’s safe to remove the old Roon Server files once you’ve confirmed your Docker-based Roon Server is running correctly and your library/settings have migrated over. Here’s what to keep in mind:

Before deleting anything, verify:

  • Your Docker instance is running and you can connect to it with Roon remotes
  • Your library looks correct (albums, playlists, edits, play history)
  • Your audio zones/settings are intact
What's safe to delete:
  • The old Roon Server application/binary files
  • Any old startup scripts tied to the previous install
Be careful with the database folder (typically RoonServer/ in your home directory or wherever it was stored). This contains your library database, and if your Docker container is pointing to the same folder as a mounted volume, don't delete it, that's your live data. If the Docker instance has its own separate copy that's already been migrated, then the old one can go.

A safe approach:

  1. Rename the old folder rather than deleting it immediately (e.g. RoonServer_old)
  2. Run your Docker setup normally for a week or two
  3. Once you're confident everything is working, delete the renamed folder

Hope this helps and answers your question :+1:

3

Thanks,

I think the database is renewed, but I renamed the old RoonOnNas Folder and will use that for a while. Looks good so far

Cheers,

Peter

4

Hey, @Peter_Schut

Great to hear it’s looking good so far. Renaming the old RoonOnNas folder and keeping it around for a while is a sensible approach.

Glad we got this sorted, and we’ll go ahead and close this one out. Enjoy your music! :slightly_smiling_face: