Plex / file storage advice
Currently I have an old workstation (intel x9650 o.c. to 3.63, 8gb ram) that i'm using to host plex as well as backing up other family computers and keeping redundant backups of photos.
As far as storage goes i have a 240gb ssd for the os and then a 160gb internal storage disk for local libraries. I then have three external drives currently, a 1tb and a 2tb connected through esata (3gbs) and a 500gb connected through usb 2.0.
I recently started a trial of drive pool to make life a little easier by better utilizing available space and making only certain files redundant rather than everything on a particular disk. I currently have the 1tb, 2tb, 500gb, and the 160gb internal pooled together but i'm quickly running out of space as i'm in the process of ripping all our dvds/blu-rays.
I'm looking to expand my storage and my transfer speeds. As of right now i'm looking at getting a mediasonic 4 bay probox and 3 or 4 2tb or 3tb WD red drives. To connect it i was looking at one of these figured use one esata for the enclosure and switch one of my internal drives over to it (most likely the ssd since correct me if i'm wrong but i should get the best performance boost out of it). I would then add those drives to the existing pool.
So finally my question. Is this a decent setup for what i'm trying to do and should i take it a step further and make the drives in the new enclosure into some form of a raid to increase redundancy and/or improve performance? Any and all suggestions are welcome but i'm trying to keep this as a very budget build hence not filling the enclosure with 4 x 8tb drives to start.
Also since i know it will come up i plan on getting setup on either crashplan or backblaze once i have things up and running for a true backup of everything.
Thanks in advance for the advice.
Posted Oct 8, 2016, 6:11 AM UTC
Your setup sounds like something I migrated away from at the end of 2015, though I only did so because I was tired of all the boxes / wires for everything being everywhere (which is also the primary reason I consolidated all my physical PCs into a single, albeit beefy, ESXi host in the first place).
I had an eSATA controller in my ESXi host, which I used 'pcipassthrough' to attach to my WHS2011 VM. To that eSATA controller, I connected a 4x5.25" eSATA enclosure. I installed a 4x3.5" in 3x5.25" hot swap cage, and a single 3.5" to 5.25" hot swap tray into the eSATA enclosure and populated it with a bunch of 1TB 3.5" drives I had available. It worked great, but I had one issue -- the enclosure didn't have enough air flow, and I kept killing the shitty WD drives that were in it (several blues and a black, but strangely the greens survived!).
I migrated to 2.5" drives, stored in 4-in-1 2.5" to 5.25" hot swap cages. I'm currently sitting at three 2TB 2.5" drives (though one mysteriously started developing bad sectors, so it's been temporarily replaced with a 3.5" 3TB Toshiba until I can get the 2.5" replaced under warranty).
The whole time I stuck with StableBit's DrivePool. I mostly use the pool for media (TV shows, movies, and a small amount of music I download from mixcrate) storage, though I did start using it for my Macrium Reflect backups (I have two Windows VMs that I back up).
I'd stay away from RAID, if possible. If you need redundancy for some of the data that will live on the pool, DrivePool supports per file / folder duplication, so you can have the data duplicated between 2, up to the number of HDDs in the pool, drives. The drives are also plain NTFS, so if you ever had the need, you can stick them in an NTFS capable PC and read the contents without issue. :)
Sounds like a lot of cage adapters...
Unfortunately I don't have the space for a large case (currently live in a small 2 bedroom apartment). So being able to semi-remotely locate the drives is nice. Eventually once funding and space is available a single case would be nice.
The keeping the drives as NTFS is also nice considering my track record of doing dumb things on occasion. I've been shying away from both windows storage spaces with parity and other software raids because of this. The only reason i brought up the raid is for improved write performance but in the long run its probably not worth it since i'm not continuously writing large amounts of data.
Any comments on the hardware i linked? Is there anything you would consider changing about the proposed addition to the setup?
As far as drivepool is concerned thanks for reassuring me that it will fill my needs. My only trouble with it so far has been it doesn't handle running about of space very well, it basically locked up when i tried to add files when it hit the limits for the drives, no warning or anything windows just showed the transfer speed as zero.
Thanks for the info, at least i know i'm at the very least in the right ball park.
DrivePool supports using SSDs for write caching via a plugin. ;) I've never run my pool out of space before, so I've never encountered that issue before...
As to the hardware you've mentioned -- the only opinion I have is against the Western Digital HDDs. In my 20+ years of being a computer tech, I've had far too many failures with WDs to ever use / recommend them again. :) Beyond that, I don't have enough experience with a large enough array of eSATA gear to make a statement. :)
Thank you for the guidance, i will definitely take everything you said into consideration.