92 lines
6.3 KiB
HTML
92 lines
6.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Reduce the time to restart your system" />
|
||
|
|
<meta name="abstract" content="Unfortunately, systems periodically experience an unplanned outage. Use the availability tools described here to restart your system as quickly as possible after an unplanned outage." />
|
||
|
|
<meta name="description" content="Unfortunately, systems periodically experience an unplanned outage. Use the availability tools described here to restart your system as quickly as possible after an unplanned outage." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwshorten_unplanned.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzalwrestart" />
|
||
|
|
<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>Reduce the time to restart your system</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalwrestart"><a name="rzalwrestart"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Reduce the time to restart your system</h1>
|
||
|
|
<div><p>Unfortunately, systems periodically experience an unplanned outage.
|
||
|
|
Use the availability tools described here to restart your system as quickly
|
||
|
|
as possible after an unplanned outage. </p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />Before your system powers down, it performs certain activities
|
||
|
|
to ensure that your data is protected and that jobs are ended in a controlled
|
||
|
|
manner. When you experience an unplanned outage, your system cannot perform
|
||
|
|
these activities. Each of these tools should be used together to quicken the
|
||
|
|
start up times for your system. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>For more details on what happens when your system ends abnormally, see
|
||
|
|
<a href="../rzal2/rzal2startstop.htm">Start and stop the
|
||
|
|
system</a>.</p>
|
||
|
|
<p>Use the <a href="../experience/ipla-3-exprabstract.htm">Reducing
|
||
|
|
iSeries IPL Time experience report</a> to learn how to control the time
|
||
|
|
that it takes to start your iSeries server.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">System-managed access-path protection (SMAPP)</h4><p>An <dfn class="term">access
|
||
|
|
path</dfn> is the route an application takes through a database file to get
|
||
|
|
to the records it needs. A file can have multiple access paths, if different
|
||
|
|
programs need to see the records in different sequences. When your server
|
||
|
|
ends abnormally, such as during an unplanned outage, the system must rebuild
|
||
|
|
the access paths the next time it starts, which can take a long time. When
|
||
|
|
you use system-managed access-path protection, the system protects the access
|
||
|
|
paths so they do not have to be rebuilt when your system starts after an unplanned
|
||
|
|
outage. This will save you time when you restart your server, which will enable
|
||
|
|
you to get back to your normal business processes as quickly as possible.
|
||
|
|
For detailed information on SMAPP, see <a href="../rzaki/rzakismappintro.htm">System-managed
|
||
|
|
access-path protection</a>.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Journaling access paths</h4><p>Like SMAPP, journaling access
|
||
|
|
paths can help you to ensure that critical files and access paths are available
|
||
|
|
as soon as possible after you restart your server. However, when you use SMAPP,
|
||
|
|
the system decides which access paths to protect. Therefore, if the server
|
||
|
|
does not protect an access path that you consider critical, you may be delayed
|
||
|
|
in getting your business running again. When you journal access paths, you
|
||
|
|
decide which paths to journal. </p>
|
||
|
|
<p>For more details on journaling access
|
||
|
|
paths, see <a href="../rzaki/rzakismappapjourn.htm">SMAPP
|
||
|
|
and access path journaling</a>.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />SMAPP and journaling access
|
||
|
|
paths can be used separately. However; if you use these tools together, you
|
||
|
|
can maximize their effectiveness for reducing startup time by ensuring that
|
||
|
|
all access paths that are critical to your business operations are protected.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />Protecting your access paths is also important if you plan to use
|
||
|
|
any disk-based copy services, such as cross-site mirroring or IBM TotalStorage
|
||
|
|
Enterprise Storage Solution (ESS) peer-to-peer copy features, to avoid rebuilding
|
||
|
|
access paths when you failover to a backup server. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Independent disk pools</h4><p>When a system is started
|
||
|
|
or restarted, you can start each independent disk pools individually. By starting
|
||
|
|
each independent disk pool separately, the system can be made available more
|
||
|
|
quickly. You can prioritize the workload so that critical data becomes available
|
||
|
|
first. You can then vary on independent disk pools in a specific order based
|
||
|
|
on this priority. See <a href="../rzaly/rzalystartup.htm">Example:
|
||
|
|
Make independent disk pool available at startup</a> for more information.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwshorten_unplanned.htm" title="Unplanned outages do occur, and a key to availability is to ensure that when they do occur you can recover from them as quickly as possible.">Shorten unplanned outages</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|