53 lines
4.8 KiB
HTML
53 lines
4.8 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="Journals that are good candidates for remote journal management" />
|
||
|
|
<meta name="abstract" content="Journals that you are currently replicating, or that you plan to replicate, in their entirety to one or more systems, are excellent candidates for the remote journal function." />
|
||
|
|
<meta name="description" content="Journals that you are currently replicating, or that you plan to replicate, in their entirety to one or more systems, are excellent candidates for the remote journal function." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplanrjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanorsysmng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautodelete.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="rzakicandidates" />
|
||
|
|
<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>Journals that are good candidates for remote journal management</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakicandidates"><a name="rzakicandidates"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journals that are good candidates for remote journal management</h1>
|
||
|
|
<div><p>Journals that you are currently replicating, or that you plan to replicate, in their entirety to one or more systems, are excellent candidates for the remote journal function.</p>
|
||
|
|
<p>Journals with high activity that require frequent saves and deletes of the associated journal receivers during the day are also good candidates for the remote journal function. If you use remote journaling,
|
||
|
|
you can specify that the backup system takes over the journal receiver save processing. Then the primary system can specify system journal-receiver management and automatic deletion of journal receivers.
|
||
|
|
This frees up disk space on the primary system as quickly as possible. The backup system is the system where a replica of the original data is being maintained. The primary system is the system where the
|
||
|
|
original data resides.</p>
|
||
|
|
<p>Also, you might have applications that are so critical to your business that any downtime will impact your operations. The <span class="uicontrol">application dependent data</span> is a good candidate to protect
|
||
|
|
with the remote journal function. Application dependent data is any data that a particular application depends on if that application is interrupted and has to be restarted.</p>
|
||
|
|
<p>For example, you may have a database that has a lot of query activity that impacts your system performance. That local database is a good candidate to replicate to another system so that the query activity
|
||
|
|
moves from the local system to that remote system. The remote journal function can assist this process of replicating the database.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplanrjrn.htm" title="The following topics provide detailed information for planning to set up remote journals:">Plan for remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakimanorsysmng.htm" title="When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you can select to have either system managed or user managed journal receivers.">Manual versus system journal-receiver management</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>
|
||
|
|
</body>
|
||
|
|
</html>
|