91 lines
5.2 KiB
HTML
91 lines
5.2 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="Write cache and auxiliary write cache IOA" />
|
|||
|
<meta name="DC.Relation" scheme="URI" content="rzalydppprf.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="cache" />
|
|||
|
<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>Write cache and auxiliary write cache IOA </title>
|
|||
|
</head>
|
|||
|
<body id="cache"><a name="cache"><!-- --></a>
|
|||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
<h1 class="topictitle1">Write cache and auxiliary write cache IOA </h1>
|
|||
|
<div><div class="section"><h4 class="sectiontitle">Write cache</h4>The write cache provides greater data integrity
|
|||
|
and improved performance. When the iSeries(TM) server sends a write operation,
|
|||
|
the data is written to the cache. Then, a write-completion message is sent
|
|||
|
back to the server. Later, the data is written to the disk. The cache provides
|
|||
|
a faster write capability and ensures data integrity.<p>The following actions
|
|||
|
occur during a write request from the server:</p>
|
|||
|
<ol><li>Data is committed to a nonvolatile battery-backed cache in the IOA.</li>
|
|||
|
<li>A write completion message is sent from the server.</li>
|
|||
|
<li>The following actions occur after the write completion message is sent.<ol type="a"><li>A write operation is sent from the IOA cache to the disk unit:<ul><li>A write operation is sent from the IOA cache to the disk unit:<ul><li>Reads the original data.</li>
|
|||
|
<li>Calculates delta parity by comparing new and original data.</li>
|
|||
|
<li>Writes the new data.</li>
|
|||
|
</ul>
|
|||
|
</li>
|
|||
|
<li>Write operations for parity data:<ul><li>Reads the original parity information.</li>
|
|||
|
<li>Calculates the new parity by comparing the delta parity and the original
|
|||
|
parity.</li>
|
|||
|
<li>Writes the new parity information.</li>
|
|||
|
</ul>
|
|||
|
</li>
|
|||
|
</ul>
|
|||
|
</li>
|
|||
|
<li>Data is marked as committed data when it is successfully written to both
|
|||
|
the data disk unit and the parity disk unit.</li>
|
|||
|
</ol>
|
|||
|
</li>
|
|||
|
</ol>
|
|||
|
<p>The performance for this type of write operation is dependent on disk
|
|||
|
contention and the time that is needed to calculate the parity information.</p>
|
|||
|
</div>
|
|||
|
<div class="section"><h4 class="sectiontitle">Auxiliary cache IOA</h4>The auxiliary cache
|
|||
|
IOA mirrors the write cache on a storage IOA. Protection is enhanced because
|
|||
|
two copies of data are stored onto two separate IOAs. If a failure occurs
|
|||
|
to the write cache, then the auxiliary cache IOA serves as a back up during
|
|||
|
the recovery of the failed IOA.<p>When an iSeries(TM) server sends a write
|
|||
|
operation, the data is written to the write cache on the storage IOA. The
|
|||
|
storage IOA mirrors the write cache data to the auxiliary write cache IOA.
|
|||
|
Then, a write-completion message is sent back to the server and the data is
|
|||
|
then written to a disk.</p>
|
|||
|
<div class="note"><span class="notetitle">Note:</span> In order for write cache mirroring to occur,
|
|||
|
the storage IOAs connected to supported auxiliary write cache IOA. The storage
|
|||
|
IOA and the auxiliary write cache IOA must also be in the same enclosure and
|
|||
|
under the same partition.</div>
|
|||
|
<p id="cache__acinfo"><a name="cache__acinfo"><!-- --></a>The auxiliary write cache is
|
|||
|
an additional IOA that has a one-to-one relationship with a disk IOA. The
|
|||
|
auxiliary write cache protects against extended outages due to the failure
|
|||
|
of a disk IOA or its cache by providing a copy of the write cache which can
|
|||
|
be recovered following the repair of the disk IOA. This avoids a potential
|
|||
|
system reload and gets the system back on line as soon as the disk IOA is
|
|||
|
replaced and the recovery procedure completes. Note, however, that this IOA
|
|||
|
is not a failover device that can keep the system operational if the disk
|
|||
|
IOA, or it’s cache, fails.</p>
|
|||
|
<p>For more information about auxiliary write
|
|||
|
cache see the <a href="http://www.redbooks.ibm.com/redpapers/abstracts/redp4003.html" target="_blank">Planning for IBM<sup>®</sup> i5 Data Protection with Auxiliary Write
|
|||
|
Cache Solutions</a> redbook.</p>
|
|||
|
</div>
|
|||
|
</div>
|
|||
|
<div>
|
|||
|
<div class="familylinks">
|
|||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalydppprf.htm">How device parity protection affects performance</a></div>
|
|||
|
</div>
|
|||
|
</div>
|
|||
|
</body>
|
|||
|
</html>
|