When done, now you have an image (perfect) backup of everything
MOVE THE ZIP FILE to someplace safe
1000 files is a lot to index. Imagine those with tens or hundreds of thousands and you see the scope of the problem. It’s not easy to solve for everyone
After it’s done, you can erase the install and then put the data back after. ( You might want to look at the structure so you see what it looks like)
PS: FYI.
I was involved in the Engineering meeting today about backups for exactly this type scenario
I did this over a year ago to provide a work around but won’t help here since PMS isn’t working right.
Thanx for your post.
But this i figured out already by myself, PMS has a share PlexData in the shares folder.
The backup is not my problem. Restoring works fine, that’s why i’m still able to run the 1.21.1 version. I just restore my backups.
Using a SSH Commandline is also no problem for me.
Migrating data to a different PMS installation on a different device with the same media files & library on another operating system is the issue that seems impossible.
I have a second PMS installation on Windows 10, that accesses the same QNAP-NAS media files. The “regular” movies & TV-Shows is no problem, they are indexed automatically by the agents.
But the Private files are not. MP3 / MP4 Tag’s Meta data is being read minimally. Collections are not restored. Descent Cast information (except for name) is not supported anyway.
Adding my experience as I have encountered the same exact problem on the same nas (TS-453BE).
Tried every steps reported in this post, reinstalled at least 10 times many different releases, but the problem was still occurring.
At the end I noticed that the plex data shared folder was wrongly mapped. I had linked .qpkg/PlexMediaServer and not just the library. It worked for months and I didn’t care about it, but at the end that was the problem. Surely a permissions issue. Deleting the shared folder and reinstalling plex fixed the issue. Restored the library and finally I can enjoy Plex again!