Table of Contents
Advertisement
In general, each storage object included in the RAID should be from a different physical disk to
maximize I/O performance and to achieve disk fault tolerance where supported by the RAID level
you use. In addition, they should be of the same type (disks, segments, or regions).
Using component devices of differing speeds might introduce a bottleneck during periods of
demanding I/O. The best performance can be achieved by using the same brand and models of disks
and controllers in your hardware solution. If they are different, you should try to match disks and
controllers with similar technologies, performance, and capacity. Use a low number of drives on
each controller to maximize throughput.
IMPORTANT: As with any hardware solution, using the same brand and model introduces the risk
of concurrent failures over the life of the product, so plan maintenance accordingly.
The following table provides recommendations for the minimum and maximum number of storage
objects to use when creating a software RAID:
Recommended Number of Storage Objects to Use in the Software RAID
Table 6-6
RAID Type
RAID 0 (striping)
RAID 1 (mirroring)
RAID 4 (striping with dedicated parity)
RAID 5 (striping with distributed parity)
Connection fault tolerance can be achieved by having multiple connection paths to each storage
object in the RAID. For more information about configuring multipath I/O support before
configuring a software RAID, see
6.1.7 RAID 5 Algorithms for Distributing Stripes and Parity
RAID 5 uses an algorithm to determine the layout of stripes and parity. The following table
describes the algorithms.
Minimum Number of
Storage Objects
2
2
3
3
Chapter 5, "Managing Multipath I/O for Devices," on page
Recommended
Maximum Number of
Storage Objects
8
4
8
8
41.
Managing Software RAIDs with EVMS
57
Advertisement
Chapters
Table of Contents
