193 lines
18 KiB
HTML
193 lines
18 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||
|
|
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||
|
|
<title>Available RAID Configurations</title>
|
||
|
|
<link rel="StyleSheet" href="css/3ware_Intro.css" type="text/css" media="all" />
|
||
|
|
<link rel="StyleSheet" href="css/webworks.css" type="text/css" media="all" />
|
||
|
|
<script type="text/javascript" language="JavaScript1.2" src="scripts/expand.js"></script>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2" src="scripts/seealso.js"></script>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">
|
||
|
|
<!--
|
||
|
|
var WebWorksRootPath = "";
|
||
|
|
// -->
|
||
|
|
</script>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">
|
||
|
|
<!--
|
||
|
|
var WebWorksSeeAlso = "xxx";
|
||
|
|
// -->
|
||
|
|
</script>
|
||
|
|
</head>
|
||
|
|
<body style="">
|
||
|
|
<table align="right">
|
||
|
|
<tr>
|
||
|
|
<td style="text-align: left;">
|
||
|
|
<a href="http://www.lsi.com/channel/products" target="_blank">
|
||
|
|
<img src="LSI-logo.jpg" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<div style="text-align: left;">
|
||
|
|
<p style="color: Navy; font-weight:bold">3DM2™ Online
|
||
|
|
Help</p>
|
||
|
|
<table cellspacing="0">
|
||
|
|
<tr>
|
||
|
|
<td>
|
||
|
|
<a href="toc.html">
|
||
|
|
<img src="images/toc.gif" alt="Table of Contents" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
<td>
|
||
|
|
<a href="3ware_Intro.2.6.html">
|
||
|
|
<img src="images/prev.gif" alt="Previous" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
<td>
|
||
|
|
<a href="3ware_Intro.2.8.html">
|
||
|
|
<img src="images/next.gif" alt="Next" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
<td>
|
||
|
|
<a href="ix.html">
|
||
|
|
<img src="images/index.gif" alt="Index" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<br clear="all" />
|
||
|
|
<br />
|
||
|
|
<div class="WebWorks_Breadcrumbs" style="text-align: left;">
|
||
|
|
<a class="WebWorks_Breadcrumb_Link" href="3ware_Intro.2.5.html#1584812">Understanding RAID Concepts and Levels</a> > RAID Concepts > Available RAID Configurations</div>
|
||
|
|
<hr align="left" />
|
||
|
|
<div>
|
||
|
|
<div class="Heading2"><a name="1584812">Available RAID Configurations</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584813">RAID is a method of combining several hard drives into one unit. It can offer </a>fault tolerance and higher throughput levels than a single hard drive or group of independent hard drives. The following information explains the different RAID levels.</div>
|
||
|
|
<div class="Body"><a name="1587920">The following RAID levels and configurations are available for drives </a>attached to a 3ware RAID controller: </div>
|
||
|
|
<div class="Heading3"><a name="1584821">RAID 0</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584822">RAID 0 provides improved performance, but no fault tolerance. Because the </a>data is striped across more than one disk, RAID 0 disk arrays achieve high transfer rates because they can read and write data on more than one drive simultaneously. You can configure the stripe size during unit creation. RAID 0 requires a minimum of two drives.</div>
|
||
|
|
<div class="Body"><a name="1584825">When drives are configured in a striped disk array, large files are distributed </a>across the multiple disks using RAID 0 techniques. </div>
|
||
|
|
<div class="Body"><a name="1584827">Striped disk arrays give exceptional performance, particularly for data-</a>intensive applications such as video editing, computer-aided design, and geographical information systems. </div>
|
||
|
|
<div class="Body"><a name="1584828">RAID 0 arrays are not fault tolerant. The loss of any drive results in the loss of </a>all the data in that array, and can even cause a system hang, depending on your operating system. RAID 0 arrays are not recommended for high-availability systems unless you take additional precautions to prevent system hangs and data loss. </div>
|
||
|
|
<div class="Figure" onclick="WebWorks_ToggleDIV(WebWorksRootPath, "wwdd1584830");"><a name="1584830">Show </a>RAID 0 Configuration Example<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteArrow(WebWorksRootPath, "wwdd1584830", false);</script></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVOpen("wwdd1584830", false);</script>
|
||
|
|
<div class="anchor">
|
||
|
|
<span class="Red"> </span><a name="1584834"><img id="1584832" class="Default" src="images/RAID-0.gif" width="250" height="165" style="display: block; float: none; left: 0.0; text-align: left; top: 0.0;" /></a></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVClose();</script>
|
||
|
|
<div class="Heading3"><a name="1584837">RAID 1</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584838">RAID 1 provides fault tolerance and a speed advantage over non-RAID disks. </a>RAID 1 also is known as a mirrored array. Mirroring is done on pairs of drives. Mirrored disk arrays write the same data to two different drives using RAID 1 algorithms. This gives your system fault tolerance by preserving the data on one drive if the other drive fails. Fault tolerance is a basic requirement for critical systems should as web and database servers.</div>
|
||
|
|
<div class="Body"><a name="1584842">3ware firmware uses a patented TwinStor technology, on RAID 1 arrays for </a>improved performance during sequential read operations. With TwinStor technology, read performance during a sequential read operation is twice the speed of a single drive.</div>
|
||
|
|
<div class="Body"><a name="1584843">The adaptive algorithms in TwinStor technology boost performance by </a>distinguishing between random read request and sequential read requests. For the sequential read requests generated when accessing large files, both drives are used with the drive heads simultaneously reading alternating sections of the file. For the smaller random transactions, the data is read by a single optimal drive head. </div>
|
||
|
|
<div class="Figure" onclick="WebWorks_ToggleDIV(WebWorksRootPath, "wwdd1584845");"><a name="1584845">Show </a>RAID 1 Configuration Example<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteArrow(WebWorksRootPath, "wwdd1584845", false);</script></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVOpen("wwdd1584845", false);</script>
|
||
|
|
<div class="anchor">
|
||
|
|
<span class="Red"> </span><a name="1584849"> <img id="1584847" class="Default" src="images/RAID-1.gif" width="198" height="164" style="display: block; float: none; left: 0.0; text-align: left; top: 0.0;" /></a></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVClose();</script>
|
||
|
|
<div class="Heading3"><a name="1584852">RAID 5</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584853">RAID 5 provides performance, fault tolerance, high capacity, and storage </a>efficiency. It requires a minimum of three drives and combines striping data with parity (exclusive OR) to restore data in case of a drive failure. Performance and efficiency increase as the number of drives in a unit increases.</div>
|
||
|
|
<div class="Body"><a name="1584854">Parity information is distributed across all of the drives in a unit rather than </a>being concentrated on a single disk. This method avoids throughput loss due to contention for the parity drive.</div>
|
||
|
|
<div class="Body"><a name="1584858">RAID 5 can tolerate one drive failure in the unit.</a></div>
|
||
|
|
<div class="Figure" onclick="WebWorks_ToggleDIV(WebWorksRootPath, "wwdd1584861");"><a name="1584861">Show </a>RAID 5 Configuration Example<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteArrow(WebWorksRootPath, "wwdd1584861", false);</script></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVOpen("wwdd1584861", false);</script>
|
||
|
|
<div class="anchor">
|
||
|
|
<span class="Red"> </span><a name="1584868"><img id="1584863" class="Default" src="images/RAID5Config_Mac.gif" width="277" height="354" style="display: block; float: none; left: 0.0; text-align: left; top: 0.0;" /></a></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVClose();</script>
|
||
|
|
<div class="Heading3"><a name="1584871">RAID 6</a></div>
|
||
|
|
<div class="Body"><a name="1584873">RAID 6 provides greater redundancy and fault tolerance than RAID 5. It is </a>similar to RAID 5 but, instead of a single block, RAID 6 has two blocks of parity information (P+Q) distributed across all the drives of a unit (see <a href="#1584880">Figure: Show RAID 6 Configuration Example</a>). </div>
|
||
|
|
<div class="Body"><a name="1584877">Due to the two parities, a RAID 6 unit can tolerate two hard drives failing </a>simultaneously. This also means that a RAID 6 unit can be in two different states at the same time. For example, one subunit can be degraded while another is rebuilding, or one subunit can be initializing while another is verifying. </div>
|
||
|
|
<div class="Body"><a name="1584878">The 3ware implementation of RAID 6 requires a minimum of five drives. </a>Performance and storage efficiency also increase as the number of drives increase. </div>
|
||
|
|
<div class="Figure" onclick="WebWorks_ToggleDIV(WebWorksRootPath, "wwdd1584880");"><a name="1584880">Show </a>RAID 6 Configuration Example<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteArrow(WebWorksRootPath, "wwdd1584880", false);</script></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVOpen("wwdd1584880", false);</script>
|
||
|
|
<div class="fig-anchor">
|
||
|
|
<span class="Red"> </span><a name="1584886"><img id="1584882" class="Default" src="images/RAID6Config.gif" width="348" height="472" style="display: block; float: none; left: 0.0; text-align: left; top: 0.0;" /></a></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVClose();</script>
|
||
|
|
<div class="Heading3"><a name="1584891">RAID 10</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584892">RAID 10 is a combination of striped and mirrored arrays for fault tolerance </a>and high performance.</div>
|
||
|
|
<div class="Body"><a name="1584893">When drives are configured as a striped mirrored array, the disks are </a>configured using both RAID 0 and RAID 1 techniques. A minimum of four drives are required to use this technique. The first two drives are mirrored as a fault-tolerant array using RAID 1. The third and fourth drives are mirrored as a second fault-tolerant array using RAID 1. The two mirrored arrays are then grouped as a striped RAID 0 array using a two-tier structure. Higher data transfer rates are achieved by leveraging TwinStor technology and striping the arrays. </div>
|
||
|
|
<div class="Body"><a name="1584897">In addition, RAID 10 arrays offer a higher degree of fault tolerance than </a>RAID 1 and RAID 5 because the array can sustain multiple drive failures without data loss. For example, in a 12-drive RAID 10 array, up to 6 drives can fail (half of each mirrored pair) and the array continues to function. Note that if both halves of a mirrored pair in the RAID 10 array fail, all of the data is lost.</div>
|
||
|
|
<div class="Figure" onclick="WebWorks_ToggleDIV(WebWorksRootPath, "wwdd1584899");"><a name="1584899">Show </a>RAID 10 Configuration Example<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteArrow(WebWorksRootPath, "wwdd1584899", false);</script></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVOpen("wwdd1584899", false);</script>
|
||
|
|
<div class="anchor">
|
||
|
|
<span class="Red"> </span><a name="1584903"><img id="1584901" class="Default" src="images/RAID-10.gif" width="371" height="312" style="display: block; float: none; left: 0.0; text-align: left; top: 0.0;" /></a></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVClose();</script>
|
||
|
|
<div class="Heading3"><a name="1584906">RAID 50</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584907">RAID 50 is a combination of RAID 5 and RAID 0. This array type provides </a>fault tolerance and high performance. RAID 50 requires a minimum of six drives.</div>
|
||
|
|
<div class="Body"><a name="1584908">Several combinations are available with RAID 50. For example, on a 12-port </a>controller, you can have a grouping of three, four, or six drives. A grouping of three means that the RAID 5 arrays used have three disks each; four of these 3-drive RAID 5 arrays are striped together to form the 12-drive RAID 50 array. On a 16-port controller, you can have a grouping of four or eight drives.</div>
|
||
|
|
<div class="Body"><a name="1584909">No more than four RAID 5 subunits are allowed in a RAID 50 unit. For </a>example, a 24-drive RAID 50 unit may have groups of 12, eight, or six drives, but not groups of four or three (see <a href="#1584915">Figure: Show RAID 50 Configuration Example</a>). </div>
|
||
|
|
<div class="Body"><a name="1584913">In addition, RAID 50 arrays offer a higher degree of fault tolerance than </a>RAID 1 and RAID 5, because the array can sustain multiple drive failures without data loss. For example, in a 12-drive RAID 50 array, one drive in each RAID 5 set can fail and the array continues to function. Note that if two or more drives in a RAID 5 set fail, all of the data is lost.</div>
|
||
|
|
<div class="Figure" onclick="WebWorks_ToggleDIV(WebWorksRootPath, "wwdd1584915");"><a name="1584915">Show </a>RAID 50 Configuration Example<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteArrow(WebWorksRootPath, "wwdd1584915", false);</script></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVOpen("wwdd1584915", false);</script>
|
||
|
|
<div class="anchor">
|
||
|
|
<span class="Red"> </span><a name="1584926"><img id="1584917" class="Default" src="images/RAID50Config.gif" width="794" height="535" style="display: inline; float: none; left: 0.0; text-align: left; top: 0.0;" /></a></div>
|
||
|
|
<script type="text/javascript" language="JavaScript1.2">WebWorks_WriteDIVClose();</script>
|
||
|
|
<div class="Heading3"><a name="1584929">Single Disk</a></div>
|
||
|
|
<div class="Body"><a name="1584930">You can configure a single drive as a unit through 3ware software. (</a>3BM, 3DM2, or CLI). </div>
|
||
|
|
<div class="Body"><a name="1584931">Similar to disks in other RAID configurations, single disks contain 3ware </a>Disk Control Block (DCB) information and the OS addresses them as available units.</div>
|
||
|
|
<div class="Body"><a name="1584932">Single drives are not fault tolerant and, therefore, are not recommended for </a>high availability systems unless you take additional precautions to prevent system hangs and data loss.</div>
|
||
|
|
<div class="Heading3"><a name="1584935">Hot Spare</a></div>
|
||
|
|
<div class="BodyAfterHead"><a name="1584936">A hot spare is a single drive, available online, so that a redundant unit is </a>automatically rebuilt without human intervention in case of drive failure. </div>
|
||
|
|
<hr />
|
||
|
|
<dl>
|
||
|
|
<dt>Related Topics</dt>
|
||
|
|
<dd>
|
||
|
|
<div class="RelatedTopic"><a href="3ware_Intro.2.6.html#1584775" name="1587973">RAID Concepts</a></div>
|
||
|
|
</dd>
|
||
|
|
<dd>
|
||
|
|
<div class="RelatedTopic"><a href="3ware_Intro.2.8.html#1584955" name="1587977">Determining Which RAID Level to Use</a></div>
|
||
|
|
</dd>
|
||
|
|
<dd>
|
||
|
|
<div class="RelatedTopic"><a href="GetStart.html#1103258" name="1587981">Getting Started with Your 3ware RAID Controller</a></div>
|
||
|
|
</dd>
|
||
|
|
<dd>
|
||
|
|
<div class="RelatedTopic"><a href="Config_Units.6.1.html#1062869" name="1587985">Configuring Units</a></div>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<hr align="left" />
|
||
|
|
<div style="text-align: left;">
|
||
|
|
<table cellspacing="0">
|
||
|
|
<tr>
|
||
|
|
<td>
|
||
|
|
<a href="toc.html">
|
||
|
|
<img src="images/toc.gif" alt="Table of Contents" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
<td>
|
||
|
|
<a href="3ware_Intro.2.6.html">
|
||
|
|
<img src="images/prev.gif" alt="Previous" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
<td>
|
||
|
|
<a href="3ware_Intro.2.8.html">
|
||
|
|
<img src="images/next.gif" alt="Next" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
<td>
|
||
|
|
<a href="ix.html">
|
||
|
|
<img src="images/index.gif" alt="Index" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<table align="right">
|
||
|
|
<tr>
|
||
|
|
<td style="text-align: left;">
|
||
|
|
<a href="http://www.lsi.com/channel/products" target="_blank">
|
||
|
|
<img src="LSI-logo.jpg" border="0" />
|
||
|
|
</a>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td style="text-align: left; font-size: 16px ; font-weight: bold">
|
||
|
|
<a href="http://www.lsi.com/channel/products" target="_blank">LSI Corporation</a>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p style="font-size: .8em">Copyright LSI 2004-2010<br />
|
||
|
|
To contact Support, go to <a href="http://www.lsi.com/channel/ContactUs">http://www.lsi.com/channel/ContactUs</a></p>
|
||
|
|
</body>
|
||
|
|
</html>
|