75 lines
5.6 KiB
HTML
75 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="topic" />
|
||
|
|
<meta name="DC.Title" content="Scenarios: Remote journal management and recovery" />
|
||
|
|
<meta name="abstract" content="These scenarios describe the possible ways that JKL Toy Company can use remote journal management. JKL Toy Company uses the server JKLINT as their web server." />
|
||
|
|
<meta name="description" content="These scenarios describe the possible ways that JKL Toy Company can use remote journal management. JKL Toy Company uses the server JKLINT as their web server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiremotekickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirdatarep.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihotbackup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirecovery.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirecovdtails.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijklint.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijournalscenario.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="rzakirscenarios" />
|
||
|
|
<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>Scenarios: Remote journal management and recovery</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakirscenarios"><a name="rzakirscenarios"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenarios: Remote journal management and recovery</h1>
|
||
|
|
<div><p>These scenarios describe the possible ways that JKL Toy Company
|
||
|
|
can use remote journal management. JKL Toy Company uses the server JKLINT
|
||
|
|
as their web server.</p>
|
||
|
|
<p>They need 24x7 availability for the critical data on this server, and they
|
||
|
|
accomplish that by having a second server, JKLINT2, that shadows JKLINT. They
|
||
|
|
use a high availability replication solution to copy the data from JKLINT
|
||
|
|
to JKLINT2. Then, if JKLINT goes down, they can switch to JKLINT2.</p>
|
||
|
|
<p>The following scenarios describe two possible environments in which they
|
||
|
|
can use remote journaling. The first scenario describes how JKL Toy Company
|
||
|
|
can set up a data replication environment. The second scenario describes how
|
||
|
|
they set up a hot-backup environment. The third scenario describes recovery
|
||
|
|
steps if one of the servers fails.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Scenario: Journal management contains a complete description
|
||
|
|
of JKL Toy Company's network and their overall strategy for journaling.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakirdatarep.htm">Scenario: Data replication environment for remote journals</a></strong><br />
|
||
|
|
In this scenario, JKLINT and JKLINT2 use remote journaling for data replication purposes only.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakihotbackup.htm">Scenario: Hot-backup environment</a></strong><br />
|
||
|
|
In this scenario, the remote journaling environment uses a hot-backup application that causes JKLINT2 to replace JKLINT in the case that JKLINT has a failure.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakirecovery.htm">Scenario: Recovery for remote journaling</a></strong><br />
|
||
|
|
This scenario describes a hot-backup environment in which the local system, JKLINT fails. It is necessary to restore the local system, and synchronize it with the remote system, JKLINT2.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakirecovdtails.htm">Details: Recovery for remote journaling scenario</a></strong><br />
|
||
|
|
A description of the recovery process for remote journaling.</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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijklint.htm" title="JKLINT is the system that JKL uses for their Web site and e-mail. While this data is critical to their business, it is fairly static.">JKLINT</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="rzakijournalscenario.htm" title="Provides the steps that a fictitious company, JKL Toy company, takes as it implements journal management on its iSeries server.">Scenario: Journal management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|