RAID recommendation for Hyper-V host
-
I don't see the need to separate the drives into different arrays for this.
-
What server are you going to use as your host?
-
@i3 said in RAID recommendation for Hyper-V host:
Two drive Raid 1 for the OS
min. 4 drive Raid 1+0 for the data array (15k SAS)That's very silly, of course. As I always say... be worried that your ERP vendor might not be thinking very clearly about good system setup. But it will work fine, it's just wasteful on resources. Nothing risky there.
-
@i3 said in RAID recommendation for Hyper-V host:
My thoughts were to put the virtual machines OS' on the two drive raid 1 array and the data drives for both our ERP and file server on the second array.
Yup, that's fine. It would be better to have all six drives in a single array not in split arrays, but the split arrays aren't dangerous here, just not as good speed or capacity as merging them all into a single array. A single array would be better all around, no downsides.
-
@wrx7m said in RAID recommendation for Hyper-V host:
I don't see the need to separate the drives into different arrays for this.
Other than the vendor demanding it.
-
I say "demands", but really he only said "recommends." So they might be perfectly fine with a better setup than they recommended.
-
@scottalanmiller said in RAID recommendation for Hyper-V host:
@wrx7m said in RAID recommendation for Hyper-V host:
I don't see the need to separate the drives into different arrays for this.
Other than the vendor demanding it.
Ah, but they only "recommended" it
-
@wrx7m said in RAID recommendation for Hyper-V host:
@scottalanmiller said in RAID recommendation for Hyper-V host:
@wrx7m said in RAID recommendation for Hyper-V host:
I don't see the need to separate the drives into different arrays for this.
Other than the vendor demanding it.
Ah, but they only "recommended" it
I beat you.
-
Prices on SSDs have come down enough that they compare pretty favorably to 15k drives.
-
@i3 said in RAID recommendation for Hyper-V host:
Our ERP data size is around 400GB and our file server data size is around 700GB.
Honestly, at that size, you would fit on SSD RAID 1 which is faster and with good drives, safer, than the RAID 10 with 15K. Might be cheaper too, or not, hard to say.
-
In this case, I would suggest doing some performance tests on your existing ERP server to see how many iops you have currently, then see what you will get with various disks in RAID10
-
I didn't realize enterprise SSDs had come down enough to compete with 15k drives. Interesting.
-
@wrx7m said in RAID recommendation for Hyper-V host:
I didn't realize enterprise SSDs had come down enough to compete with 15k drives. Interesting.
https://www.neweggbusiness.com/product/product.aspx?item=9b-2rc-0034-000b7 = $0.53 per GB. It is still more, but the value can be justified, imo.
-
If going with Dell, Xbyte has
https://i.imgur.com/RkmYKlF.png
So you'd need 4 in RAID 10 to get enough storage for your situation. 960 GB is the largest drives I see on Xbyte when sorting by the R730.
-
@i3 said in RAID recommendation for Hyper-V host:
Our ERP data size is around 400GB and our file server data size is around 700GB.
...
Should I add more drives to the second array or create a third array with less expensive drives since our file server doesn't require 15k drives.
Couple approaches here that tend to make sense. Here are the two that I would consider most strongly:
-
Single array. Use 10K drives and a lot of them. Six 10K drives is the same speed as four 15K drives. So use eight or more here, get more speed for everything. The OS, the data, the DB all on a single array. More speed for everything.
-
Split array. Use NS-SAS or 7200 RPM SATA drives for the OS and the file server data. Use RAID 1 SSDs for the database.
-
-
@wrx7m said in RAID recommendation for Hyper-V host:
I didn't realize enterprise SSDs had come down enough to compete with 15k drives. Interesting.
Have for a while. The trick is compare by IOPS rather than by capacity.
-
@scottalanmiller said in RAID recommendation for Hyper-V host:
@wrx7m said in RAID recommendation for Hyper-V host:
I didn't realize enterprise SSDs had come down enough to compete with 15k drives. Interesting.
Have for a while. The trick is compare by IOPS rather than by capacity.
But it's exactly that, a trick. It's all about making numbers do whatever you want them to do.
-
Xbyte had 15K drives at
https://i.imgur.com/44OL5yh.pngSo at the high end, assuming 6 drives, you're looking at $2094 vs $4196 for SSD
Of course, the SSD is going to swim circles around those other drives performance wise.
-
@i3 said in RAID recommendation for Hyper-V host:
We are looking to purchase a Hyper-V host to consolidate a few of our physical servers. The two main servers would be our file server and an ERP system. The ERP system is supported on Hyper-V, however their recommended RAID is as follows:
Two drive Raid 1 for the OS
min. 4 drive Raid 1+0 for the data array (15k SAS)Our ERP data size is around 400GB and our file server data size is around 700GB.
My thoughts were to put the virtual machines OS' on the two drive raid 1 array and the data drives for both our ERP and file server on the second array. At are current data usage, (4) 600GB 15k SAS drives would not be leaving us much more room for growth.
Should I add more drives to the second array or create a third array with less expensive drives since our file server doesn't require 15k drives.Thanks,
GDo you know your IOPs usage? What is the drive array configuration of your ERP currently? We can do some real rough calculations based on that (type of drive, RPM, number of drives in each array, etc).
-
@Dashrender said in RAID recommendation for Hyper-V host:
@scottalanmiller said in RAID recommendation for Hyper-V host:
@wrx7m said in RAID recommendation for Hyper-V host:
I didn't realize enterprise SSDs had come down enough to compete with 15k drives. Interesting.
Have for a while. The trick is compare by IOPS rather than by capacity.
But it's exactly that, a trick. It's all about making numbers do whatever you want them to do.
It's not a trick at all in that sense. No more than using capacity as the sole gauge of storage value is a trick. It's like cars, sometimes you are shopping for speed, sometimes for capacity. If we only shopped for speed we'd only buy F1 cars. If we only shopped for capacity we'd only buy minivans. Everyone with something that isn't one of those two blended their needs.
