Hi @Pacoinmass,
You’re spot on correct here, it looks like you’ve had a successful backup complete at the date included in your screenshot. 
Will migrate today. While the new update appeared to have improved some aspects of performance for me, more often than not, Roon still has a lag when receiving commands from the remotes.
I have a few questions regarding my Previous Roon Server before I run Roon on the Dell Windows 10 machine.
The migration guide says:
Previous Roon Server
Once your new Roon Server machine is up and running, you can continue running Roon as a remote on the machine that previously ran your Roon Server. It is important that you “clean up” the machine that was previously running your database. You do not want the same database running on two machines.
We recommend renaming or deleting the Roon database folder on the machine that previously ran your Roon Server. You can find the Roon database folder here.
- What does it mean to “clean up” the machine that was previously running my database?
- Rather than renaming or deleting the Roon Database folder, can I simply stop the server in Docker?
- If I shouldn’t just stop the server in docker, is the database below, the correct one to rename?
- If I want to switch back to the NAS server, would I simply turn on the server in the Container (and if it was renamed “olddatabse” on the NAS, rename the database “database”? Understanding I would lose changes, etc. for a couple of weeks between reverting (if necessary).
Hi @Pacoinmass,
Thanks for the reply, here are answers to each of your questions:
“Cleaning up” just means making sure the old database on the QNAP can never start back up and go looking for your zones and library again. The risk we’re avoiding is two Roon Servers being live on your network at the same time, they’ll fight over the same endpoints and can corrupt each other’s state. It has nothing to do with your music files; those stay exactly where they are. We’re only retiring the old database.
Yes, for your situation that’s the cleanest approach, with one addition. In Container Station, stop the roonserver container and also turn off its “auto-start” / “start on boot” setting. That second step matters: if you only stop it, a QNAP reboot or a Container Station update could quietly bring the old Server back to life, and then you’d have two live databases. With auto-start disabled and the container stopped, the old database stays safely dormant, and you don’t have to rename or delete anything. That also keeps your revert path simple.
Assuming this is the RoonServer folder tied to your Docker container install, yes, you’ll want to rename the ‘RoonServer’ folder specifically. I can’t tell 100% from the screenshot, but it does appear to be correct.
Correct. If you go the stop-the-container route and don’t rename anything, reverting is as easy as starting the container again (and re-enabling auto-start). If you did rename RoonServer to RoonServer_Old, you’d stop the container, rename it back to RoonServer, then start it. Two things to keep in mind: (1) never have both running at once, stop the Dell’s Roon Server before bringing the QNAP one back up, and (2) as you noted, anything you did on the Dell in the meantime (play history, edits, new settings) won’t carry back to the older database, so you’d lose that interim window.
On your note from the previous post about remotes still lagging, that’s worth watching closely once you’re on the Dell. The i7-3770 has far more headroom than the TS-251’s Celeron, so the migration itself is really the test of whether that stutter is hardware-bound like we suspect. Keep us posted on how it feels over there.
You’ve got this, and we’re here if anything comes up mid-migration.
Thanks.
Up and running on the Dell. Can I use the Mac version as a remote? Want to make sure the server part doesn’t start on the Mac.
Will report back on performance in a few days.