Back to Contents Page
Dell OpenManage Array Manager User's Guide Version 3.6
What Is RAID?
Organizing Data Storage for Availability and Performance
Choosing RAID Levels and Concatenation
Comparing RAID Level Performance
Array Manager provides storage management using RAID (Redundant Array of Independent Disks) technology. Understanding storage management requires an understanding of RAID concepts, as well as some familiarity with how your system's RAID controllers and operating system view disk space.
RAID (Redundant Array of Independent Disks) is a technology for managing how data is stored on the physical or hard disks that reside in your system or are attached to it. A key aspect of RAID is the ability to span hard disks so that the combined capacity of multiple disks can be treated as a single, extended chunk of disk space. Another key aspect of RAID is the ability to maintain redundant data which can be used to restore data onto a disk in the event of a disk failure. RAID uses different techniques, such as striping, mirroring, and parity, to store and reconstruct data. There are different RAID levels that use different methods for storing and reconstructing data. The RAID levels have different characteristics in terms of read/write performance, data protection, and storage capacity. Not all RAID levels maintain redundant data, which means for some RAID levels lost data cannot be restored. Which RAID level you choose depends on whether your priority is performance, protection, or storage capacity.
 |
Note The RAID Advisory Board (RAB) defines the specifications used to implement
RAID. Although the RAID Advisory Board (RAB) defines the RAID levels,
commercial implementation of RAID levels by different vendors may vary from the
actual RAID specifications. An implementation used by a particular vendor may
affect the read and write performance and the degree of data redundancy.
|
RAID can be implemented with either hardware or software. A system using hardware RAID has a RAID controller that implements the RAID levels and processes data reads and writes to the array disks. When using software RAID, the operating system must implement the RAID levels. For this reason, using software RAID by itself can slow system performance. You can, however, use software RAID on top of hardware RAID volumes to provide greater performance and variety in the configuration of RAID volumes. For example, you can mirror a pair of hardware RAID-5 volumes across two RAID controllers to provide RAID controller redundancy.
 |
