93 lines
6.2 KiB
HTML
93 lines
6.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="Eliminating save-outage time: Overview" />
|
||
|
|
<meta name="abstract" content="This information tells you what happens when you use the save-while-active function to eliminate your save-outage time." />
|
||
|
|
<meta name="description" content="This information tells you what happens when you use the save-while-active function to eliminate your save-outage time." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu300.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu348.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu311.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu365.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu358.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu347.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="rzaiu313" />
|
||
|
|
<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>Eliminating save-outage time: Overview</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiu313"><a name="rzaiu313"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Eliminating save-outage time: Overview</h1>
|
||
|
|
<div><p>This information tells you what happens when you use the save-while-active
|
||
|
|
function to eliminate your save-outage time. </p>
|
||
|
|
<p>The save-while-active function can eliminate your outage for particular
|
||
|
|
save operations by not waiting for applications to end before starting the
|
||
|
|
save procedure. However, you will have more complex and longer recovery procedures
|
||
|
|
after restoring objects from the media.</p>
|
||
|
|
<p>You will have more complex recovery procedures because eliminating your
|
||
|
|
save-outage time saves objects at different application boundaries. For save-while-active
|
||
|
|
purposes, an <span class="uicontrol">application boundary</span> is a point in time:</p>
|
||
|
|
<ul><li>When all of the objects that a particular application is dependent upon
|
||
|
|
are at a consistent state in relationship to each other.</li>
|
||
|
|
<li> When the objects are also in a state where you can start or restart the
|
||
|
|
application.</li>
|
||
|
|
</ul>
|
||
|
|
<p>When you choose to eliminate your save-outage time, applications can update
|
||
|
|
the objects you are saving before the objects reach a checkpoint. When this
|
||
|
|
happens the server cannot determine if the images of those objects reached
|
||
|
|
application boundaries when you restore those objects. Therefore at restore
|
||
|
|
time, you need to define recovery procedures to bring those objects to a common
|
||
|
|
application boundary. You will need these recovery procedures to bring the
|
||
|
|
objects to a consistent state in relationship to each other. For this reason
|
||
|
|
you should protect the objects you are saving with journaling or commitment
|
||
|
|
control.</p>
|
||
|
|
<p>Furthermore, if you do not use commitment control, partial transactions
|
||
|
|
can be saved without your knowledge. When you use commitment control, you
|
||
|
|
can choose to have the save operation save all objects at transaction boundaries.
|
||
|
|
However, if applications do not reach commitment boundaries within the specified
|
||
|
|
time, the save operation will fail.</p>
|
||
|
|
<p> You should consider each of the following when you determine these recovery
|
||
|
|
procedures: </p>
|
||
|
|
<ul><li>If the objects that the applications are dependent on consist entirely
|
||
|
|
of database files or if they depend on other object types such as integrated
|
||
|
|
file system objects.</li>
|
||
|
|
<li>If the objects that the applications are dependent on are in a single
|
||
|
|
library or span multiple libraries.</li>
|
||
|
|
<li>If the objects that the applications are dependent on are journaled objects.</li>
|
||
|
|
<li>If the changes the applications made to the objects are under commitment
|
||
|
|
control.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu300.htm" title="The save-while-active function allows you to use your server during all or part of the save process, that is, save your server while it is active.">Save your server while it is active</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaiurzaiu311.htm" title="How your save-while-active function fits into your backup and recovery strategy depends on whether you will reduce or eliminate your save-outage time. These pages contain information to help you decide how you will use the save-while-active function. It also contains pages with technical descriptions of the save-while-active function.">Save-while-active and your backup and recovery strategy</a></div>
|
||
|
|
<div><a href="rzaiurzaiu365.htm">Considerations for recovery procedures after eliminating save-outage time</a></div>
|
||
|
|
<div><a href="rzaiurzaiu347.htm">Example: Restore libraries after reducing save-outage time</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaiurzaiu358.htm">Recommended recovery procedures after eliminating save-outage time</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaiurzaiu348.htm" title="Use the save-while-active function to eliminate your save-outage time.">Eliminate your save-outage time</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|