![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
luckylinux
Limp Gawd
- Joined
- Mar 19, 2012
- Messages
- 225
This is kind of the sequel of what was described in this thread.
Basically I find myself with two JBOD chassis laying around.
Finally I have some free time to build my NAS.
Since I cannot fit any motherboard into these old chassis (SC847E16-R1400UB) - not even socket 1156 (yes, 1156), let alone newer ones, I finally decided to get the host where these JBOD will be connected to.
I'm going to get a redundant PSU system which - unfortunately from Supermicro - only comes in dual socket configuration.
Therefore I selected the Supermicro Superserver 6027R-3RF4+ (redundant PSU, dual E5-260, 24 DIMM slots - up to 768GB RAM, 6 PCIe low-profile, IPMI 2.0, 4x1Gbit LAN). Now the "problem" is that this is a bit too much powerful for my needs since it "only" needs to do a ZFS zoop (or more) under FreeBSD with no plan on using Dedup. I think for starters I'll go with 4x8GB DDR3 ECC Registered RAM and single CPU (E5-2620) for budget reasons. After (I get my wallet a bit refilled) I plan on upgrading to 64GB DDR3 ECC Registered RAM and dual CPU.
I though about using Xenserver / ESXi and create a FreeBSD VM giving direct access to the disks (only to that VM), while creating other VMs that can use the free resources.
Does this pose some (or serious) problem, like not being able to access my data anymore, data corruption, being locked to ESXi / Xenserver, etc?
I ask these question specifically related to Xenserver / ESXi (obviosly data corruption occurs, but does create a NAS in a VM increase that risk).
What are your experiences ? Anyone running his ZFS NAS inside a VM ? Between the two, which would you choose? NAS on bare metal or in a VM? In the latter with Xenserver / ESXi / other ? Or would be better using virtualbox on a NAS running FreeBSD on bare metal to do the virtualization ?
Thank you very much.
Basically I find myself with two JBOD chassis laying around.
Finally I have some free time to build my NAS.
Since I cannot fit any motherboard into these old chassis (SC847E16-R1400UB) - not even socket 1156 (yes, 1156), let alone newer ones, I finally decided to get the host where these JBOD will be connected to.
I'm going to get a redundant PSU system which - unfortunately from Supermicro - only comes in dual socket configuration.
Therefore I selected the Supermicro Superserver 6027R-3RF4+ (redundant PSU, dual E5-260, 24 DIMM slots - up to 768GB RAM, 6 PCIe low-profile, IPMI 2.0, 4x1Gbit LAN). Now the "problem" is that this is a bit too much powerful for my needs since it "only" needs to do a ZFS zoop (or more) under FreeBSD with no plan on using Dedup. I think for starters I'll go with 4x8GB DDR3 ECC Registered RAM and single CPU (E5-2620) for budget reasons. After (I get my wallet a bit refilled) I plan on upgrading to 64GB DDR3 ECC Registered RAM and dual CPU.
I though about using Xenserver / ESXi and create a FreeBSD VM giving direct access to the disks (only to that VM), while creating other VMs that can use the free resources.
Does this pose some (or serious) problem, like not being able to access my data anymore, data corruption, being locked to ESXi / Xenserver, etc?
I ask these question specifically related to Xenserver / ESXi (obviosly data corruption occurs, but does create a NAS in a VM increase that risk).
What are your experiences ? Anyone running his ZFS NAS inside a VM ? Between the two, which would you choose? NAS on bare metal or in a VM? In the latter with Xenserver / ESXi / other ? Or would be better using virtualbox on a NAS running FreeBSD on bare metal to do the virtualization ?
Thank you very much.