177 lines
11 KiB
HTML
177 lines
11 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="task" />
|
||
|
|
<meta name="DC.Title" content="Rules for saving and restoring journal receivers" />
|
||
|
|
<meta name="abstract" content="The restore relationships for journal receivers associated with remote journals are described in this topic." />
|
||
|
|
<meta name="description" content="The restore relationships for journal receivers associated with remote journals are described in this topic." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisaverestre.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakitwotypes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirsavstg.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="rzakirsavconsidrcv" />
|
||
|
|
<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>Rules for saving and restoring journal receivers</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakirsavconsidrcv"><a name="rzakirsavconsidrcv"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Rules for saving and restoring journal receivers</h1>
|
||
|
|
<div><p>The restore relationships for journal receivers associated with
|
||
|
|
remote journals are described in this topic.</p>
|
||
|
|
<div class="section"><p>The following figure illustrates the restore relationships for
|
||
|
|
journal receivers that are associated with remote journals, based on the remote
|
||
|
|
journal type.</p>
|
||
|
|
<br /><img src="rzaki517.gif" longdesc="rzakidesc_3.htm" alt="Restore relationships for journal receivers and remote journals." /><br /><p><img src="c.gif" alt="Image description" /> </p>
|
||
|
|
<p>There
|
||
|
|
are several unique rules which govern where the journal receivers that are
|
||
|
|
associated with a remote journal can be restored. The rules also discuss the
|
||
|
|
placement of the journal receivers in the receiver directory chain of a local
|
||
|
|
or remote journal. These rules are influenced by the remote journal type of
|
||
|
|
the journal to which the journal receiver was attached. These rules are also
|
||
|
|
influenced by the library redirection that was in effect when that receiver
|
||
|
|
was attached. See Types of remote journals.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> You can always save receivers
|
||
|
|
from a journal, and then restore the receivers to another local journal of
|
||
|
|
the same name. However, they will be placed in their own separate receiver
|
||
|
|
chain.</div>
|
||
|
|
<p>The following items describe the rules that the system uses
|
||
|
|
when restoring journal receivers:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>The system first attempts to find an appropriate remote journal.
|
||
|
|
When searching for a remote journal, the system follows the following rules:</span><ol type="a"><li class="substepexpand"><span>If the saved receiver was originally associated with a local
|
||
|
|
or *TYPE1 remote journal, then the system searches for a *TYPE1 remote journal.</span> <ol type="i"><li>If a *TYPE1 remote journal was defined at the time this receiver was attached,
|
||
|
|
then use the journal and receiver library redirection that was in effect and
|
||
|
|
saved with the receiver. If no *TYPE1 remote journal was defined at the time
|
||
|
|
this receiver was attached, then the original journal library and receiver
|
||
|
|
library names will be used when searching for the *TYPE1 remote journal.</li>
|
||
|
|
<li>If a *TYPE1 remote journal is found, and the current receiver library
|
||
|
|
redirection for the found *TYPE1 remote journal matches the library name where
|
||
|
|
the receiver is being restored, the journal receiver will be associated with
|
||
|
|
the found *TYPE1 remote journal.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li class="substepexpand"><span>If the receiver was originally associated with a *TYPE2 remote
|
||
|
|
journal, then the system searches for a *TYPE2 remote journal. When searching
|
||
|
|
for the *TYPE2 remote journal, a journal with the same name as the name that
|
||
|
|
was saved with the receiver will be used.</span> <ol type="i"><li>The journal receiver will be associated with a found *TYPE2 remote journal
|
||
|
|
if the following conditions are met: <ul><li>A *TYPE2 remote journal is found with the correct name in the correct
|
||
|
|
library.</li>
|
||
|
|
<li>The found journal is in the exact same remote journal network as that
|
||
|
|
of the saved receiver.</li>
|
||
|
|
<li>The receiver is being restored to the same named system or same named
|
||
|
|
ASP group as the name of the system or ASP group at the time the receiver
|
||
|
|
was saved.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>If a remote journal was not found, then the system searches for
|
||
|
|
a local journal. When searching for a local journal, the original journal
|
||
|
|
and journal library names are used.</span> <p>The journal receiver will
|
||
|
|
be associated with a found local journal if the following conditions are met:</p>
|
||
|
|
<ul><li>A local journal is found by the correct name in the correct library.</li>
|
||
|
|
<li>The original journal receiver library name for the found journal matches
|
||
|
|
the library name where the receiver is being restored.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>If a local journal cannot be found, the restore operation will
|
||
|
|
be allowed to proceed. The journal receiver will not be associated with any
|
||
|
|
journal, if the receiver is being restored to the original or redirected receiver
|
||
|
|
library.</span></li>
|
||
|
|
<li class="stepexpand"><span>Still honoring the previous receiver restore rules, the following
|
||
|
|
must also be true if the receiver is being restored over an existing receiver:</span><ol type="a"><li class="substepexpand"><span>If the receiver is not being associated with any journal (as
|
||
|
|
previously determined from the prior receiver restored rules), then following
|
||
|
|
items apply:</span> <ol type="i"><li>The receiver creation time stamps must match.</li>
|
||
|
|
<li>If the saved receiver was ever associated with a journal, then it must
|
||
|
|
have been previously associated with a journal of the same type as that of
|
||
|
|
the existing receiver.</li>
|
||
|
|
<li>If the saved receiver was ever associated with a remote journal network,
|
||
|
|
then it must have been previously associated with the same remote journal
|
||
|
|
network as that of the existing receiver.</li>
|
||
|
|
<li>The saved receiver must have at least as many entries as the existing
|
||
|
|
receiver.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li class="substepexpand"><span>If the receiver is being associated with a local journal, then
|
||
|
|
the following items apply: </span> <ol type="i"><li>If the saved receiver was originally associated with a local journal,
|
||
|
|
then the receiver creation time stamps must match.</li>
|
||
|
|
<li>If the saved receiver was not originally associated with a local journal,
|
||
|
|
then the saved receiver must have been originally associated with the same
|
||
|
|
remote journal network as that of the existing receiver.</li>
|
||
|
|
<li>The saved receiver must have at least as many entries as the existing
|
||
|
|
receiver.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li class="substepexpand"><span>If the receiver is being associated with a *TYPE1 remote journal,
|
||
|
|
then the following items apply:</span> <ol type="i"><li>The receiver creation time stamps must match, and the saved receiver must
|
||
|
|
have been originally associated with a local or *TYPE1 remote journal.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li class="substepexpand"><span>If the receiver is being associated with a *TYPE2 remote journal,
|
||
|
|
then the following items apply:</span> <ol type="i"><li>The receiver creation time stamps must match, and the saved receiver must
|
||
|
|
have been originally associated with the same *TYPE2 remote journal.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>When receivers are saved from or restored to a target system and
|
||
|
|
associated with a remote journal, no journal entries are deposited to indicate
|
||
|
|
that the save or restore occurred. However, the object save and restored date
|
||
|
|
and time stamps are updated accordingly.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakisaverestre.htm" title="The following information describes general considerations for save and restore operations with remote journals:">Considerations for save and restore operations with remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakitwotypes.htm" title="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.">Types of remote journals</a></div>
|
||
|
|
<div><a href="rzakirsavstg.htm" title="If you restore a system from Save Storage (SAVSTG) media, the primary remote journal function concerns have to do with configuration changes involving additionally defined remote journals.">Considerations for restoring objects saved with SAVSTG</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" xml:lang="en-us" id="saverestoreconsiderations"><a name="saverestoreconsiderations"><!-- --></a><h2 class="topictitle2">Save and restore considerations</h2>
|
||
|
|
<div><div class="section"><dl><dt class="dlterm">Considerations for remote journal receivers</dt>
|
||
|
|
<dd>Do not save the receiver while it is attached to the remote journal. If
|
||
|
|
it is a long running save it can inhibit a change journal operation that was
|
||
|
|
initiated by the source and the remote journaling environment can time out
|
||
|
|
and fail.</dd>
|
||
|
|
<dt class="dlterm">Nonreplicated journal receiver protection considerations</dt>
|
||
|
|
<dd>The protection provided, which prevents journal receivers that are not
|
||
|
|
fully replicated to all associated remote journals from being deleted, is
|
||
|
|
removed when the journal receiver is restored.</dd>
|
||
|
|
<dt class="dlterm">Unconfirmed journal entries save considerations</dt>
|
||
|
|
<dd>When a journal receiver that is associated with a remote journal is saved,
|
||
|
|
only those journal entries which have been confirmed are saved to the media.
|
||
|
|
Therefore, no unconfirmed journal entries, nor any journal entries that would
|
||
|
|
not survive any IPL journal recovery processing, will be saved.</dd>
|
||
|
|
<dt class="dlterm">Journal receivers saved with STG(*FREE) considerations</dt>
|
||
|
|
<dd>Even if a journal receiver has not been fully sent to all known remote
|
||
|
|
journals, such a journal receiver can be saved with STG(*FREE). However, a
|
||
|
|
diagnostic message is left in the job log indicating the freeing of the journal
|
||
|
|
receiver storage without the journal receiver first being fully replicated
|
||
|
|
to all downstream remote journals. This is in contrast to the default action
|
||
|
|
taken when attempting to delete a receiver that has not been fully replicated
|
||
|
|
to all downstream remote journals.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|