Would it be an idea to add an official backup/restore functionality on the Plex Server, so that it is possible to click BACKUP for instance from Server Settings and generate a complete, compressed backup file of all the metadata and related information needed on the server in case of a crash or server migration?
And a corresponsing restore function that can either replace or merge existing data?
In summary, these functions would be highly useful:
backup (all, or just seen/unseen-status)
restore / migrate (manual restore-button of all or just seen/unseen-status)
change section path (useful when migrating from one server to another or changing mount-point)
store/read metadata to media folder (for easier migration)
Override default backup location
Autobackup every X hours
Would be especially good for PlexPass users who may run "experimental" builds and may be concerned about downgrading after database upgrades. With a complete backup at the push of a button, one could relatively easily backup, upgrade, revert and then restore the old data in case of trouble.
Food for thought? What do you think?
EDIT/UPDATE: It'd probably also be useful to ONLY backup the seen/unseen and how far into each movie/episode watched. This should make it possible to do a fresh start without losing the valuable data keeping track of what's watched in a big library. A bit more coding, but highly useful. Comments, thoughts?
Would it be an idea to add an official backup/restore functionality on the Plex Server, so that it is possible to click BACKUP for instance from Server Settings and generate a complete, compressed backup file of all the metadata and related information needed on the server in case of a crash or server migration?
And a corresponsing restore function that can either replace or merge existing data?
Would be especially good for PlexPass users who may run "experimental" builds and may be concerned about downgrading after database upgrades. With a complete backup at the push of a button, one could relatively easily backup, upgrade, revert and then restore the old data in case of trouble.
I totally need this feature, I often change servers and then need to rescan all of the 1000s of movies and tv shows and over 24,000 songs. It often takes too long (hours of Boredom lol)
I totally need this feature, I often change servers and then need to rescan all of the 1000s of movies and tv shows and over 24,000 songs. It often takes too long (hours of Boredom lol)
There is details in the wiki on how you can do this without rescan but built in backup/restore would be better.
+1 such a feature should also include a step that lets you replace paths for the library sections so that if you restore to a new server or switch platforms that you can maintain the data but just remap it to its new location...
For example if your movies where in /mnt/remotesmb on linux and they are now in \\remoteserver\media but all the same data and structure.
+1 such a feature should also include a step that lets you replace paths for the library sections so that if you restore to a new server or switch platforms that you can maintain the data but just remap it to its new location...
For example if your movies where in /mnt/remotesmb on linux and they are now in \\remoteserver\media but all the same data and structure.
It would be interesting to learn the developers' take on this if they are reading this thread. Any thoughts of how useful, viable and realistic a backup/resture function on the server would actually be?
Would be great if we were to see a quick non- commit comment from development team on feasibility of requests such as this. If implementing the way dane22 suggests for instance is reasonably doable and thus a potential roadmap candidate or not…
Were we being completely thorough, this would also include a way to change the base paths during the restore. This would allow someone migrating from Windows to migrate their content from C:\CONTENT to /mnt/user/plexcontent when they move over to an unRAID installation.
