Questions on server/client/storage strategy

facesnorth

Limp Gawd
Joined
Feb 5, 2007
Messages
240
If I am going to have a storage solution somewhere in the house, either FreeNas or Windows Server, then are people of the mind that it's better to keep this in a separate machine from their media client PC which is connected to the AVR/TV? Or just do it all in one box with VMWare and such?

Ideally have the least amount of expenditure to get the job done properly (not cheaply, just efficient and smart, no wasted product or energy consumption). Don't want my video to be choppy or pixelated, want it to be smooth. Will both stream and play files off my own storage.

The way I see it there are basically 3 components - the media server, the media client, and the storage server.... Just wondering if these can/should be combined into one box or separated. Leaning towards FreeNas for the storage element. I expect these will all be left on 24/7 for the most part.

As for the client element, our typical use is to stream Xfinity on demand, Netflix, pandora, play stored HD movies or audio files, show picture slideshows, and light video game usage (things like Civ IV and V).
 
The thing is that both methods (all-in-one and separate systems) are both ways to get the job done properly. Booth are efficient and smart in their own ways. The separate systems tends to be the easier route to set-up and maintain but at the cost of increased power usage, space use, total overall costs (assuming that you don't have parts to reuse). The all-in-one is relatively complicated by comparison due to dealing with relatively complicated virtualization configurations and requires significantly more time, effort, and research and more than likely significantly noisier but can be cheaper and uses less space (though not many people like seeing a giant PC in their living room.) and power overall. So it comes down to what factors are actually important to you.

Also, the media server and the storage server are often one and the same.

In my situation, I already had the parts for a separate systems setup. However, none of the parts would be powerful enough for the all-in-one nor was I willing to have a relatively noisy PC in my living room. Otherwise, I would have totally gone with an-in-one if I could.
 
An all-in-one box doesn't need to be some complex virtualized beast. You can build an all-in-one with Windows 8.1 and get pretty much all the features of the virtualized method, but a lot simpler to implement and manage (for a non linux/bsd geek). With Core i3 hardware, you can run your storage, media server and client all from the same box and still be able to run games like Civ V @ 1080p. It can also run in a quiet system sitting in your home entertainment center as well.

I personally, run my storage and media server in one box and my clients from another. I do this in order to offload my processing (video encoding/transcoding/virtual machines) and also to have a secondary system to send all my backups to, from my clients. The server then gets backed up to the cloud. A NUC is used to run my main client and it runs Windows 8.1 as well. Plex is used for handling all media.

Storage wise I use Storage Spaces with mirror drives for now. I can add drives, in two drive pairs, for expansion and once I reach eight drives total, I will migrate it to a double parity space for added redundancy. All this can be done with no downtime and I'm running ECC memory and ReFS so I know the data is safe on the cheap WD Green drives I use.

Jake
 
There's good and bad about both. As for me, I have a server setup in my computer room closet running linux. I don't even have a monitor hooked up to it, just SSH into it if needed. This way I can leave my HTPC off, and still access everything from my main PC. Just wish I could remotely power on my storage array, but I'm hoping someone comes up with a solution on that.
 
I personally prefer the server, NAS, client setup in separate boxes. I have multiple clients throughout my home so 1 single one did not make sense. If I take a client down I still want the server and NAS up. My NAS serves way more than just media files. It houses files for about everything and everyone in the house so it is up 24/7 no matter what. My server (Plex) is housed in a pretty beefy ESXi host, I had the hardware and again did not want to run the server and client on the same machine.
 
Yeah I think I prefer the idea of separate units. Just still trying to decide the most efficient way to do it both in parts and energy use.
 
Client/Server model preferred method.

You need to also determine how many clients you will be needing to serve, and if transcoding will be involved. This will then determine how much processing power your server needs to be. (then add some for a little buffer zone.. this is [H] forum, right) :)

All-in-one ... if server is down.. so is the client..
With client/server infrastructure.. then if server is down for "maintenance", then you still have clients available.
 
Really just one client. it's just me, my wife and our baby. most streaming will be done to just our one TV. if we are on our laptops at the same time, we prob won't be pulling anything off the server except perhaps some photos or transferring some files or something.

I'd like to be able to transcode if needed. I'd like a nice roomy buffer without adding significant cost or energy usage. I'd mostly prefer not to have any performance issues.

Here's what I'm thinking. At a minimum I need a unit to connect directly into my home theater receiver that can serve as a client. Not sure if I should have a separate unit for running games that I can just turn on when desired, so I can leave the client on 24/7, or if I should just combine those two into one single unit. Like I said, the only games we play are the occasional Civ 4 or 5 really. This client will be used primarily for streaming Xfinity, Netflix, Pandora, etc. Occasionally for pulling ripped Blu-Rays, Flac's, etc off of a separate storage server. And for playing photo slideshows and home videos off the server.

Storagre server I'm leaning towards ZFS with ECC, I want to be able to send asynchronous snapshots back and forth over a VPN between my server and an identical one at my parents house. So we keep an offsite backup for each other.

I'm not sure what else I'll need. But as far as my asterisk server, I am thinking of just running this on a new model raspberry Pi using nerdvittles guide for pbx in a flash.
 
Maybe btrfs actually. Looks like it has some nice improvements over ZFS, and I don't see any drawbacks so far in my reasearch....
 
Here's what I'm thinking. At a minimum I need a unit to connect directly into my home theater receiver that can serve as a client. Not sure if I should have a separate unit for running games that I can just turn on when desired, so I can leave the client on 24/7, or if I should just combine those two into one single unit. Like I said, the only games we play are the occasional Civ 4 or 5 really. This client will be used primarily for streaming Xfinity, Netflix, Pandora, etc. Occasionally for pulling ripped Blu-Rays, Flac's, etc off of a separate storage server. And for playing photo slideshows and home videos off the server.
Just combine the two. You're overly complicating things by having two separate units.
 
Back
Top