115 lines
8.3 KiB
HTML
115 lines
8.3 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="Network configurations for remote journals" />
|
||
|
|
<meta name="abstract" content="This topic describes various network configuration for remote journals." />
|
||
|
|
<meta name="description" content="This topic describes various network configuration for remote journals." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiaddprocess.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="rzakirnetworks" />
|
||
|
|
<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>Network configurations for remote journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakirnetworks"><a name="rzakirnetworks"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Network configurations for remote journals</h1>
|
||
|
|
<div><p>This topic describes various network configuration for remote journals.</p>
|
||
|
|
<p>The following figure shows the two basic remote journal function configurations.</p>
|
||
|
|
<br /><img src="rzaki508.gif" alt="Image of broadcast and cascade configurations" /><br /><p>A <span class="uicontrol">broadcast</span> configuration is a journal that replicates
|
||
|
|
its journal entries to one or more remote journals. A <span class="uicontrol">cascade</span> configuration
|
||
|
|
is a remote journal that replicates its journal entries to an additional remote
|
||
|
|
journal. The additional remote journal can replicate the entries to yet another
|
||
|
|
remote journal, and so on. The remote journal function configurations can
|
||
|
|
stand alone or can be combined with one another. For example, one or more
|
||
|
|
of the remote journals in the broadcast configuration could cascade down to
|
||
|
|
several additional remote journals. Likewise, one or more remote journals
|
||
|
|
in the cascade configuration could broadcast out to one or more remote journals.</p>
|
||
|
|
<p>A <span class="uicontrol">local journal</span> is populated by applications that
|
||
|
|
are depositing journal entries. A <span class="uicontrol">remote journal</span> is
|
||
|
|
populated by receiving its journal entries from either a local or another
|
||
|
|
remote journal. The journals are paired, as depicted in the preceding figure
|
||
|
|
where (S) represents a journal on a source system, and (T) represents a journal
|
||
|
|
on a target system. In the cascade configuration, a remote journal can be
|
||
|
|
a recipient of journal entries (a target), and a replicator of journal entries
|
||
|
|
(a source) at the same time.</p>
|
||
|
|
<p>A <span class="uicontrol">source system</span> is a system where a journal resides
|
||
|
|
and is having its journal entries replicated to a remote journal on a target
|
||
|
|
system.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> A source system is not necessarily the primary system. For example,
|
||
|
|
a remote journal that is cascading its journal entries to another remote journal
|
||
|
|
is said to reside on a source system.</div>
|
||
|
|
<p>A <span class="uicontrol">target system</span> is a system where a remote journal
|
||
|
|
resides and is receiving journal entries from a journal on a source system.</p>
|
||
|
|
<p>A <span class="uicontrol">remote journal network</span> includes the local journal
|
||
|
|
and all of the remote journals that are downstream from that local journal.
|
||
|
|
You can set up the remote journal network in broadcast configuration, cascade
|
||
|
|
configuration, or a combination of the two configurations.</p>
|
||
|
|
<p>In many environments, users attempt to minimize the amount of processing
|
||
|
|
that the local or primary system performs by shifting as much of the processing
|
||
|
|
as possible to other systems in the network. A combination of the broadcast
|
||
|
|
and cascade configurations allows for this when replicating the journal entries
|
||
|
|
from a single system to multiple other systems. For example, replicating a
|
||
|
|
local journal to a single remote journal on a target system will minimize
|
||
|
|
the replication cost on the primary system. Then, from the target system,
|
||
|
|
the replicated journal can be asynchronously replicated by either a broadcast
|
||
|
|
or cascade configuration to other remote journals on other systems. This allows
|
||
|
|
all of the journal entries to be known to all desired systems, while requiring
|
||
|
|
a minimal amount of processing on the primary system.</p>
|
||
|
|
<p>The following characteristics apply to local journals and to any journal
|
||
|
|
receivers that were attached to local journals:</p>
|
||
|
|
<ul><li>Objects can be journaled to local journals.</li>
|
||
|
|
<li>Journal entries can be directly deposited to local journals. For example,
|
||
|
|
the Send Journal Entry (SNDJRNE) command or the Send Journal Entry (QJOSJRNE)
|
||
|
|
API can be used to send journal entries directly to a local journal.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The following characteristics apply to remote journals and to any journal
|
||
|
|
receivers that were attached to remote journals:</p>
|
||
|
|
<ul><li>Objects cannot be journaled to remote journals.</li>
|
||
|
|
<li>Journal entries cannot be directly deposited to remote journals. For example,
|
||
|
|
the Send Journal Entry (SNDJRNE) command or API (QJOSJRNE) cannot be used
|
||
|
|
to send journal entries directly to a remote journal.</li>
|
||
|
|
<li>Journal entries are only replicated to remote journals from an associated <span class="uicontrol">source
|
||
|
|
journal</span>. A source journal is the journal on the source system
|
||
|
|
to which a remote journal has been added. A source journal can be either a
|
||
|
|
local or a remote journal.</li>
|
||
|
|
<li>The information in the journal entries such as time stamps, system name,
|
||
|
|
and qualified journal receiver names reflect information as deposited in the
|
||
|
|
local journal for this remote journal network.</li>
|
||
|
|
<li>The information in the journal receiver such as attach time and detach
|
||
|
|
time reflect the information as it is for the local journal for the remote
|
||
|
|
journal network.</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Certain attributes of the remote journal are fixed and determined
|
||
|
|
based on the source journal, such as the values for the journal receiver,
|
||
|
|
manage receiver, manage receiver delay, receiver size options, journal cache,
|
||
|
|
fix length data, threshold, journal object limit, and journal recovery count.
|
||
|
|
These attributes cannot be changed because either they do not apply for a
|
||
|
|
remote journal or they can only be changed by changing the attributes of the
|
||
|
|
source journal. <img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakirconcepts.htm" title="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.">Remote journal concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakiaddprocess.htm" title="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.">Add remote journal process</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|