69 lines
4.4 KiB
HTML
69 lines
4.4 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="Benefits of SMAPP" />
|
||
|
<meta name="abstract" content="System-managed access-path protection (SMAPP) can greatly reduce the amount of time it takes to restart your system or vary on an independent disk pool, after an abnormal end." />
|
||
|
<meta name="description" content="System-managed access-path protection (SMAPP) can greatly reduce the amount of time it takes to restart your system or vary on an independent disk pool, after an abnormal end." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakismappintro.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyconcepts.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="rzakibenefits" />
|
||
|
<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>Benefits of SMAPP</title>
|
||
|
</head>
|
||
|
<body id="rzakibenefits"><a name="rzakibenefits"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Benefits of SMAPP</h1>
|
||
|
<div><p>System-managed access-path protection (SMAPP) can greatly reduce
|
||
|
the amount of time it takes to restart your system or vary on an independent
|
||
|
disk pool, after an abnormal end.</p>
|
||
|
<p>The time is reduced by protecting access paths. A protected access path
|
||
|
can be recovered much quicker than a unprotected access path.
|
||
|
It is an automatic function that runs without attention. SMAPP determines
|
||
|
which access paths to protect without any intervention by the user. It adjusts
|
||
|
to changes in the environment, such as the addition of new applications or
|
||
|
new hardware.</p>
|
||
|
<p>SMAPP does not require any setup. You do not have to change your applications.
|
||
|
You do not have to journal any physical files or even use journaling at all.
|
||
|
You simply need to determine your policy for access path recovery:</p>
|
||
|
<ul><li>After a failure, how long you can afford to spend rebuilding access paths
|
||
|
when you restart the system, or vary on an independent disk pool.</li>
|
||
|
<li>How to balance access path protection with other demands on system resources.</li>
|
||
|
<li>Whether to have different target times for recovering access paths for
|
||
|
different disk pools.</li>
|
||
|
</ul>
|
||
|
<p>You may need to experiment with different target recovery times for access
|
||
|
paths to achieve the correct balance for your system. If you configure additional
|
||
|
basic or independent disk pools, you must also evaluate your access path recovery
|
||
|
times.</p>
|
||
|
<p>The system protects access paths by journaling the access paths to internal
|
||
|
system journals. Therefore, SMAPP requires some additional auxiliary storage
|
||
|
for journal receivers. However, SMAPP is designed to keep the additional disk
|
||
|
usage to a minimum. SMAPP manages journal receivers and removes them from
|
||
|
the system as soon as they are no longer needed.</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakismappintro.htm" title="System-managed access-path protection (SMAPP) allows you to use some of the advantages of journaling without explicitly setting up journaling. Use SMAPP to decrease the time it takes to restart your system after an abnormal end.">System-managed access-path protection</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="../rzaly/rzalyconcepts.htm">Independent disk pool</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|