65 lines
6.2 KiB
HTML
65 lines
6.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="concept" />
|
|
<meta name="DC.Title" content="Journal receiver disk pool considerations" />
|
|
<meta name="abstract" content="The receiver configuration is the disk pool the receiver resides in, and how the data for the receiver is spread across the disk arms within that disk pool." />
|
|
<meta name="description" content="The receiver configuration is the disk pool the receiver resides in, and how the data for the receiver is spread across the disk arms within that disk pool." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplanrjrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisrcjrnrcv.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakidiskpoolrcv.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyoverview.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzakirdiskpool" />
|
|
<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>Journal receiver disk pool considerations</title>
|
|
</head>
|
|
<body id="rzakirdiskpool"><a name="rzakirdiskpool"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Journal receiver disk pool considerations</h1>
|
|
<div><p>The <span class="uicontrol">receiver configuration</span> is the disk pool the receiver resides in, and how the data for the receiver is spread across the disk arms within that disk pool.</p>
|
|
<p>A remote journal receiver will have the same receiver configuration as its corresponding source receiver. If the source receiver is in a disk pool that is spread across multiple disk units, then the
|
|
remote journal receiver will also be configured to use the same number of disk units. The remote journal receiver may be in a disk pool that has fewer disk units than the disk pool that contains the journal
|
|
receiver on the source system. If this occurs, the remote journal receiver will still be configured as if it still had that same number of disk units as the source journal receiver. However, the data may
|
|
physically be going to a fewer number of disk units.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> If the remote journal receiver is in a disk pool with fewer disk arms than the source journal receiver, then performance may be impacted. This is because the disk arms for the remote receiver will
|
|
be moving considerably more than the disk arms will be moving for the source receiver. Therefore, we recommend that the number of disk arms is the same on the source and remote journal receivers disk pools.</div>
|
|
<p>Likewise, the journal receiver on the source system may be in a disk pool that has fewer disk units than the disk pool that contains the remote journal receiver. If this occurs, the remote journal receiver
|
|
will not take advantage of all possible disk units on the target system.</p>
|
|
<div class="section"><h4 class="sectiontitle">Independent disk pool considerations</h4><p>The following considerations apply if the remote journal receiver is on an independent disk pool:</p>
|
|
<ul><li>If the local system has the journaling environment in a basic, system disk pool, or independent disk pool, the remote journal can be in a independent disk pool. Likewise, if the local system has the
|
|
journaling environment in an independent disk pool, the remote journal can be in a basic, system disk pool, or independent disk pool.</li>
|
|
<li>The independent disk pool on the remote system must be varied on.</li>
|
|
<li>The independent disk pool must be a library capable independent disk pool.</li>
|
|
<li>The remote journal and remote journal receiver must be in the same disk pool group.</li>
|
|
</ul>
|
|
<p>Determine the type of disk pool in which to place journal receivers has more information about journal receivers and disk pools. The Independent disk pools topic has detailed information
|
|
about independent disk pools.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplanrjrn.htm" title="The following topics provide detailed information for planning to set up remote journals:">Plan for remote journals</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakisrcjrnrcv.htm" title="When you specify a journal receiver for remote journaling, you are specifying where the replication of journal entries will start.">Where the replication of journal entries start</a></div>
|
|
<div><a href="rzakidiskpoolrcv.htm" title="Use disk pools (auxiliary storage pool) to control which objects are allocated to which groups of disk units. If you are journaling many active objects to the same journal, the journal receiver can become a performance bottleneck. One way to minimize the performance impact of journaling is to put the journal receiver in a separate disk pool. This also provides additional protection because your objects are on different disk units from the journal receiver, which contains a copy of changes to the objects.">Determine the type of disk pool in which to place journal receivers</a></div>
|
|
<div><a href="../rzaly/rzalyoverview.htm">Independent disk pools</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |