Storage pools vs Raid 10

Storagepools vs Raid 10.
Hi. We are setting up a physical server (not running Hyper-V) to act as a Domain controller and a SQL server.
Plan is to use 8 x 600GB drives (SAS) sat up in Raid 10 (using onboard Raid controller - HP ML 350 Gen10 server)
Divide in 2 partitions C: for Win 2016 and D: for SQL data.

Not familiar with storagepools.
Is an option to use 2 disks in a mirror (created on raid controller and create a Storage Pool in File manager after windows is installed.
Looking for max r\w but also safety in case of disks crashing.

This setup may also be used for single Hyper-V host as well?

Happy for any suggestions
Tore JacobsenSystem adminstratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I've prefer "old school" hardware RAID 10  HPE Smart Array controller, easier to repair/restore.

Although why your DC is not virtual is another question ?
Tore JacobsenSystem adminstratorAuthor Commented:
Hi and thanx.
Small 10 user dentist office only using\ needing fast SQL access.
Have also sat ut hyper-V with 2 vm's (DC and SQL) but don't seem to get the same speed as with one physical.
Also question of licenses.
A pair of SDD will be much faster and less expensive than 8 HDD in RAID 10.

Don't use Storage Pools.

You should be running as VMs.
Get a highly available system for cyber protection

The Acronis SDI Appliance is a new plug-n-play solution with pre-configured Acronis Software-Defined Infrastructure software that gives service providers and enterprises ready access to a fault-tolerant system, which combines universal storage and high-performance virtualization.

andyalderSaggar maker's framemakerCommented:
Storage Spaces isn't good for fast writes as it has no non-volatile  write cache, So long as you get a model with a storage battery write performance will be good using hardware RAID. Read performance will be similar either way.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
This is a DC, not SQL.

A Windows Standard licenses, entitles you to use 2 VMs. (e.g. includes licenses)
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Run two VMs as has been suggested.

SQL of any flavour is not supported on a Domain Controller.

I have two very thorough EE articles on all things Hyper-V that are applicable to this situation:

Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations

Note that a small dentist's office could benefit from the SQL VM being on a pair of SATA SSDs such as the Intel SSD D3-4610 series in RAID 1. There would be more than enough IOPS for that scenario.
Doug BishopDatabase DeveloperCommented:
Also, I would NOT put the system drive on the same drives as SQL Server. Also, any flavor of SQL Server will benefit best with a minimum of three drives/devices, one for database, one for log and one for tempdb. Since you have space for it, use 8 SSD drives, each configured as RAID 1. Two each for system, database, log and tempdb. TempDB can actually be two drives configured as RAID 0 to give you more space. There is no real reason to have your  tempdb be redundant.
Eight SSD for 10 people running a light SQL program, where they are concerned about license costs for a VM, is IMHO not appropriate. I don't have that many SSD disks for a system running hundreds of interactive users processing millions of transactions per month. We started with 2 SSD, and only added more for capacity reasons.

A pair of SSD if fine. Any more than two should only be for capacity reasons, which is unlikely to be needed.
Tore JacobsenSystem adminstratorAuthor Commented:
Hi and thanx for all answers.
So to conclude (don't have SSD drives avaiable now so 8 sata it is)
Instead og making 1 Raid 10 with all 8 drives. Installing Hyper-V and creating 5 vhd (dc and 4 for SQL)
You suggests making 4 mirrors? 1 for hyper-v and DC-vhd, and 3 for SQL? (only have 8 drives)
andyalderSaggar maker's framemakerCommented:
I'd just make a single array but slice it into a small RAID 10 for Hyper-V OS and the rest as bigger RAID 10 or RAID 6 for the VMs and data. Depends which controller you are getting with the machine though.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The best way to get maximum throughput and IOPS is to set up all disks in a single array and then have two logical/virtual disks set up on that array.

A single disk is about 150MiB/Second or 250 to 450 IOPS depending on the storage stack configuration.

A set of RAID 1 pairs would perform very poorly.
Since you only have 8 HDD, the optimal configuration by far for SQL performance is all 8 drives in RAID 10. Every other configuration will provide fewer random IOPS to SQL with the given drives.

I only buy HDD if I am looking for capacity, such as for backups and recordings, but since OP is stuck with SAS HDD, RAID 10 is the best option, as everything else will relatively cripple performance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.