Note Careful consideration should be given to a decision between hardware RAID and
software RAID. Software RAID generally has lower performance; and when it is
used with SAN Fibre Channel storage, the volumes cannot be moved from server to
server.
|
RAID uses particular techniques for writing data to disks. These techniques enable RAID to provide data redundancy or better performance. These techniques include:
- Mirroring Duplicating data from one disk to another disk. Mirroring provides data redundancy by maintaining two copies of the same data on different disks. If one of the disks in the mirror fails, the system can continue to operate using the unaffected disk. Both sides of the mirror contain the same data at all times. Either drive can act as the operational drive. A mirrored RAID group is comparable in performance to a RAID-5 group in read operations but faster in write operations.
- Striping Disk striping writes data across several disks. Typically, each "stripe" spans 3 or more disks but only consumes a portion of each disk. Each disk, therefore, may have several stripes. The amount of space consumed by a stripe is the same on each disk included in the stripe. The portion of a stripe that resides on a single disk is a "strip" or "chunk." Striping by itself does not provide data redundancy. Striping in combination with parity does provide data redundancy.
- Stripe size or stripe depth The amount of space that each stripe consumes on a single disk.
- Parity Parity refers to redundant data that is maintained using an algorithm in combination with striping. When one of the striped disks fails, the data can be reconstructed from the parity information using the algorithm.
- Spanning or Concatenation Although concatenation is not considered a RAID level, Array Manager enables you to concatenate (or span) multiple disks so that the combined disk space can be treated as a single, large disk. RAID levels that use striping also employ the concept of spanning, since each stripe uses space from multiple disks. Spanned disks can also be mirrored.
- Consistency Check Verifies the accuracy of redundant data in a RAID group. For example, in a system with parity, checking consistency computes the parity of the data drives and compares the results with the contents of the parity drive.
- Hot Spare An extra, unused disk drive that is part of an array disk subsystem. A hot spare is always in standby mode. If a disk failure occurs, the hot spare replaces the failed drive without interrupting the system.
- Disk Rebuild A rebuild is the recreating of data that existed on a drive before it failed. You can rebuild data only in arrays with data redundancy, such as RAID level 1. (See "Choosing RAID Levels and Concatenation" for more information about RAID levels.)
- Hot Swapping A hot swap is the manual replacement of a defective physical disk unit while the computer is still running. When a new drive has been installed, you must issue a command to rebuild the drive. Before removing a drive, be sure to follow the steps required to remove the drive safely and avoid possible data loss. To remove a drive from a PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controller see "Offline Array Disk" and "Replacing a Failed Disk." To remove a disk from a PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controller, see "Prepare to Remove." To remove a disk from a PV660F storage system, see "Prepare to Remove."
- Fault Tolerance Includes features like automatic failed drive detection, rebuild, and hot swapping.
Each RAID level uses some combination of mirroring, striping, and parity to provide data redundancy or improved read and write performance. For specific information on each RAID level, see "Choosing RAID Levels and Concatenation."
RAID provides different methods or RAID levels for organizing the disk storage. Some RAID levels maintain redundant data so that you can restore data after a disk failure. Different RAID levels may also entail an increase or decrease in the system's I/O (read and write) performance.
Maintaining redundant data requires the use of additional array disks. As more disks become involved, the likelihood of a disk failure increases. Because of the differences in I/O performance and redundancy, one RAID level may be more appropriate than another based on the applications in the operating environment and the nature of the data being stored.
When choosing concatenation or a RAID level, the following performance and cost considerations apply:
- Availability or fault-tolerance. Availability or fault-tolerance refers to a system's ability to maintain operations and provide access to data even when one of its components has failed. In RAID volumes, availability or fault-tolerance is achieved by maintaining redundant data. Redundant data includes mirrors (duplicate data) and parity information (reconstructing data using an algorithm).
- Performance. Read and write performance can be increased or decreased depending on the RAID level you choose. Some RAID levels may be more appropriate for particular applications.
- Cost efficiency. Maintaining the redundant data or parity information associated with RAID volumes requires additional disk space. In situations where the data is temporary, easily reproduced, or non-essential, the increased cost of data redundancy may not be justified.
- Mean Time Between Failure (MTBF). Using additional disks to maintain data redundancy also increases the chance of disk failure at any given moment. Although this cannot be avoided in situations where redundant data is a requirement, it does have implications for the workload of your organization's system support staff.
For more information, see "Choosing RAID Levels and Concatenation."
You can use RAID or concatenation to control data storage on multiple disks. Each RAID level or concatenation has different performance and data protection characteristics.
The following sections provide specific information on how each RAID level or concatenation store data as well as their performance and protection characteristics.
In Array Manager, concatenation refers to storing data on either one array disk or on disk space that spans multiple array disks. When spanning more than one disk, concatenation enables the operating system to view multiple array disks as a single disk.
Data stored on a single disk can be considered a simple volume. This disk could also be defined as a virtual disk that comprises only a single array disk. Data that spans more than one array disk can be considered a spanned volume. Multiple concatenated disks can also be defined as a virtual disk that comprises more than one array disk.
In Array Manager, a dynamic volume that spans to separate areas of the same disk is also considered concatenated.
When an array disk in a concatenated or spanned volume fails, the entire volume becomes unavailable. Because the data is not redundant, it cannot be restored by rebuilding from a mirrored disk or parity information. Restoring from a backup is the only option.
Because concatenated volumes do not use disk space to maintain redundant data, they are more cost-efficient than volumes that use mirrors or parity information. A concatenated volume may be a good choice for data that is temporary, easily reproduced, or that does not justify the cost of data redundancy.
Concatenating Disks
- Concatenates n disks as one large virtual disk with a capacity of n disks.
- Data fills up the first disk before it is written to the second disk.
- No redundancy data is kept. When a disk fails, the large virtual disk fails.
- No performance gain.
- No redundancy.
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
RAID 0 uses data striping, which is writing data in equal-sized segments across the array disks. RAID 0 does not provide data redundancy.
Striping Disks
- Groups n disks as one large virtual disk with a capacity of n disks.
- Data is stored to the disks alternately.
- No redundancy data is kept. When a disk fails, the large virtual disk fails with no means of rebuilding the data.
- Better read and write performance.
 |
Note The PERC 2/DC and PERC 2/SC controllers are limited to eight drives when using
RAID 0, or RAID 5.
|
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch and CERC SATA1.5/2s controllers, see the following:
RAID 1 is the simplest form of maintaining redundant data. In RAID 1, data is mirrored or duplicated on one or more drives. If one drive fails, then the data can be rebuilt using the mirror.
Mirroring Disks
- Groups n + n disks as one virtual disk with the capacity of n disks. The controllers currently supported by Array Manager allow the selection of two disks when creating a RAID 1. Because these disks are mirrored, the total storage capacity is equal to one disk.
- Data is replicated on the two disks.
- When a disk fails, the virtual disk still works. The data will be read from the failed disk's mirror.
- Better read performance, but slightly slower write performance.
- Redundancy for protection of data.
- RAID 1 is more "expensive" in terms of disk space since twice the number of disks are used than required to store the data without redundancy.
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
RAID 5 provides data redundancy by using data striping in combination with parity information. Rather than having all parity information reside on a single drive, the parity information is striped across all disks in the array.
Striping Disks with Distributed Parity Drive
- Groups n disks as one large virtual disk with a capacity of (n-1) disks.
- Redundant information (parity) is alternately stored on all disks.
- When a disk fails, the virtual disk still works, but it is operating in a degraded state. The data is reconstructed from the surviving disks.
- Better read performance, but slower write performance.
- Redundancy for protection of data.
 |
