Avoid meta data reset and library rescans with media library move?

I run Plex server in Docker on one computer and the media library is stored on another computer (NAS server). I’m moving my whole media library folder from the current NAS server to new NAS server. When done I would simply need to change the NFS source (i.e., 10.0.0.10:/mnt/pool/plexmedia to 10.0.0.20:/mnt/pool/plexmedia) for the mount point on the computer running the Plex server app (/mnt/plexmedia).

I’m doing a mirror copy with rsync so the file & directory structure are exactly the same and so are their timestamps. When done Plex server app SHOULD see no changes and NOT re-add all the media as if they were new and subsequently my recently added, watch history, on deck, etc. data should stay in tack… correct??? If not, how do I guarantee Plex won’t re-add everything as if new and lose my recent and history meta data??

Are you keeping everything in Docker or are you switching to the native app ?

If moving to the native app, you must remember to match the UID/GID the native app uses.

Also, as part of the move,

  1. Turn off all automatic scanning

  2. Turn off Empty Trash

  3. Give a read here. The procedure is fundamentally the same for any Linux-based environment. Make certain you understand the concepts and then adapt as required for your situation.

  4. If the mount points are different (as seen by PMS) then this applies:

  1. The ‘cloning’ follows this general procedure:

I’m keeping everything in the [official Plex] docker container. Since the new media library folder is a clone Plex should notice no difference, correct? So, I can skip turning off those features in Plex and just need to shut down the container, unmount old server NFS share, mount new server NFS share (again, using the same mount point as before) and spin up the Plex container to see everything there as if nothing happened…?

@instarlation

As long as the media, inside the container, is where PMS expects it then you’re good to go.

When I do things like this,

  1. Tarball of the container /config & copy to new machine.
  2. Create the new container (adjusting source path if needed but maintaining internal)
  3. Extract the source machine’s tar ball into position.
  4. Verify hardware access (UID/GID) if needed
  5. Start it up.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.