Given that auto update doesnt really work well using Map drives, I'm thinking of moving my plex installation to my storage server in order to get auto update of media to work because this function is very important with the amount of new content added to my library every day. Periodic scan isnt a option since there is to much risk of getting a scan loop unless i set it to every 1hr which isnt what i want.
We all know how big our plex data folder can get and since my C drive is a 64GB SSD, storing the data folder there isnt really a option. So my Questions...
- Has anyone tried to use symbolic links for the Plex data folder and if so any issues or performance problems?
- Has anyone tried storing the Plex data folder on pooled Drives? I use Stablebit Drivepool but i could be on Drivebender, flexraid or other. And again issues or performance problems? Also if you use Drivepool, have you tried Symlinks to store the data folder on the pool?
Ideally if i move plex to my storage server, i would like to store the plex data folder in my pool so that i dont have to worry about space and so i dont have to add a extra drive just to store the plex data folder (which would take up the spot of a potential data drive to expand my pool).
Ok, i did some searching on Drivepool forum and storing Plex data on the pool in any shape will probably not work. I guess im stuck using up a slot for a non pool drive. Using USB3 or eSata external drive wouldnt be a good option either im guessing?
From DP forum
Plex Media Server's database. This database relies on hard linking files together, instead of using the database to point to the same file for redundant files.
Because we don't support hard links on the Pool, you may notice missing images in Plex if the database is being stored on the pool.
It is a VERY bad idea to store Plex's data on network based storage and even worse to put it in DrivePool on a network based device.
Just spend the $60.00 or so and put a 250gb to 1tb drive on your server. Deticate it to Plex data only and you will not run out of space unless your media gets into the petabyte (1024tb) range. So far I have not seen anyone get even near that number although there are a few in the 75tb range.
It is a VERY bad idea to store Plex's data on network based storage and even worse to put it in DrivePool on a network based device.
Just spend the $60.00 or so and put a 250gb to 1tb drive on your server. Deticate it to Plex data only and you will not run out of space unless your media gets into the petabyte (1024tb) range. So far I have not seen anyone get even near that number although there are a few in the 75tb range.
I have the drive...that is not the issue. What i would like to avoid is using up a slot in my case just for plex. For Drivepool it wont be a possibility anyways as they stated on there forum. What about running it from a USB3 or esata drive connected to my storage server. If it wasnt for plex short coming with the auto update of media when using mapped drives or UNC path, i could leave plex on my app server that it has its own drive.
I have the drive...that is not the issue. What i would like to avoid is using up a slot in my case just for plex. For Drivepool it wont be a possibility anyways as they stated on there forum. What about running it from a USB3 or esata drive connected to my storage server. If it wasnt for plex short coming with the auto update of media when using mapped drives or UNC path, i could leave plex on my app server that it has its own drive.
Do not complicate Plex more than needed and do not set it up where the Plex data folder requires that you access it via your network. If you are low on USB ports then you can get a USB hub to expand the number of ports.
Also be aware that nothing Plex does (Except maybe playing some very high bitrate files) requires that the drive providing the data be particularly high speed. USB 2.0 is plenty fast enough for 99.9% of anything Plex is likely to need. The only place where Plex needs real speed is in the CPU on the server if you are transcoding.
What Plex does require is steady and uninterrupted connection to its database and that is wher both DrivePool and networked storage have problems. Those are fine for the media files but problematic for Plex's database.
And to add what Elijah said - if your data folder is on network resource then it will be very difficult to support you because the integrity of the log file content is lost. Hours were spent before looking into issues because the log file did not have everything that was logged and also the database access is millions of transactions and you will end up at some point with database corruptions. So local drive - USB3 is probably ok but not optimum
If this was directed at me, and I suspect not, then I have not seen any post saying that auto updating was not working for mapped networked drives. In fact all my media, except for a very few specialized files, reside on a DrivePool drive that is mapped and that mapping is used on my server for my libraries and auto updating works great.
As far as partial scanning goes that I do not know about as I don't micro-manage my server. I just set it up and let it do its thing so, unless there is a problem, I would never know if a scan was full or partial.
If this was directed at me, and I suspect not, then I have not seen any post saying that auto updating was not working for mapped networked drives. In fact all my media, except for a very few specialized files, reside on a DrivePool drive that is mapped and that mapping is used on my server for my libraries and auto updating works great.
As far as partial scanning goes that I do not know about as I don't micro-manage my server. I just set it up and let it do its thing so, unless there is a problem, I would never know if a scan was full or partial.
No not you but at saitoh. The only thing we proved was partial scanning not working for all drives: internal / external / network
I too like things nice and simple.. I have a 60TB sever and PMS is installed on the same machine.
The SSD O/S drive is only 128GB and was filling up fast. I hooked up an old 2TB drive that i had lying around via USB 3.0, moved the Plex folder to that and haven't had an issue in the year or so since I did it.
I will add I did consider at the time storing the Plex data on the pool and just decided for myself it was probably a bad idea. :)
I too like things nice and simple.. I have a 60TB sever and PMS is installed on the same machine.
The SSD O/S drive is only 128GB and was filling up fast. I hooked up an old 2TB drive that i had lying around via USB 3.0, moved the Plex folder to that and haven't had an issue in the year or so since I did it.
I will add I did consider at the time storing the Plex data on the pool and just decided for myself it was probably a bad idea. :)
This is what i wanted to here
Do not complicate Plex more than needed and do not set it up where the Plex data folder requires that you access it via your network. If you are low on USB ports then you can get a USB hub to expand the number of ports.
Also be aware that nothing Plex does (Except maybe playing some very high bitrate files) requires that the drive providing the data be particularly high speed. USB 2.0 is plenty fast enough for 99.9% of anything Plex is likely to need. The only place where Plex needs real speed is in the CPU on the server if you are transcoding.
What Plex does require is steady and uninterrupted connection to its database and that is wher both DrivePool and networked storage have problems. Those are fine for the media files but problematic for Plex's database.
Im not complicating things :)...i think you misunderstand my intentions. My plan wasnt to access the plex data folder over the network.
Current setup:
App server: Plex installed with Plex data on its own drive since C drive is too small. Media sources in plex via mapped drive.
Storage server (all internal drive): contains all my media
Problem is Auto update from what i have been noticing since yesterday is working on and off. I assume it is because media is being access via mapped drive (explain by sa2000 and read on wiki) There is a problem with the partial scan via windwos but i dont think it is related to the auto scan not firing off when new content is added
Intention:
Move entire plex setup to Storage server to gain Local drive as source instead of mapped drive.
What i want to avoid is using up a internal slot in my case for a drive dedicated to the plex data folder (since C drive is a SSD and too small) because i would prefer keeping the internal slot for storage expansion with Drivepool. So since storing the plex data folder on the pool is out of the question, the only other alternative is to store it on a external USB drive (USB3 since i have the ports).
From what davehobson says, it is feasible but i would it affect things like scan time, transcoding storage/time and offline sync operations because it is using USB. I transcoding is dependent on CPU (will probably switch out the Pentium G3220 3ghz for a I3-3220 i have spare).
From what davehobson says, it is feasible but i would it affect things like scan time, transcoding storage/time and offline sync operations because it is using USB. I transcoding is dependent on CPU (will probably switch out the Pentium G3220 3ghz for a I3-3220 i have spare).
I hope that makes it clearer? :)
Scan time negligible... I certainly didn't pick up on anything noticable.
I share my server with a few friends... some need to transcode others don't.. There has never been an issue with 3 transcodes.(PS the transcode directory can be independently assigned to any drive you choose, but mine is again set to the USB)
Sync times I cant say, I dont really use it although some of my friends do, but to be fair they probably just work on the basis of "its done when its done"
None of them have ever suggested they suddenly got a major slowdown.
Thanks for this post it cleared up an issue I was having with my posters not showing, now I realize it’s cause I put the PMS data folders on Drivepool, thanks so much for this discussion saved me so much time.