Note The PERC 2/DC and PERC 2/SC controllers are limited to eight drives when using
RAID 0, or RAID 5.
|
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
RAID 50 is striping across more than one three-drive span. For example, a RAID 5 array that is implemented with three drives and then continues on with three more array drives would be a RAID 50 array.
It is possible to implement RAID 50 even when the hardware does not directly support it. In this case, you can implement more than one RAID 5 virtual disks and then convert the RAID 5 disks to dynamic disks. You can then create a dynamic volume that is spanned across all RAID 5 virtual disks.
RAID 50
- Groups n*s disks as one large virtual disk with a capacity of s*(n-1) disks, where s is the number of spans and n is the number of disks within each span.
- Redundant information (parity) is alternately stored on all disks of each RAID 5 span.
- Better read performance, but slower write performance.
- Requires proportionally as much parity information as standard RAID 5.
- Data is concatenated across all spans. RAID 50 is more expensive in terms of disk space.
 |
Note On the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di,
4e/Si, 4e/Di, and CERC ATA100/4ch controllers, there are special considerations
when implementing RAID 50 on an array group that has disks of different sizes. See
"Considerations for RAID 10 and 50 on PERC Subsystem 1 Controllers" for more
information.
|
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
The RAID Advisory Board considers RAID Level 10 to be an implementation of RAID level 1. RAID 10 combines mirrored drives (RAID 1) with data striping (RAID 0). With RAID 10, data is striped across multiple drives. The set of striped drives is then mirrored onto another set of drives. RAID 10 can be considered a stripe of mirrors.
Striping over mirror sets
- Groups n disks as one large virtual disk with a capacity of (n/2) disks.
- Mirror images of the data are striped across sets of disk drives. This level provides redundancy through mirroring.
- When a disk fails, the virtual disk is still functional. The data will be read from the surviving mirrored disk.
- Improved read performance and write performance.
- Redundancy for protection of data.
 |
Note On the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di,
4e/Si, 4e/Di, and CERC ATA100/4ch controllers, there are special considerations
when implementing RAID 10 on an array group that has disks of different sizes. See
"Considerations for RAID 10 and 50 on PERC Subsystem 1 Controllers" for more
information.
|
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
RAID-1 Concatenated is a RAID-1 array that spans across more than a single pair of array disks. This combines the advantages of concatenation with the redundancy of RAID-1. No striping is involved in this RAID type.
Also, RAID-1 Concatenated can be implemented on hardware that supports only RAID-1 by creating multiple RAID-1 virtual disks, upgrading the virtual disks to dynamic disks, and then using spanning to concatenate all of the RAID-1 virtual disks into one large dynamic volume.
RAID 1-Concatenated
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
The RAID Advisory Board considers RAID Level 0+1 to be an implementation of RAID level 1. RAID 0+1 combines data striping (RAID 0) with mirrored drives (RAID 1). With RAID 0+1, data is striped across multiple drives and their mirrors. RAID 0+1 can be considered a mirror of stripes.
Mirroring Over Stripe Sets
 |
Note In Array Manager, RAID 0+1 is only used with the PowerVault 660F storage system.
This RAID level also allows you to use an odd number of disks.
|
- Groups n disks as one large virtual disk with a capacity of (n/2) disks.
- Mirror images of the data are striped across sets of disk drives. This level provides redundancy through mirroring.
- When a disk fails, the virtual disk is still functional. The data will be read from the surviving mirrored data stripes.
- Improved read performance and write performance.
- Redundancy for protection of data.
- For an overview of storage availability and performance considerations, see "Organizing Data Storage for Availability and Performance."
- For the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, see the following:
- For the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, see the following:
On the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, there are special considerations when implementing RAID 10 or RAID 50 on an array group that has disks of different sizes. When implementing RAID 10 or RAID 50, disk space is spanned to create the stripes and mirrors. The span size can vary to accommodate the different disk sizes. There is, however, the possibility that a portion of the largest disk in the array will be unusable, resulting in wasted disk space. For example, consider an array that has the following disks:
Disk A = 40 GB
Disk B = 40 GB
Disk C = 60 GB
Disk D = 80 GB
In this example, data will be spanned across all four disks until Disk A and Disk B and 40 GB on each of Disk C and D are completely full. Data will then be spanned across Disks C and D until Disk C is full. This leaves 20 GB of disk space remaining on Disk D. Data cannot be written to this disk space, as there is no corresponding disk space available in the array to create redundant data.
The following table compares the performance characteristics associated with the more common RAID levels. This table provides general guidelines for choosing a RAID level. Keep in mind the needs of your particular environment when choosing a RAID level.
RAID Level Performance Comparison
|
RAID Level
|
Data Availability
|
Read Performance
|
Write Performance
|
Rebuild Performance
|
Minimum Disks Required
|
Suggested Uses
|
RAID 0 | None | Very Good | Very Good | N/A | N | Noncritical data |
RAID 1 | Excellent | Very Good | Good | Good | 2N (N = 1) | Small databases, database logs, critical information |
RAID 5 | Good | Sequential reads: good. Transactional reads: Very good | Fair, unless using write-back cache | Poor | N + 1 (N = at least two disks) | Databases and other read-intensive transactional uses |
RAID 10 | Excellent | Very Good | Fair | Good | 2N x X | Data-intensive environments (large records) |
RAID 50 | Excellent | Very Good | Fair | Fair | N + 2 (N = at least 4) | Medium-sized transactional or data-intensive uses |
|
N = Number of array disks X = Number of RAID sets
|
Back to Contents Page