74 lines
4.3 KiB
HTML
74 lines
4.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="Disk pool benefits" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalyaspsovrvw.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalybenefits.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="hdraspsben" />
|
|
<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>Disk pool benefits</title>
|
|
</head>
|
|
<body id="hdraspsben"><a name="hdraspsben"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Disk pool benefits</h1>
|
|
<div><p>Placing objects in user disk pools, also called auxiliary storage pools
|
|
(ASPs) in the character-based interface, can provide several advantages. These
|
|
include the following:</p>
|
|
<div class="section"><h4 class="sectiontitle">Additional data protection</h4><p>By separating libraries,
|
|
documents, or other objects in a user disk pool, you protect them from data
|
|
loss when a disk unit in the system disk pool or other user disk pool fails.
|
|
For example, if you have a disk unit failure, and data contained on the system
|
|
disk pool is lost, objects contained in user disk pools are not affected and
|
|
can be used to recover objects in the system disk pool. Conversely, if a failure
|
|
causes data that is contained in a user disk pool to be lost, data in the
|
|
system disk pool is not affected.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Improved system performance</h4><p>Using disk pools can
|
|
also improve system performance. This is because the system dedicates the
|
|
disk units that are associated with a disk pool to the objects in that disk
|
|
pool. For example, suppose you are working in an extensive journaling environment.
|
|
Placing journals and journaled objects in a <a href="rzalyuserasp.htm">Basic disk pools</a> can reduce contention between the receivers and journaled
|
|
objects if they are in different disk pools, which improves journaling performance.
|
|
If you use independent disk pools to reduce contention, place the objects
|
|
to be journaled in the primary disk pool and journal receivers in one or more
|
|
secondary disk pools. </p>
|
|
<p>Placing many active journal receivers in the
|
|
same disk pool is not productive. The resulting contention between writing
|
|
to more than one receiver in the disk pool can slow system performance. For
|
|
maximum performance, place each active journal receiver in a separate user
|
|
disk pool.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Separation of objects with different availability and recovery
|
|
requirements</h4><p>You can use different disk protection techniques for
|
|
different disk pools. You can also specify different target times for recovering
|
|
access paths. You can assign critical or highly used objects to protected,
|
|
high-performance disk units. You might assign large, low-usage files, like
|
|
history files, to unprotected, low-performance disk units.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalyaspsovrvw.htm">Disk pools</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="rzalybenefits.htm">Benefits of independent disk pools</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |