So, @brian: if I’m migrating a library to a completely different server which has exactly the same music files, except that the paths to them might be completely rearranged (either because of a regrouping to split things across available physical devices on a new Linux server or the above PLUS moving to a Windows environment with freakin’ drive letters)…
Is this How do I move my collection to a new folder, hard drive or NAS, Will I lose my edits? the complete how-to (perhaps along with the companion KB entry “How do I move my Roon library to a new computer?”), or are there any other best practices one should be aware of?
Basically, our existing RoonServer setup is, um, suboptimal in a number of ways, one of which is that the tracks are being read from two distinct mounted volume shares from NASes, and (because of history having to do with how music is stored on those shares, with some areas holding tracks Roon should index and other areas holding tracks which should not go into the Roon library) there are cough seventeen distinct watched folders set up in Roon, pointing at subtrees within those two mounted shares.
My plan is to have the new Roon server read tracks from three internal spinning disks, each one containing only tracks Roon should read (the weird earlier go/no-go rules now incorporated in the script which will keep the internal disks updated from the NAS masters rather than in Roon’s watched folders lists), and have just three watched folders: one for the top of the tree of tracks on each physical local track-storage disk. Any obvious problem with that scheme?
…and if I follow the advice above (disable, apparently no need to actually delete, all the watched directories in the current RoonServer, then shut down and grab a database backup, then migrate that database to the new hardware) – Roon should actually recognize albums in all those different places, and retain my laborious edits over the last couple of years like gathering multi-disk sets together into one album, finding an existing release to tie unrecognized albums together, per-album tag and image source overrides, track and album tagging?
Also… to try to minimize downtime, I’ve been thinking of getting the new server going and tested with a 60-day trial license, then rolling the production database in. Are there any gotchas there?