My current NAS (QNAP) is running low on disk space, I have seeded the data to another NAS (QNAP). Plex is installed on both devices.
When connecting to the source QNAP via WinSCP; I have found the Plex directory is located in the following directory “share/CACHEDEV1_DATA/ .qpkg/PlexMediaServer” ; I then navigated to the destination QNAP via WinSCP and noticed there is no PlexMediaServer under the .qpkg directory. I believe this does exist given I have not logged into Plex on destination QNAP.
Should I login with the credentials on the destination NAS to propagate the PlexMediaServer directory or no?
Should I just copy and paste the PlexMediaServer folder from the source to the destination, then login? Then the migration is complete?
Have Plex pass lifetime.
What I am looking to accomplish:
retain Watched
retain custom posters
retain Activity such as Top Users, Top Played, Play history and stats ranging from 30 days to all time
If someone has a detailed video or instructions on how to accomplish this, I would be grateful.
/share/CACHEDEVx_DATA/.qpkg/PlexMediaServer will exist somewhere if you’ve installed PMS on that host.
You cannot transfer the server from one host to another until PMS is installed on that host.
Once installed on both –
– Create the PlexData shared folder as shown in the below How-To
– It’s important PMS be started and then stopped once after creating the shared folder (it populates the locations for you)
Now make a backup (ZIP) of the contents of “PlexData/Plex Media Server” (you must get into the Plex Media Server directory to see all files and subfolders)
When the ZIP is complete, transport it to the same directory on the new machine
UNZIP it
At this point, you will have cloned server 1.
– If you want to change this and make a “server 2” with the same data,
– DELETE “Preferences.xml”
– Start PMS
– Claim it
The instructions may be dated but they are current. Please follow as written and use Defaults. (Do NOT manually place the folder inside a .qpkg directory as you’ll defeat the whole purpose)
PlexData
Is the exact upper/lower case you are to use.
By doing this, PMS will use that shared folder automatically.
No manual intervention is required on your part.
In the future, should you move PMS to a different volume on the NAS. it will automatically track to that new location.
Step 3 is confusing me. I do not have an existing folder with the name so i skip and go to " : Create an empty file "${QPKG_DIR}/Library/Plex Media Server/.disablePlexDataSymlink""
I navigate to /Share/CACHEDEV1_DATA/ .qpkg/PlexMediaServer via WinSCP and then right click, create new file and name it .disablePlexDataSymlink - I then choose okay and a new window comes up, I am unable to save.
I am trying to make since of this, I am taking these instructions quite literal
You create the dummy file IF AND ONLY IFF you have have an existing shared folder named “PlexData”.
– Some folks have created shared folders (for their media) named “PlexData”
– The dummy file turns off the PlexData feature and allows the shared folder to be used as a normal shared folder.
You’re over-thinking it. This isn’t hard. I can show you in a screenshot.
Create the EMPTY PlexData shared folder anywhere you want on the first NAS
Stop PMS, Start PMS, then stop it again (so we can make the backup)
same result… Going to call QANP on this one unless you can think of something.
Once I do the backup, I suspect, create the same PlexData folder on the destination NAS, then extract and drop the content of the backup into this location, then start PMS and login with the appropriate Plex account, then switch the server from old to new?
It provides a link (to fool FileStation) so you can get into the Plex Media Server directory when there are problems or special cases.
It supersedes the old “PMSLibShare” package and other manual methods because it automatically tracks wherever (which volume) PMS is installed on. (the App Center “migrate to” function)
Problems are things like “Retrieve logs without using SSH when PMS won’t start”
Special cases are “Make a backup of all server data”
I implemented it below the package, in the base filesytem, so it would work with both SSH , SMB (wide mapping), and FileStation
QNAP Connected, we can create, delete edit content in the “PlexData” folder , any child objects below this, denied. Vetted permissions everywhere, solid no issues.
Confirmed PMS service is stopped; QTS version 5.1.1.2491
Also confirmed, same issue on the destination NAS
