Quantcast
Channel: All MSA Storage posts
Viewing all articles
Browse latest Browse all 8327

Re: MSA 2050

$
0
0

Thanks Shawn for your explanation on the tiering feature. How does the storage software identify which vdisk is faster and which is slower? for e.g. vdisk with 6 SAS disks in RAID10 is faster than 6 disks in RAID5 but may be slower than 10 disks in RAID5.

Is there anyway we can have control over what data is placed (written) where? for e.g. we use the storage for Oracle database. and we procure only SAS disks. So far (in P2000 & 2040) we configure it as follows:

2 disk RAID1 for REDO (odd groups)

2 disk RAID1 for REDO (even groups)

4 disk RAID10 for ARCHIVELOGS

10 disk RAID10 for DATA

We want REDO, DATA & ARCHIVE to be written to separate (physical) disks and that is because we want very low latency. If the volume that stores DATA & REDO goes to the same physical disk, then latency will get affected. Since 2050 volumes are striped across all vdisks of a storage pool, we are not able to achieve what we used to do in P2000 & 2040. Is there anyway to achieve this in 2050? OR, if you agree that our requirement is valid, then should we look at some other storage? Would appreciate your views/comments on this.

Thanks


Viewing all articles
Browse latest Browse all 8327

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>