170 lines
12 KiB
HTML
170 lines
12 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: Data replication environment for remote journals" />
|
||
|
|
<meta name="abstract" content="In this scenario, JKLINT and JKLINT2 use remote journaling for data replication purposes only." />
|
||
|
|
<meta name="description" content="In this scenario, JKLINT and JKLINT2 use remote journaling for data replication purposes only." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirscenarios.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihotbackup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiaddremj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiactiverep.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisrcjrnrcv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QJOCHGST.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgrmtjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiactive.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautodelete.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihotbackup.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="rzakirdatarep" />
|
||
|
|
<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: Data replication environment for remote journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakirdatarep"><a name="rzakirdatarep"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: Data replication environment for remote journals</h1>
|
||
|
|
<div><p>In this scenario, JKLINT and JKLINT2 use remote journaling for
|
||
|
|
data replication purposes only.</p>
|
||
|
|
<p>The following figure illustrates this remote journaling environment. <strong>Data
|
||
|
|
replication</strong> is the function of maintaining a separate copy of data from
|
||
|
|
an original copy, keeping the two copies consistent with each other.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Typical data replication environment with remote journal function</h4><br /><img src="rzaki514.gif" alt="This figure shows a typical replication environment." /><br /></div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">How the data replication environment works</h4><p>Local
|
||
|
|
objects, F1, F2, and F3, on JKLINT are journaled to local journal JRN in library
|
||
|
|
JLB1. A remote journal is defined on JKLINT2, where JRN has been redirected
|
||
|
|
to library JLB2. This remote journal receives journal entries from the local
|
||
|
|
journal on JKLINT. A hot-backup application apply replays the changes to the
|
||
|
|
data replica on system JKLINT2.</p>
|
||
|
|
<p>The data replica is journaled to a local
|
||
|
|
journal, JRN in library JLB1, for system recovery purposes only, so this journal
|
||
|
|
must be in active state. If system JKLINT2 fails, the system performs recovery
|
||
|
|
for the objects by using this local journal.</p>
|
||
|
|
<p>A hot-backup application
|
||
|
|
assists in replicating data from one system to another. The hot-backup application
|
||
|
|
apply is only performing the replay of operations to the data replica on the
|
||
|
|
target system.</p>
|
||
|
|
<p>Since this scenario is for a data replication environment,
|
||
|
|
the hot-backup application does not perform a switch-over to the backup system.
|
||
|
|
See Scenario: Hot-backup environment for more details about hot-backup applications
|
||
|
|
applies and hot-backup switch-overs.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">How to establish the data replication environment for JKLINT
|
||
|
|
and JKLINT2</h4><p>The objects and local journal on JKLINT are already
|
||
|
|
assumed to exist. The journal state for the local journal is also assumed
|
||
|
|
to be active. The communications environment and associated RDB entries already
|
||
|
|
exist and are established.</p>
|
||
|
|
<p>Establishing the data replication environment
|
||
|
|
for JKLINT and JKLINT2 requires the following:</p>
|
||
|
|
<ol><li>Create the remote journal on JKLINT2, and specify library redirection.
|
||
|
|
Library redirection indicates that the journal's library, JLB1 on JKLINT,
|
||
|
|
is redirected to library JLB2 on JKLINT2. The journal receiver's library,
|
||
|
|
RLB1 on JKLINT, is redirected to library RLB2 on JKLINT2.<p>After this step,
|
||
|
|
the remote journal exists, but no receiver is currently attached.</p>
|
||
|
|
</li>
|
||
|
|
<li>To establish a clean breakpoint, perform a change journal operation to
|
||
|
|
attach a new journal receiver at this time.<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />The next step
|
||
|
|
restores local journal JRN in library JLB1 and attaches receiver X1002 in
|
||
|
|
library RLB1. It then restores the objects, and starts journaling for the
|
||
|
|
objects to the restored local journal.<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</li>
|
||
|
|
<li>Save the local journal and objects from JKLINT and restore them to JKLINT2.
|
||
|
|
This primes the data replica and establishes the local journaling environment
|
||
|
|
on JKLINT2.</li>
|
||
|
|
<li>Activate the remote journal on system JKLINT2. Specify that the remote
|
||
|
|
journal must start with the attached receiver. Since no receiver is attached
|
||
|
|
to the remote journal, the receiver that is currently attached to the local
|
||
|
|
journal on JKLINT (X2) is created on JKLINT2. This receiver is then attached
|
||
|
|
to the remote journal. Journal entries are replicated, starting with the first
|
||
|
|
journal entry in receiver X2.<p>An additional parameter on the Change Journal
|
||
|
|
State (QjoChangeJournalState) API and Change Remote Journal (CHGRMTJRN) command
|
||
|
|
indicates whether the remote journal function is to be maintained synchronously
|
||
|
|
or asynchronously. Depending on how the remote journal is maintained, other
|
||
|
|
parameters may also apply.</p>
|
||
|
|
</li>
|
||
|
|
<li>The hot-backup application apply process receives or retrieves journal
|
||
|
|
entries from the remote journal, starting with the entries that were deposited
|
||
|
|
after the data was saved and primed into the data replica. The process then
|
||
|
|
starts replaying the changes that are contained in these journal entries to
|
||
|
|
the data replica.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Normal run-time environment for the data replication environment</h4><p>You
|
||
|
|
can activate and inactivate the replication of journal entries to the remote
|
||
|
|
journal as needed. Each time you activate the remote journal, *ATTACHED is
|
||
|
|
specified as the point in the receiver chain to start receiving journal entries.
|
||
|
|
The system checks the currently attached remote journal receiver for journal
|
||
|
|
entries and replicates the next journal entry in sequence.</p>
|
||
|
|
<p>You must
|
||
|
|
specify the delivery mode when activating the remote journal. If needed, the
|
||
|
|
delivery mode can be different on each activation of the remote journal.</p>
|
||
|
|
<p>Change
|
||
|
|
journal operations that attach a new receiver to the local journal on system
|
||
|
|
JKLINT are performed by the remote journal function as required on the target
|
||
|
|
system. The remote journal function attaches the associated receivers to the
|
||
|
|
remote journal automatically. If the remote journal is being maintained synchronously,
|
||
|
|
the change journal operation to attach a new receiver is essentially a coordinated
|
||
|
|
operation between the source and target systems. If the remote journal is
|
||
|
|
being maintained asynchronously, the change journal operation to attach a
|
||
|
|
new receiver on the target system is performed differently. In this case,
|
||
|
|
it is triggered when the journal entry with journal code 'J' and entry type
|
||
|
|
'PR' is received by the remote journal on the target system.</p>
|
||
|
|
<p>The hot-backup
|
||
|
|
application apply continues to replay changes to the data replica as received
|
||
|
|
or retrieved from the receivers associated with the remote journal.</p>
|
||
|
|
<p>If
|
||
|
|
needed, you can delete the receivers that are associated with the local journal
|
||
|
|
on JKLINT when each receiver is replicated to JKLINT2. Sharon can accomplish
|
||
|
|
this by specifying automatic deletion of journal receivers or manually deleting
|
||
|
|
the receivers on JKLINT.</p>
|
||
|
|
<p>You can save the receivers from JKLINT2. If
|
||
|
|
necessary, you can use the receivers for recovery of the original data on
|
||
|
|
system JKLINT at a later time.</p>
|
||
|
|
<p>See <a href="rzakideletercv.htm">Delete journal receivers</a> for more information.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Data replication recovery if JKLINT fails</h4><p>Recovery
|
||
|
|
for JKLINT and JKLINT2 is simpler than environments that involve hot-backup
|
||
|
|
because the hot-backup application does not switch-over to the backup system.
|
||
|
|
What prevents the complications is an assumption that the hot-backup application
|
||
|
|
apply logic will not receive and replay unconfirmed journal entries to the
|
||
|
|
data replica if system JKLINT2 loses communications with system JKLINT. Therefore,
|
||
|
|
the data replica on system JKLINT2 can never get ahead of the data on system
|
||
|
|
JKLINT. This greatly simplifies data synchronization.</p>
|
||
|
|
</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="rzakisrcjrnrcv.htm" title="When you specify a journal receiver for remote journaling, you are specifying where the replication of journal entries will start.">Where the replication of journal entries start</a></div>
|
||
|
|
<div><a href="rzakiactive.htm" title="Activating a remote journal means starting and then maintaining the replication of journal entries from a source journal to a remote journal. Activating a remote journal always occurs from the source system.">Activate and inactivate remote journals</a></div>
|
||
|
|
<div><a href="rzakiautodelete.htm" title="If you choose system journal receiver management, you can also have the system delete journal receivers that are no longer needed for recovery. You can only specify this if you are using system journal receiver management.">Automatic deletion of journal receivers</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakiaddremj.htm" title="This topic provides instructions for adding a remote journal.">Add remote journals</a></div>
|
||
|
|
<div><a href="rzakiactiverep.htm" title="In order to activate the replication of journal entries to a given remote journal, the following must be true:">Activate the replication of journal entries to a remote journal</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../apis/QJOCHGST.htm">Change Journal State (QjoChangeJournalState) API</a></div>
|
||
|
|
<div><a href="../cl/chgrmtjrn.htm">Change Remote Journal (CHGRMTJRN) command</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>
|