#How to update a new servers collections from a cloned DB & Metadata?

1 messages · Page 1 of 1 (latest)

surreal yacht
#

I have a PMS already with all of my collections and overlays, etc exactly how I like them, and I am using that PMS to clone the DB & Metadata to any new PMS so everything is already built and ready to go including my collections. My question is, if I have all this already pre built, do I just copy everything from that servers folder to the new one like it's assets, cache, logs, overlays?

I want to be able to maintain and update it without it having to rebuild everything over again and hammer my brand new DB, I have over 500 collections in total for the server, so I'd rather just update on it's normal scheduled runs instead of having to rebuild everything would be key in this situation.

half night
#

That should hopefully work 🙂

#

It depends on how the cloning of the database goes really - if the IDs change then PMM may end up re-applying collections etc

#

If you're literally copy and pasting the entire database that should be fine

surreal yacht
#

I know that when everything is cloned over to the new server, anything that is a Plex Smart Collection, it'll load everything but when you select a collection, it shows not titles inside of it. Only when you edit the collection and update it it'll then load the titles into it. This is only for Smart Collections

silent patrol
#

PMM references things in the Plex DB by their rating key, which differs from install to install [Star Wars on my system has a different rating key than yours, for example]

surreal yacht
#

What exactly is a rating key and how does that play a role in this situation?

silent patrol
#

When you add a thing to a library, Plex assigns an internal ID to it; what it calls its "rating key". That value apparently differs from install to install, so if you move collections from one Plex to another there exists some small chance that the movies in the collection have different internal Ids and won't be found in the new Plex.

Moreover, the metadata and images associated with things in the database are stored under opaque IDs down in the metadata folders, so there's a [I would imagine good] chance that if you move just the database to the new plex, all the links to artwork and the like will be broken.

If you're copying the entire Plex app data folder and just replacing the Preferences.XML or claiming it in some other way, this is not a problem.

surreal yacht
#

Ok thank syou for the response, that makes sense now.

If you're copying the entire Plex app data folder and just replacing the Preferences.XML or claiming it in some other way, this is not a problem.

By doing it this way, can I just copy and paste the same assets, cache, logs, etc to this new servers PMM folder and go about doing my scheduled runs without it having to rebuild all the collections again, or should I not copy over some certain folders/files?

I know Yozora said it should be fine, but just want to make sure everything should be copied over or only certain ones should.

silent patrol
#

I would imagine so.