@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.>
And I would say that by having a migration tool, it keeps development aware of what needs to be kept, and how to organize it. If you were having problems, is that indicative of lack of your knowledge of the structures, or lack of consistency of the product, or something else?
As I see it, it is indicative of a total lack of documentation and logical structure from Plex’ side. Basically, there is a separation between “The Software” and “The Data”. However, “The Data” also contains installed plugins (as I see it, they are post-installed), some sort of cache, etc…
A good question should be if I, as a user/admin, should be aware of the internal structure of an application. If I should, it requires Plex to maintain documentation and communicate it clearly when it changes. Or they could go the intelligent route and decide that as a user/admin I have no business inside these files/directories asides keeping them alive and transporting them between servers. IMHO, the later is the better option and requires Plex to provide a backup solution of some sort.
@m.hutchinson said:
Converting txt files between Linux/*ux and Windows is trivial. Testing or converting CR to CR/LF and back is two lines of code. Converting pathing constructs is not difficult. Given the data, there can be an intermediary export format, with a re-import filter based on the destination OS.
That part is simple, but you miss some essential details. The structure between Windows and Linux is subtly different (some files are stored elsewhere), so it really requires in-depth knowledge to see what filepaths need to be changed into what. The same goes for Linux, there are extremely subtle differences between the structures. So, if you know what you are looking at, yes. However, there are directories that contain millions of small files which are probably the cache in some way without any documentation about need and meaning.
@m.hutchinson said:
How about a straight export function of everything out to a zip/rar as a disaster recovery, and then the more technical of us can at least hack away at a cross load util? And no, I would not consider SSH’ing into a device for us to do it ourselves an acceptable backup strategy.
Well, I don’t mind using SSH :). But a backup strategy should be fool-proof. Hacking away until it works, with millions of small files, might be time-consuming.
My approach has been to switch to a Docker-container, and put all “The Data” in a dedicated folder. I simply shut down the container before the backup, make the backup and turn the container on again. Benefit is that the container is self-contained, so changing paths on the host-system doesn’t affect my container. I have no clue what I am backing up, but I do know that doing a clean install of the container with the same data directory simply works…
I am about to migrate plex to a new server / platform for about the 3rd time since I started using plex, not including complete start overs from corrupt / lost libraries.
With multiple family members having watch tracking on and carefully corrected metadata and poster art now the lack of backup and restore functions is getting frustrating… Overwriting the library files and backing up the whole thing manually is not really that easy.
it’s about time to get our backup, almost five years from the original request, and still with no real option to easy back and restore a server (think of migrating to a new server).
I agree. It seems like this is actually more work for the developers and those that troubleshoot to have logs, metadata, etc all in different locations… There should be a better way to back this up and migrate to something else in the event of a system OS change or a complete rebuild.
Charging for PlexPass would assume that this would be a feature that would have gotten attention as everyone eventually has to rebuild or repave.
Also would be nice if you have a auto back up to have it be able to be a set location on a mount point or drive, not just in a folder in plex. so if it all is lost or needs to be reinstalled you have that back up I am sure some one has said this just was not going to read the 500 posts. also if a auto back up is set up would be nice to have like 3 or 5 back up’s so when plex rights to the drive have it do a date then every one it does will be Unique. Also be able to set a min max on amount of back up’s just idea roiling around my head. Also I am really surprised plex does not have a auto back up and restore function yet Pretty Much all the automated media programs I use have this Function even plex’s compered has this function. +1 you have my vote
+1 for me also. I have been wanting a stream lined backup option for Plex. It’s kind of crazy that this topic has been on the radar for 5 years old now.
This is a big one. I have already migrated the location of my server folder several times, and each time I had to clean up a bunch of errors because I simply moved the database folder with it.
I have quite a bit of customization with backgrounds, cover art, etc. that I would like to back up if and when I migrate the files to another location.
I know backup is already implemented, but I like the idea of configurable schedule and change the “what” to backup.
Restore would be very nice from a fresh install standpoint as it means we don’t have to dig around the file structure anymore, and it would also make it easier when going from different OS platforms, which is interesting enough as it is without having to deal with digging around the file system. It would also make upgrading to a different Plex server much easier, which was already called out a few times.
a proper backup system for a app like this should of been one of the key features, or do like zoho mail. zoho saves all your folders, emails, settings online so when you reinstall zoho and signin everything is there just as you left it, no wasting time having to resetup everything the way you like it. this later idea would be perfect for plex since if you launch the server from the desktop it opens your browser anyway.
I do not understand how a program that is keeps track of such a large amount of information does not have a proper restore feature. I am have over 18000 files in my library and 8 users redoing it is not practical. I am a windows guy using FreeNAS command line is not a natural method so even with the backup the application does using it is another thing. Everyone assumes that all user are Unix/Linux gurus some are some are not I am in the lower middle and still unclear how to affectedly restore the backup being made.
ran across another issue that somewhat fits in here, and that is plex having the ability to delete files. i went to delete a entry figuring plex would just not track that folder or it’s contents any longer only to realize plex was actually deleting the files in that folder, being able to play the media through plex is one thing, plex having file operation access is entirely another thing.
What is urgently needed according to my opinion is indeed a functionally for backing up the data base of Plex server in a defined way, ideally by creating a backup file in the form of a zip file or some other archive file, of course with a corresponding functionality for restoring Plex server with its data base on the same or a new computer on basis of this backup file. Backing up the Plex data base directory it tedious and very time consuming due to the great number of individual small files. Please note that the meta data of the date base may be based on a lot of work, so that a professional and convenient way of backing up is highly appropriate and indeed urgently needed.
What did you think Delete meant??? Delete Means Delete.
Off this subject please add in a Restore path just like the backup path.
Would make change to a new plex sever or fresh install pretty simple.
We need the ability to backup the database & restore Simply.
Also In the GUI add a Backup Browse Function .
Add a way to use backups in the GUI to restore past database.
