HPE MSA 2052 "virtual storage?"

[kehilbatu]

Need some clarify from what I'm reading in the documentation. It seems data is stored across all disk groups in a virtual pool. Meaning, If I built one RAID 1 disk group, and another RAID 5 disk group with the intention of splitting SQL transaction logs from the database, this would give me no benefit as I don't have control where the files are actually stored on the hardware?

[sbhat09]

Hello @kehilbatu,

You are correct. Data on the same volume may not be split (database and logs) in controlled manner between the 2 disk groups. The purpose of virtual pool is to move the data between the disk groups based on the amount of data reads.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[support_s]

System recommended content:

1. HPE MSA 2052 SAN Storage

2. HPE MSA 1060/2060/2062 Storage Management Guide

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[SUBHAJIT KHANBARMAN_1]

@kehilbatu 

I would suggest you to go through the best practices white paper.

https://www.hpe.com/psnow/doc/a00015961enw?jumpid=in_lit-psnow-red

Please refer page no 18 and see this,

"Allocated pages are evenly distributed among disk groups in a tier; therefore, create all disk groups in a tier with the same RAID type and number of drives to ensure uniform performance in the tier.

Consider an example where the first disk group in the standard tier consists of five 15K enterprise SAS drives in a RAID 5 configuration. To ensure consistent performance in the tier, any additional disk groups for the standard tier should also be a RAID 5 configuration. Adding a new disk group configured with four 10K enterprise SAS drives in a RAID 6 configuration produces inconsistent performance within the tier because of the different characteristics of the disk groups.

For optimal write sequential performance, parity-based disk groups (RAID 5 and RAID 6) should be created with “the power of 2” method. This method means that the number of data drives (nonparity) contained in a disk group should be a power of 2."

Now if you have different drive types to create different VDGs, then also Automated Tiering will take care.

If you want to define things at the Volume level then got for Volume Tier Affinity feature.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

*************************************************************************

[JonPaul]

Don't forget about the Virtual Storage Technical Reference Guide
https://www.hpe.com/psnow/doc/a00087404enw