89 lines
5.3 KiB
HTML
89 lines
5.3 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 lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="topic" />
|
||
|
<meta name="DC.Title" content="Change parity set optimization" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzalydpy.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzalychgdpy" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Change parity set optimization</title>
|
||
|
</head>
|
||
|
<body id="rzalychgdpy"><a name="rzalychgdpy"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Change parity set optimization</h1>
|
||
|
<div><p>If you use a V5R2 input/output adapter (IOA) and OS/400<sup>®</sup> V5R2 or later, you can now choose
|
||
|
how you want your parity sets to be optimized. When you select to optimize
|
||
|
a parity set, the I/O adapter will choose disk units for parity sets according
|
||
|
to the optimization value you have chosen. Depending on your configuration,
|
||
|
different parity set optimizations might generate the same parity sets. You
|
||
|
have several options for parity set optimization:</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalydpy.htm">Work with device parity protection</a></div>
|
||
|
</div>
|
||
|
</div><div class="nested1" xml:lang="en-us" id="abailability"><a name="abailability"><!-- --></a><h2 class="topictitle2">Availability</h2>
|
||
|
<div><p>A parity set optimized for availability offers a greater level of protection
|
||
|
because it allows a parity set to remain functional in the event of a I/O
|
||
|
bus failure. The availability optimization value ensures that a parity set
|
||
|
is formed from at least three disk units of equal capacity each attached to
|
||
|
a separate bus on the input/output adapter (IOA). For example, if an I/O adapter
|
||
|
had 15 disk units and was optimized for availability, the result might be
|
||
|
five parity sets with three disk units each attached to separate I/O buses
|
||
|
on the adapter. OS/400 V5R3
|
||
|
is required to optimize for availability.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="capacity"><a name="capacity"><!-- --></a><h2 class="topictitle2">Capacity</h2>
|
||
|
<div><p>A parity set optimized for capacity stores the most data possible. The
|
||
|
I/O adapter may generate fewer parity sets with more disk units in each parity
|
||
|
set. For example, if an I/O adapter has 15 disk units and is optimized for
|
||
|
capacity, the result might be one parity set containing 15 disk units. </p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="balanced"><a name="balanced"><!-- --></a><h2 class="topictitle2">Balanced</h2>
|
||
|
<div><p>A balanced parity set compromises between the ability to store large amounts
|
||
|
of data and also provide fast access to data. For example, if an I/O adapter
|
||
|
has 15 disk units and you choose balanced parity optimization, the result
|
||
|
might be two parity sets, one with nine disk units and one with six disk units.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="performance"><a name="performance"><!-- --></a><h2 class="topictitle2">Performance</h2>
|
||
|
<div><p>Parity sets optimized for performance provide the fastest data access.
|
||
|
The I/O adapter may generate more parity sets with fewer numbers of disk units.
|
||
|
For example, if an I/O adapter had 15 disk units and is optimized for performance,
|
||
|
the result might be three parity sets with five disk units each.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="change"><a name="change"><!-- --></a><h2 class="topictitle2">Steps to change parity set optimization</h2>
|
||
|
<div><div class="p">To change the parity set optimization for all new parity sets that are
|
||
|
created, use the following steps. This change stays in effect until you change
|
||
|
it again. If you need to start parity, you can also change the parity set
|
||
|
optimization as part of the start parity process.<ol><li> Expand <span class="uicontrol">Disk Units.</span></li>
|
||
|
<li> Right-click <span class="uicontrol">Parity Sets</span> and select <span class="uicontrol">Change
|
||
|
Optimization</span>.</li>
|
||
|
</ol>
|
||
|
</div>
|
||
|
<div class="note"><span class="notetitle">Note:</span> RAID 6 protection gives you optimal performance, capacity,
|
||
|
and balance, so selecting any of the parity set optimizations does not affect
|
||
|
the outcome of the parity set.</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
</html>
|