ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaki_5.4.0.1/rzakisaverestre.htm

68 lines
5.6 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="Considerations for save and restore operations with remote journals" />
<meta name="abstract" content="The following information describes general considerations for save and restore operations with remote journals:" />
<meta name="description" content="The following information describes general considerations for save and restore operations with remote journals:" />
<meta name="DC.Relation" scheme="URI" content="rzakirmanage.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakirsaveconsid.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakirsavconsidrcv.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakisavrstorejrn.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakirsavstg.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakitwotypes.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakiifsissue.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="rzakisaverestre" />
<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>Considerations for save and restore operations with remote journals</title>
</head>
<body id="rzakisaverestre"><a name="rzakisaverestre"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Considerations for save and restore operations with remote journals</h1>
<div><p>The following information describes general considerations for
save and restore operations with remote journals:</p>
<ul><li>Rules for saving and restoring journals</li>
<li>Rules for saving and restoring journal receivers</li>
<li>File identifier considerations for working with integrated file system
entries</li>
<li>Considerations for restoring journaled objects</li>
<li>Considerations for restoring objects saved with SAVSTG</li>
</ul>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzakirsaveconsid.htm">Rules for saving and restoring journals</a></strong><br />
It is recommended that you save the remote journal network after the addition of any and all remote journals that will be associated with the journal. This includes saving the local journal and any associated remote journals, as well as the journal receivers that are associated with the local journal.</li>
<li class="ulchildlink"><strong><a href="rzakirsavconsidrcv.htm">Rules for saving and restoring journal receivers</a></strong><br />
The restore relationships for journal receivers associated with remote journals are described in this topic.</li>
<li class="ulchildlink"><strong><a href="rzakisavrstorejrn.htm">Considerations for restoring journaled objects</a></strong><br />
For an object that is restored and associated with a local journal in standby state, journaling starts for that object, but no restore entry is deposited in the journal receiver. If the object is being restored-over and is currently journaled to a local journal in standby state, the restore is not prevented, and no restore entry is deposited in the journal receiver.</li>
<li class="ulchildlink"><strong><a href="rzakirsavstg.htm">Considerations for restoring objects saved with SAVSTG</a></strong><br />
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.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakirmanage.htm" title="Managing the remote journal function requires basic tasks such as:">Manage 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="rzakiifsissue.htm" title="If you plan to replay the integrated file system operations in the remote journal to objects on the target system, and if you primed that target system with objects that were restored from the source system, then some additional considerations apply to replaying those journal entries.">File identifier considerations for working with integrated file system entries</a></div>
</div>
</div>
</body>
</html>