Trying to find where my Meta Data is store don my qnap. Looking at changing the folder to an SSD. Can’t figure out in Plex how to point the meta data folder.
Any help would be amazing.
Thanks.
Server Version#:
Player Version#:
I did read those, but it doesn’t show how to point your server to that new folder on an SSD?
Thanks,
Chris
If I may add here?
- The metadata is stored with the app in the
.qpkgdirectory structure. - I just completed adding what will become the
PlexDatashare. That shared folder will contain a directory entry (Plex Media Server) which is always connected via FileStation to the actual location in.qpkg. - With the implementation done this way, whenever you
Migrate Toto another volume (e.g. SSD), the linkage will automatically be updated when PMS starts.
Wow that’s amazing ChuckPa, how does that look and or operate?
Very interested.
Thanks,
Chris
Wow,
I am just confused on how you got the Plex director to open up like that on FileStateion. I am having a hard time getting the Plex server files to show. Or did you create these folders and point plex to each one?
This is the new capability I have added to the packaging.
When you install the next update, it will be there for you automatically just as it appears here.
I hope to have confirmation tonight of when it will be released. Fingers crossed, it will be in the next PMS release.
If you want, you can manually add the path for now but be advised it will not be the same type fuctionality
What I have done is to create a shared folder.
Then, in that shared folder, create a link to the appropriate location.
QNAP’s “Shared Folders” function does not behave that way
Chuck how will this impact those of us who have been using PMSLibShare from dane22?
So I figured out the shared folder function, but I just haven’t figured out how to direct plex to that shared folder for meta data. Thats the part that I am not following.
Looking forward to the update though.
You can’t put PMS metadata in an arbitrary shared folder without breaking the functionality of the QDK (QNAP Developers Kit) and the App Center (QPKG) mechanism unless you change how the package is built. Even if changed, the 'Migrate To" functionality will be lost.
Why we did it this way:
-
QNAP created the “Migrate To” functionality which allows any package to move to any volume. I leveraged their functionality to place PMS’ metadata on any volume, SSD or HDD, in the system.
-
PMSLibShare was created before QNAP invented and implemented “Migrate To” functionality. PMSLibShare was never changed to accommodate this capability. If you use “Migrate To” to move PMS to a new (SSD) volume, PMSLibShare won’t be valid/usable.
-
Dane22 and I worked together on how best to implement the marriage of these two capabilities. We wanted to preserve what was established, include the new Migrate To functionality, always track where PMS’ metadata is automatically, and adapt to the new naming which is being implemented for all shared folders
-
Lastly, after this is released, you can safely remove PMSLibShare if you wish. “PlexData” will takeover from that point forward.
Awesome write up! Thank you. So going forward I can just copy the folders ftom plex share / plex data to back up my server?
You are fundamentally correct.
The exact procedure:
- Stop Plex
- Open File Station
- Navigate to the PlexData share
- Navigate (click on) Plex Media Server
- File Station will refresh and show you what I’ve shown above.
5a. you will be in directory/share/*/.qpkg/PlexMediaServer/Library/Plex Media Server(wherever it resides) - You are now free to make an all-inclusive ZIP or whatever you need to do as
Be forewarned, PlexData/Plex Media Server isn’t a real directory/folder. It is a linkage ( a virtual folder ) which I create and maintain from within the package itself )
So no “back up” becuase of symbolic links etc. Do an actual copy, which is what we have to do now anyway.
What do you have in mind?
QNAP does not make application backups easy.
I know one possibility, for which I have code written but not implemented, is to move all metadata to a real share.
Doing so makes their Backup & Restore tools work
–however–
“Migrate To” automated move capability in App Center is lost unless I have PMS bring its metadata to it when it’s detected a move occurred. Attempting to move data at startup time could delay PMS starting by 3-5 minutes or longer on certain models.
Which is the lesser painful to lose?
I am not complaining at all. Just confirming a copy folder will do the trick with the new structure.
Right now I just copy the folders to an external drive.
If I peel this down to physical structures / paths:
-
Start with wherever PMS is currently installed, e.g
/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer -
I query QPKG for the
Install_Path -
I then look for
/share/PlexData -
If there is no
/share/PlexData, using the volume Plex is currently installed on, I createPlexDatathere. -
Now, regardless of where
$QPKG_DIR/Libary/Plex Media Serveris, I connect it to/share/PlexData/Plex Media Server
If you copy/backup on the QNAP directly and follow links , you’ll be ok. I’ve tested with a few backup techniques but not all (there are many tools out there)
Further, if you use SMB, you’ll find that mapping //QNAP/PlexData to a local drive will also follow the linkages. (This was important for Windows users)
I’m trying to lower the “geek level” as much as I can.
If this technique isn’t adequate, I can ratchet it up another notch and guarantee it will work in all cases at the expense more complex start/stop logic in the package itself.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
