Thanks! I think I’ll go with storage spaces, regardless of what the rest of the folks on the project I’m working on advise, then. (they are creatures of habbit, and if not well documented, then they will not use anything). My project is somewhat separate anyway, even though part of the same network. (this is not as much a business environment as it is a communal environment, so I don’t have to worry about budget approval. LOL)
From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Shelby Sent: Wednesday, May 31, 2017 11:05 PM To: [email protected] Subject: Re: [NTSysADM] Windows Storage Spaces VS. RAID Our entire production Hyper-V environment sits on Storage Spaces and it's been rock solid. We have multiple clusters across datacenters with hundreds of VMs running all sorts of loads without issue. We're serving across roughly 108 spindles per cluster across 3 enclosures (with some SSDs for caching) doing three way mirroring allowing us to lose one entire enclosure and one drive in another enclosure without issue. We've deployed one S2D cluster on 2016 Core using NVME and it's amazingly fast and has been very reliable. We're working on expanding that to include S2R but are waiting budget approval. I have zero problems recommending Storage Spaces as a production workload capable feature on 2012R2 and 2016. Just design it properly and you're fine. Nathan Shelby [email protected]<mailto:[email protected]> 425-205-9047 On Wed, May 31, 2017 at 7:03 PM, Katherine M. Moss <[email protected]<mailto:[email protected]>> wrote: Thanks for that. I will definitely keep you guys updated. Sent from Nine<http://www.9folders.com/> ________________________________ From: "Andrew S. Baker" <[email protected]<mailto:[email protected]>> Sent: May 31, 2017 18:55 To: ntsysadm Subject: Re: [NTSysADM] Windows Storage Spaces VS. RAID I haven't spent a whole lot of time looking at them, but at one client, I've seen two instances (out of about 9 or 10) where they appeared to be created properly but would not allow more than 170GB of info to be written to the volume in question. This is on Windows 2012 R2. I'm currently not that big of a fan until I see more. The Windows 2016 storage implementation seems better, but we'll see. Regards, ASB http://XeeMe.com/AndrewBaker<http://xeeme.com/AndrewBaker> Providing Expert Technology Consulting Services for the SMB market… GPG: 860D 40A1 4DA5 3AE1 B052 8F9F 07A1 F9D6 A549 8842 On Wed, May 31, 2017 at 9:52 AM, Katherine M. Moss <[email protected]<mailto:[email protected]>> wrote: Hi all, I’m looking for some open minded folks on here who can possibly provide validation for both sides of this argument. I tend to prefer storage spaces simply because they are so simple to configure and they don’t require a set of eyes to read BIOS screens. I know some people on the other hand who are either creatures of habbit, or they don’t see the benefits of storage spaces, or they see it as inferior to RAID. What do you guys think? I am familiar with Dell configurations if that matters.
