81 lines
7.0 KiB
HTML
81 lines
7.0 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="Scenario: Recovery for remote journaling" />
|
|
<meta name="abstract" content="This scenario describes a hot-backup environment in which the local system, JKLINT fails. It is necessary to restore the local system, and synchronize it with the remote system, JKLINT2." />
|
|
<meta name="description" content="This scenario describes a hot-backup environment in which the local system, JKLINT fails. It is necessary to restore the local system, and synchronize it with the remote system, JKLINT2." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirscenarios.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiconfirm.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiriplconsid.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihotbackup.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirecovdtails.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirecovdtails.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="rzakirecovery" />
|
|
<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>Scenario: Recovery for remote journaling</title>
|
|
</head>
|
|
<body id="rzakirecovery"><a name="rzakirecovery"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Scenario: Recovery for remote journaling</h1>
|
|
<div><p>This scenario describes a hot-backup environment in which the local system, JKLINT fails. It is necessary to restore the local system, and synchronize it with the remote system, JKLINT2.</p>
|
|
<p>Details: Recovery for remote journaling scenario has step-by-step instructions for recovering from this failure this scenario describes.</p>
|
|
<p>This scenario, and the details for this scenario, only discuss database physical files. All the concepts, however, apply to any journaled object type.</p>
|
|
<div class="section"><h4 class="sectiontitle">Example remote journal environment for hot-backup recovery</h4><p>The following figure illustrates the hot-backup environment for JKLINT and JKLINT2. The following items list considerations
|
|
for this environment:</p>
|
|
<ul><li>The remote journal BJ2 is only active after JKLINT fails. JKLINT2 assumes the role of primary system and JKLINT is running again (as the secondary system).</li>
|
|
<li>Journal receivers are not specifically called out in the figure. They have been omitted in an attempt to simplify the scenario and to focus on the recovery steps for the database. Where necessary, processing
|
|
specific to journal receivers is referred to in the scenario.</li>
|
|
<li>Likewise, library redirection for the journals and journal receivers is not specifically called out in the figure. Again, this is omitted in an attempt to simplify the scenario. In the scenario, the
|
|
libraries for any of the journals or journal receivers could be redirected to a library that is different from that being used for the corresponding objects on the other system.</li>
|
|
<li>The figure simply refers to the original data in the figure as DB on the primary system JKLINT and DB' as the data replica on the backup system JKLINT2. DB can be one or more journaled objects, and
|
|
DB' contains a replica for each of the journaled objects in DB.</li>
|
|
</ul>
|
|
<br /><img src="rzaki516.gif" alt="Illustration of JKLINT and JKLINT2" /><br /><p>For simplicity, the scenario below treats DB as a single database file and DB' as its replica.</p>
|
|
<p>The following
|
|
items describe the scenario at the time JKLINT fails:</p>
|
|
<ul><li>System JKLINT is the primary system.</li>
|
|
<li>The original data that is denoted by DB is journaled to an active local journal PJ1.</li>
|
|
<li>Remote journal BJ1 on backup system JKLINT2 is active, and unless otherwise noted, is synchronously receiving journal entries from journal PJ1.</li>
|
|
<li>A hot-backup application apply, not shown in the diagram, is asynchronously replaying, or applying, the changes to the data replica, DB'.</li>
|
|
<li>The data replica DB' is journaled to local journal PJ2 on system JKLINT2. <p>The journal state for journal PJ2 is *STANDBY.</p>
|
|
</li>
|
|
<li>Remote journal BJ2 has a journal state of *INACTIVE (journal entries are not replicated to it). Remote journal BJ2 is only active when accepting the data changes back from system JKLINT2. This occurs
|
|
after system JKLINT2 had been promoted to assume the role of the primary system due to a planned or unplanned outage of system JKLINT, and after system JKLINT has resumed operations.</li>
|
|
<li>The primary system, JKLINT, has failed.</li>
|
|
<li>The decision has been made to switch-over to the backup system, JKLINT2.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakirscenarios.htm" title="These scenarios describe the possible ways that JKL Toy Company can use remote journal management. JKL Toy Company uses the server JKLINT as their web server.">Scenarios: Remote journal management and recovery</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakiconfirm.htm" title="For a local journal, all entries are confirmed entries. There is no concept of unconfirmed entries.">Confirmed and unconfirmed journal entries</a></div>
|
|
<div><a href="rzakiriplconsid.htm" title="This topic discusses the considerations for remote journaling when you restart the server.">Remote journal considerations when restarting the server</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzakirecovdtails.htm" title="A description of the recovery process for remote journaling.">Details: Recovery for remote journaling scenario</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="rzakihotbackup.htm" title="In this scenario, the remote journaling environment uses a hot-backup application that causes JKLINT2 to replace JKLINT in the case that JKLINT has a failure.">Scenario: Hot-backup environment</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |