"The database is open, unless you shut down PMS before"
so the PMS should be shutdown before backup? i didn't knew that.
Goes for all databases, unless one goes out and buy a database backup agent.
/T
i really don't understand what you are meaning..
Just like the Plex-Devs, i don't see any reason for only backing up seen/unseen status ...
So again, whats your problem?
I would say this thread can be closed - because the initial request is already implemented. If you want something else/further , you should make another thread.
Or maybe you should explain what you mean. Not just saying "I want what the Topic-Starter said" , which is, again, already implemented.
I don't think anyone is having any serious problems here, as this is a feature request forum where users are actually encouraged to request features to the developers. If you actually took a few minutes to both read the entire thread and compare to what is implemented in PMS, you might notice that the backup functions implemented do not yet match what we have humbly asked for.
As others have rather eloquently pointed out - what would you do if you either have a full-on disk crash or need to migrate PMS from one server to another. Would you be able to migrate the data you need from one place/backup to another without using command-line? Currently you can't, unless it's a super-secret-hidden feature only available to a very select few.
It's really great that Plex has started to see some backup functionality, but until it's implemented as described in the first post, I suggest we leave this one open.
Agree?
-y1
ok. i didn't knew that the scheduled backup is kind of a "small backup" .. than , you are totally right. thats not what we requested.
but a topic like "scheduled backup as real backup/restore" would be take more attention to this issue.
because, i think, like myself, people think that the scheduled backup is already a real backup.
Everyone else seem to understand this just fine - might I suggest either reading up on the details or taking a slightly more moderate approach moving forward?
Point 1 - Backup - does not backup everything at the moment
Point 2 - Restore - there currently is no restore button in PMS that you can use after a crash or if you migrate some/all data to different server
Point 3 - Change Path - not globally implemented so you can move some data from one disk/NAS to another.
Point 4 - MetaData - It's not even backed up today - why would you call this a double request?
Point 5 - Override Default Location - yup - that one is pretty much done - correct :-)
Point 6 - Autobackup every X hours - it is currently hard-coded to every 3 days - what we're asking is to configure it.
Again - this is what a humble few users have asked for. There is no demands, threats or anything like that. As long as we keep things polite and civil, we might even ask for Plex to make us coffee, although I somehow doubt that would get too many votes... But I ask again - why on earth would we close a topic that has 1 out of 6 asks fully covered and start over? How would that benefit the developers or bring more value?
-y1
+1
Re bump! I’d happily forfeit trailers for this to be developed further!
Come on people. LIKE the first post!! Let’s get our PMS’s backed up properly!
I find it interesting that Plex continues to use a flat-file database structure that grows to millions of files as your content library grows. This kind of design is pretty quick for smaller content sizes, but there's pretty big disadvantages with regards to exactly what's being discussed in this thread. To tarball or zip the database up might take hours on its own, whereas mysqldump, even for a fairly complicated/large database, takes far less time. You're additionally dependent on your filesystem reliably handling those millions of tiny files.
I guess my question is - why not use a SQLite/MySQL database for the metadata blobs, and put the thumbnails/artwork/etc inline with the content itself?
this is my cron script, it runs weekly.
#!/bin/bash ...needs some simplifying, $SOURCEDIR is everything you need. (my .bz2 is 101Gb which is why I don't do this daily - I rarely make a large amount of manual changes to metadata/art, if do, I just manually run the script)
Have you tried a restore?
my .bz2 is only 594M, but I'm only about 4% through ripping my library...
I reduced it to 522M with lzma.
cd $BACKUPDIR
tar -cf ${FILENAME}.tar *
lzma -e9 ${FILENAME}.tar
+1
In program backup/restore function sounds very good! 2 Weeks ago I upgraded my server from Windows 7 to WIndows 8.1 and it costs me 2 days to restore properly from the saved backup!
So, I vote YES for in program backup/restore
In program backup/restore function sounds very good! 2 Weeks ago I upgraded my server from Windows 7 to WIndows 8.1 and it costs me 2 days to restore properly from the saved backup!
So, I vote YES for in program backup/restore
And with the amount of files piled up in the library, I really doubt you could have done it faster with a Plex build-in solution, if it really took that long time!
+1
Would be a very nice feature! +1
+1
+1, the current built in backup is not cutting it for me, I'd love to be able to customize and run a full backup anytime I want!
Scary this still hasn’t been implemented yet!!
bump!
Bump!!!
keep adding likes to this one guys and gals!
Thanks to OP (June 2013)
+1 :rolleyes:
@halfluck said:
Thanks to OP (June 2013)+1 :rolleyes:
Looks like the likes are gone, we have to vote again…
Jaap
