66 lines
4.6 KiB
HTML
66 lines
4.6 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="Recover recent changes after an unplanned outage" />
|
||
|
|
<meta name="abstract" content="After an unplanned outage, your goal is to get your system up and running again as quickly as possible. You want to get back to where you were before the outage occurred without having to manually re-enter transactions." />
|
||
|
|
<meta name="description" content="After an unplanned outage, your goal is to get your system up and running again as quickly as possible. You want to get back to where you were before the outage occurred without having to manually re-enter transactions." />
|
||
|
|
<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="rzalwrecent_changes" />
|
||
|
|
<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>Recover recent changes after an unplanned outage</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalwrecent_changes"><a name="rzalwrecent_changes"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Recover recent changes after an unplanned outage</h1>
|
||
|
|
<div><p>After an unplanned outage, your goal is to get your system up and
|
||
|
|
running again as quickly as possible. You want to get back to where you were
|
||
|
|
before the outage occurred without having to manually re-enter transactions.</p>
|
||
|
|
<p>This may involve rebuilding some of your data. There are a few availability
|
||
|
|
tools that you can use that will help you more quickly get back to where you
|
||
|
|
were before the outage occurred.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Journaling</h4><p>Journal management prevents
|
||
|
|
transactions from being lost if your system ends abnormally. When you journal
|
||
|
|
an object, the system keeps a record of the changes you make to that object.
|
||
|
|
For detailed information on how to plan for and use journaling, see <a href="../rzaki/rzakikickoff.htm">Journal management</a>.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Commitment control</h4><p>Commitment control helps to provide
|
||
|
|
data integrity on your server. It allows you to define and process a group
|
||
|
|
of changes to resources, such as database files or tables, as a single transaction.
|
||
|
|
Then, it ensures that either the entire group of individual changes occur
|
||
|
|
or that none of the changes occur. For example, you lose power just as a series
|
||
|
|
of updates are being made to your database. Without commitment control, you
|
||
|
|
run the risk of having incomplete or corrupt data. With commitment control,
|
||
|
|
the incomplete updates would be backed out of your database when you restart
|
||
|
|
your server.</p>
|
||
|
|
<p>You can use commitment control to design an application
|
||
|
|
so the system can restart the application if a job, an activation group within
|
||
|
|
a job, or the system ends abnormally. With commitment control, you can have
|
||
|
|
assurance that when the application starts again, no partial updates are in
|
||
|
|
the database due to incomplete transactions from a prior failure.</p>
|
||
|
|
<p>For
|
||
|
|
detailed information on how to plan for and use commitment control, see <a href="../rzakj/rzakjcommitkickoff.htm">Commitment control</a>.</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>
|