67 lines
4.5 KiB
HTML
67 lines
4.5 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="Example: A simple, two-node cluster" />
|
||
|
|
<meta name="abstract" content="This configuration example describes a basic cluster that contains two nodes." />
|
||
|
|
<meta name="description" content="This configuration example describes a basic cluster that contains two nodes." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigscenarios.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="rzaigscenariossimpletwonode" />
|
||
|
|
<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>Example: A simple, two-node cluster</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigscenariossimpletwonode"><a name="rzaigscenariossimpletwonode"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: A simple, two-node cluster</h1>
|
||
|
|
<div><p>This configuration example describes a basic cluster that contains
|
||
|
|
two nodes.</p>
|
||
|
|
<p>This example configuration provides the following:</p>
|
||
|
|
<ul><li>One-way replication and failover</li>
|
||
|
|
<li>Two-tier environment</li>
|
||
|
|
<li>Applications and data move together</li>
|
||
|
|
<li>Backup used for offine processing of data</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Continuous operation on peer CRG<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
<br /><img src="rzaig503.gif" alt="A two-node cluster featuring an application CRG and a data CRG." /><br /><p><img src="./delta.gif" alt="Start of change" />Using this example, Node L is currently operating as the
|
||
|
|
primary node for two cluster resource groups, an application CRG and a data
|
||
|
|
CRG. It also contains a peer CRG that provide continuous operations for either
|
||
|
|
node. Two exit programs will be running periodically on Node L for the application
|
||
|
|
CRG. The reason two exit programs may be running at the same time is if you
|
||
|
|
call the Start CRG API, an exit program is started and runs continuously while
|
||
|
|
the application CRG is active. If you should call the End CRG API for the
|
||
|
|
application CRG, another exit program is then started. Node R is the first,
|
||
|
|
and only, backup node designated in the recovery domain of each cluster resource
|
||
|
|
group. Data that is associated with the data CRG and pertinent application
|
||
|
|
information that is associated with the application CRG is being replicated
|
||
|
|
from Node L to Node R. If Node L fails or needs to be taken down for administrative
|
||
|
|
reasons, then a failover or switchover is initiated and Node R becomes the
|
||
|
|
primary node for both the application and data CRGs. Node R will take over
|
||
|
|
the Internet Protocol (IP) address defined for the application CRG.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> While Node L is down, system availability is exposed because there is
|
||
|
|
no backup should Node R also fail. When Node L recovers and rejoins the cluster,
|
||
|
|
it is made the backup for both cluster resource groups. At that time, replication
|
||
|
|
will be from Node R to Node L. If you want Node L to resume the role of primary,
|
||
|
|
then an administrative switchover should be performed.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigscenarios.htm" title="Use these examples of typical cluster implementations to understand when, why, and how using clusters can be beneficial.">Examples: Cluster configurations</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|