114 lines
9.5 KiB
HTML
114 lines
9.5 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="Remote journal concepts" />
|
||
|
|
<meta name="abstract" content="Remote journal management helps to efficiently replicate journal entries to one or more systems. You can use remote journal management with application programs to maintain a data replica. A data replica is a copy of the original data that resides on another iSeries server or independent disk pool. The original data resides on a primary system. Applications make changes to the original data during normal operations." />
|
||
|
|
<meta name="description" content="Remote journal management helps to efficiently replicate journal entries to one or more systems. You can use remote journal management with application programs to maintain a data replica. A data replica is a copy of the original data that resides on another iSeries server or independent disk pool. The original data resides on a primary system. Applications make changes to the original data during normal operations." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiremotekickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirnetworks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakitwotypes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistate.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirjrnrcvrs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiaddprocess.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiprotocols.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakireleases.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/rcvjrne.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="rzakirconcepts" />
|
||
|
|
<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>Remote journal concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakirconcepts"><a name="rzakirconcepts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Remote journal concepts</h1>
|
||
|
|
<div><p>Remote journal management helps to efficiently replicate journal
|
||
|
|
entries to one or more systems. You can use remote journal management with
|
||
|
|
application programs to maintain a <span class="uicontrol">data replica</span>. A
|
||
|
|
data replica is a copy of the <span class="uicontrol">original data</span> that resides
|
||
|
|
on another iSeries™ server
|
||
|
|
or independent disk pool. The original data resides on a primary system. Applications
|
||
|
|
make changes to the original data during normal operations.</p>
|
||
|
|
<p>Prior to V4R2M0, you could have accomplished a similar function by using
|
||
|
|
the Receive Journal Entry (RCVJRNE) command. In that environment, the RCVJRNE
|
||
|
|
exit program receives journal entries from a journal, and then sends the journal
|
||
|
|
entries to the remote system by using whatever communications method is available.
|
||
|
|
All of this processing occurs asynchronously to the operation that is causing
|
||
|
|
the journal entry deposit and takes place at an application layer of the system.</p>
|
||
|
|
<p>The remote journal function, however, replicates journal entries to the
|
||
|
|
remote system at the Licensed Internal Code layer. Moving the replication
|
||
|
|
to this lower layer provides the following:</p>
|
||
|
|
<ul><li>The remote system handles more of the replication overhead</li>
|
||
|
|
<li>Overall system performance and journal entry replication performance is
|
||
|
|
improved</li>
|
||
|
|
<li>Replication can (optionally) occur synchronously to the operation that
|
||
|
|
is causing the journal entry deposit</li>
|
||
|
|
<li>Journal receiver save operations can be moved to the remote system.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The figures below illustrate a comparison of a hot-backup environment with
|
||
|
|
and without remote journal management. <span class="uicontrol">Hot-backup</span> is
|
||
|
|
the function of replicating an application's dependent data from a <span class="uicontrol">primary
|
||
|
|
system</span> to a <span class="uicontrol">backup system</span>. The primary
|
||
|
|
system is the system where the original data resides. The backup system is
|
||
|
|
the system where a replica of the original data is being maintained. In the
|
||
|
|
event of a primary system failure, you can perform a switch-over to the backup
|
||
|
|
system.</p>
|
||
|
|
<p><strong>Hot-backup environment without remote journal function, and application-code
|
||
|
|
based apply</strong></p>
|
||
|
|
<br /><img src="rzaki506.gif" longdesc="rzakidesc_1.htm" alt="Hot-backup environment without remote journal function" /><br /><p><img src="./delta.gif" alt="Start of change" />This figure above illustrates that processing with the RCVJRNE
|
||
|
|
command occurs asynchronously to the operation that is causing the journal
|
||
|
|
entry deposit. This processing requires more overhead than the remote journal
|
||
|
|
function.<img src="c.gif" alt="Image description." /> <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><strong>Hot-backup environment with remote journal function, and application-code
|
||
|
|
based apply</strong></p>
|
||
|
|
<br /><img src="rzaki507.gif" longdesc="rzakidesc_2.htm" alt="Hot-backup environment with remote journal function" /><br /><p><img src="./delta.gif" alt="Start of change" />This figure above illustrates that processing with
|
||
|
|
the remote journal function occurs synchronously to the operation that is
|
||
|
|
causing the journal entry deposit. This processing requires less overhead
|
||
|
|
than the RCVJRNE command.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>The following topics provide more information about remote journaling:</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakirnetworks.htm">Network configurations for remote journals</a></strong><br />
|
||
|
|
This topic describes various network configuration for remote journals.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakitwotypes.htm">Types of remote journals</a></strong><br />
|
||
|
|
The two types of remote journals are *TYPE1 and *TYPE2. The two types identify operational characteristics of a remote journal and its associated journal receivers. The following table is an overview of the different remote journal types and their characteristics. There are no performance differences between the types of remote journals.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakistate.htm">Journal state and delivery mode</a></strong><br />
|
||
|
|
The <span class="uicontrol">journal state</span> describes an attribute
|
||
|
|
for a journal. The attribute value can be *ACTIVE, *INACTIVE (remote journal
|
||
|
|
only), or *STANDBY (local journal only). For a local journal, *ACTIVE indicates
|
||
|
|
that journal entries are currently allowed to be deposited into the journal.
|
||
|
|
*STANDBY indicates that most journal entries are not deposited.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakirjrnrcvrs.htm">Journal receivers associated with a remote journal</a></strong><br />
|
||
|
|
Journal receivers that are associated with a remote journal are exact replicas of the corresponding journal receivers that are associated with the journal on the source system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiaddprocess.htm">Add remote journal process</a></strong><br />
|
||
|
|
Adding a remote journal creates a remote journal on a target system or independent disk pool and associates that remote journal with the journal on the source system. This occurs if this is the first time the remote journal is being established for a journal. The journal on the source system can be either a local or remote journal.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiprotocols.htm">Supported communications protocols for remote journals</a></strong><br />
|
||
|
|
The remote journal function supports the following communications protocols for replicating the journal entries to the remote systems:</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakireleases.htm">Release-to-release considerations for remote journals</a></strong><br />
|
||
|
|
Release-to-release considerations for remote journals are discussed in this topic.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiremotekickoff.htm" title="Use remote journal management to establish journals and journal receivers on a remote system that are associated with specific journals and journal receivers on a local system. Remote journal management replicates journal entries from the local system to the journals and journal receivers that are located on the remote system after they have been established.">Remote journal management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/rcvjrne.htm">Receive Journal Entry (RCVJRNE) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|