external jbod enclosure connected via eSata compatible with storage spaces?
i may kicked out of gene pool question, gotta ask!
it seems older 6-drive bay server flakey run 2012r2. don't have other pc's laying around more 4 sata ports on motherboard.
however, have nice little slim-line i3 pc esata port sitting here gathering dust. can install 2012r2 std on it's internal hdd, buy external enclosure , use storage? create pools / storage spaces?
bill hagen, owner computer geek newberg, or www.thatcomputergeek.com
i may kicked out of gene pool question, gotta ask!
it seems older 6-drive bay server flakey run 2012r2. don't have other pc's laying around more 4 sata ports on motherboard.
however, have nice little slim-line i3 pc esata port sitting here gathering dust. can install 2012r2 std on it's internal hdd, buy external enclosure , use storage? create pools / storage spaces?
you can use esata port grow storage on slim box , have configured storage spaces run vms das (fastest way go btw).
you cannot run *clustered* storage spaces beast requires sas hardware all-around:
a) controllers, better pair of them @ every box performance , path redundancy
b) enclosure, should have @ least 2 ports have clustered config enabled better have 4 path redundancy, it's idea have @ least 2 sas jbods "passive hardware" not mean "unbreakable hardware"
c) actual disks should sas, can use sata <-> sas converters that's both expensive , begging troubles
why works way? simple: microsoft had failed deliver distributed lock mechanism lus (something lot of vendors did great level of success) need not capacity actual spindles multiple paths , scsi reservation per every disks (and missing sata present sas).
hope helped :)
Windows Server > File Services and Storage
Comments
Post a Comment