@Jaap_van_Ekris said:
Oh No! if only there was a backup of the forum 
bump! bump bump!
Not only is this needed for convenience of reinstall but it would be tremendous help for cross platform migration as well.
yes yes i love this idea +1
I agree with all that has been said and this would be a great feature. Just one small addition, an old file clean up, i.e. PLEX stores the update installation files in the %LocalAppData%\PLEX directory (on Windows), and it doesn’t seem to remove the old ones after the next update becomes available. That’s just my two cents.
I agree with this request. I also read another request to enable server mirroring that might have some common functionality. I mirror all my media to a different server. However, the manual media mappings I have done are hard to to bring to the other server. Currently I use different drive maps on the two servers so ability to use flexible dirve mappings would be good. Also I would like my Plex pass to be valid for the backup server. It does not seem like the premium music library is enabled on my backup server.
+1 for this - it should be a trivial change for the developers to make (simply add a button to copy the backups across from the relevant location) - an easy win 
mew too! +1
Bump! Bump!
just like on the mac with timemachine you should be able to select the icloud (drive) to make regularly backups of your library…
Yup i’d like to see this 
Bump.
When is this coming???
It’s always hard to backup/restore metadata. It takes huge amount of time because there are millions of files. Thats why I use virtual hard drive and manually backing just one single vhdx file. Until we got proper backup solution I recommend this to you guys. I just replaced my Plex server last week; merge your registry backup, mount your vhdx and your are done.
This is my small walkthrough in another forum.
Bump bump.
+1000! would be awesome to be able to do this rather than using virtual machine images
+1 - Especially platform migrations - Windows to say, WD… or over to Linux/unRAID/FreeNAS, etc.
Just realized, this thread has been out there for three years now… Still no solution?
@m.hutchinson said:
Just realized, this thread has been out there for three years now… Still no solution?
That’s the part that confuses me the most. Even in the worst case scenario where you had to migrate to a completely different database or structure it shouldn’t take that long to develop something as simple as a database backup/export and make an import function. It could be as simple as dumping to a bunch of csv and jpg files in a big zip archive, or as complex as they decide to make it. But it shouldn’t take three freaking years to put together. I think they’re too distracted getting apps in everything to care much about the back end at this point.
@mwsmith824 said:
That’s the part that confuses me the most. Even in the worst case scenario where you had to migrate to a completely different database or structure it shouldn’t take that long to develop something as simple as a database backup/export and make an import function. It could be as simple as dumping to a bunch of csv and jpg files in a big zip archive, or as complex as they decide to make it. But it shouldn’t take three freaking years to put together. I think they’re too distracted getting apps in everything to care much about the back end at this point.
To be honest, I found out the hard way why migrating is such a PITA. It sounds simple, but I tried to move my library across machines (different flavour of Linux), with different mounting points etc. I quickly found out that a lot of data actually is extremely difficult to move and completely useless in the end. It is a mix of a database, a filesystem containing the plugins, cache data with some obscure sort of organisatation, and the media library itself. I invested quite some time in it (to understand how to back up in the future), and just ends as a horrible mess. Since my filepaths were altered slightly, the databases started pruning the old files, etc. And this is just Linux-to-Linux, Windows-to-Linux is much harder since you got huge conversion issues (even a simple txt file must undergo some treatment along th way…) and file-paths are structured differently.
In the end I decided to burn my bridges completely, install Plex in a Docker image (which can be isolated and backed-up quite easily) and just deal with the fall-out. Benefit is that I now upgraded to the new library types as well, which has some advantages, my digital take on Spring Cleaning. It wasn’t as bad as I expected, especially since I had a working original next to it to verify specific data (age restrictions, etc.). But I will keep my new Docker Image quite safely backed-up and my filepaths extremely stable
Jaap
Wil be great that function
+1
I would thoroughly enjoy this feature!! Let’s make Plex not just great, but amazing!!!
