DL380 G6 and RAID performance

[marcus1234]

the os should be on mirror, why easier to manage

if OS and data is on same array,and oS fails predictive or otherwise has domino effect on rest of the logical array ......


raid 5 for the rest witha hot spare assigned when you create the arrray ,

special note if you add a hot spare after the raids are created , some times it is not "really hot" and the server needs a reboot to initiate it , which means if you are not present to reboot, the system will be really slow for that time and run in degraded status painfully sloooow...

also ensure you have 512 cache and battery too on controller it makes a big performance differance

you can set read write cache in HP ACU array config utility so reads or writes can be set faster, this is a dynamic option so server does not require restarts etc..
this is set within the os

IN ACU array config utility you can also set rebuild priority,its just in case a disk fails default is medium priority, high makes it slow for users that are logged on so should be used in none production hours...

tip before going in production pull a disk to check the hot one jumps in and have the rebuild priority to high , this will check cache and the battery on controller too..


have fun points appreciated :)

[marcus1234]

forgot to mention each array on its own channel , much better performance,
especially,
when a disk rebuid is in progress or if a disk is having a predictive failture, and re.. requesting , read writes

[Tim Nelson]

my 2 cents.

If you are really concerned about performance then migrate to a san based storage array.

You are only going to get so much out of an internal sas controller using 300GB drives.

If you are stuck with what you have then a mirrored pair for the host OS. and raid5 the rest to present to your VMs.

Again, you are limited to what you are going to get out of this configuration.