75 lines
7.2 KiB
HTML
75 lines
7.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 management and independent disk pools" />
|
||
|
|
<meta name="abstract" content="Independent disk pools are disk pools 33 through 255. Independent disk pools can be user-defined file system (UDFS) independent disk pools or library-capable independent disk pools." />
|
||
|
|
<meta name="description" content="Independent disk pools are disk pools 33 through 255. Independent disk pools can be user-defined file system (UDFS) independent disk pools or library-capable independent disk pools." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnuseaux.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnobjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakidiskpoolrcv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ifs/rzaaxudfsfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalydmkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiredirect.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="rzakiiasp" />
|
||
|
|
<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 management and independent disk pools</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiiasp"><a name="rzakiiasp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal management and independent disk pools</h1>
|
||
|
|
<div><p>Independent disk pools are disk pools 33 through 255. Independent disk pools can be user-defined file system (UDFS) independent disk pools or library-capable independent disk pools.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">UDFS and library-capable independent disk pools</h4><p>UDFS independent disk pools are independent disk pools that only have a user-defined file system. UDFS independent disk pools cannot
|
||
|
|
store journals and receivers. In contrast to UDFS disk pools, library-capable independent disk pools have libraries and are capable of storing journals and receivers. If you plan to journal objects on an
|
||
|
|
independent disk pool, you must use a library-capable independent disk pool.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> A library-capable independent disk pool can have integrated file system objects. You can also journal integrated file
|
||
|
|
system objects on a library-capable independent disk pool.</div>
|
||
|
|
<p>You cannot journal objects on a UDFS independent disk pool.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Switchable and dedicated independent disk pools</h4><p>Independent disk pools can also be switchable or dedicated. Dedicated independent disk pools are used on only one system. Switchable
|
||
|
|
independent disk pools can be switched between systems. If they are library-capable, you can journal objects on either switchable or dedicated independent disk pools.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Disk pool groups</h4><p>You can group switchable independent disk pools into disk pool groups. Disk pool groups consist of one primary disk pool and one or more secondary disk pools.
|
||
|
|
If you are going to journal an object in a disk pool group, the object and the journal must be in the same disk pool. The journal receiver can be in a different disk pool, but must be in the same disk pool
|
||
|
|
group as the journal and journaled object.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Rules for journaling objects on independent disk pools</h4><p>Use the following rules when journaling objects on independent disk pools:</p>
|
||
|
|
<ul><li>The disk pool must be available on the system on which you are working.</li>
|
||
|
|
<li>The disk pool must be a library-capable disk pool. You cannot journal an object on a UDFS independent disk pool.</li>
|
||
|
|
<li>In a disk pool group, the journaled object and the journal must be in the same disk pool.</li>
|
||
|
|
<li>In a disk pool group, the journal receiver can be in a different disk pool, but must be in the same disk pool group.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Manage disk units in disk pools has information about managing disk pools. The Independent disk pools topic has information about setting up and managing independent disk pools.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplnuseaux.htm" title="If you are journaling an object, journal management writes a copy of every object change to the journal receiver. It writes additional entries for object level activity, such as opening and closing the object, adding a member, or changing an object attribute. If you have a busy system and journal many objects, your journal receivers can quickly become very large.">Plan for journal use of auxiliary storage</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakiplnobjrn.htm" title="When you plan which objects to journal, consider the following:">Plan which objects to journal</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="../ifs/rzaaxudfsfs.htm">User-defined file system</a></div>
|
||
|
|
<div><a href="../rzaly/rzalydmkickoff.htm">Disk management</a></div>
|
||
|
|
<div><a href="../rzaly/rzalyoverview.htm">Independent disk pools</a></div>
|
||
|
|
<div><a href="rzakiredirect.htm" title="Library redirection provides a means for remote journals and any of their associated journal receivers to optionally reside in differently named libraries on the target system from the corresponding local journal and journal receivers on the local system.">Library redirection with remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|