72 lines
5.1 KiB
HTML
72 lines
5.1 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="Plan for logical replication" />
|
|
<meta name="abstract" content="Multiple copies of the data are maintained with logical replication. Data is replicated, or copied, from the primary node in the cluster to the backup nodes designated in the recovery domain. When an outage occurs on the primary node, the data remains available as a designated backup node takes over as the primary point of access." />
|
|
<meta name="description" content="Multiple copies of the data are maintained with logical replication. Data is replicated, or copied, from the primary node in the cluster to the backup nodes designated in the recovery domain. When an outage occurs on the primary node, the data remains available as a designated backup node takes over as the primary point of access." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandataresilience.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandeterminesysreplication.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaigplanreplication" />
|
|
<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>Plan for logical replication</title>
|
|
</head>
|
|
<body id="rzaigplanreplication"><a name="rzaigplanreplication"><!-- --></a>
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Plan for logical replication</h1>
|
|
<div><p>Multiple copies of the data are maintained with logical replication.
|
|
Data is replicated, or copied, from the primary node in the cluster to the
|
|
backup nodes designated in the recovery domain. When an outage occurs on the
|
|
primary node, the data remains available as a designated backup node takes
|
|
over as the primary point of access.</p>
|
|
<p><strong>Replication</strong> makes a copy of something in real time. It is the process
|
|
of copying objects from one node in a cluster to one or more other nodes in
|
|
the cluster. Replication makes and keeps the objects on your systems identical.
|
|
If you make a change to an object on one node in a cluster, this change is
|
|
replicated to other nodes in the cluster.</p>
|
|
<p>You must decide on a software technology to use for logical replication.
|
|
The following solutions are available for achieving logical replication in
|
|
your cluster:</p>
|
|
<ul><li><strong>IBM Business Partners products</strong> <p>Data replication software from
|
|
recognized cluster IBM Business Partners enables you to replicate objects
|
|
across multiple nodes. See <a href="rzaigplanmiddlewarebps.htm">Cluster middleware IBM Business Partners and available clustering products</a> for details.</p>
|
|
</li>
|
|
<li><strong>A custom-written replication application</strong> <p>IBM<sup>®</sup> journal management provides a means
|
|
by which you can record the activity of objects on your system. You can write
|
|
an application taking advantage of journal management to achieve logical replication.
|
|
See iSeries™ journal
|
|
management for details on how journal management works.</p>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaigplandeterminesysreplication.htm">Determine which systems to use for logical replication</a></strong><br />
|
|
When you are determining which systems to use for logical replication, there are several key considerations.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplandataresilience.htm" title="Data resilience is achieved when data is always available to an user or application. You can achieve data resilience through the use of logical replication or switchable independent disk pools.">Plan for data resilience</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="../rzaki/rzakikickoff.htm">Journal management</a></div>
|
|
</div>
|
|
</div>
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
|
</html> |