59 lines
4.0 KiB
HTML
59 lines
4.0 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="Comparison between primary-backup and peer models" />
|
|||
|
|
<meta name="abstract" content="Primary-backup CRGs and peer CRGs provide resiliency for resources within a cluster; however, it is important to understand their differences and uses." />
|
|||
|
|
<meta name="description" content="Primary-backup CRGs and peer CRGs provide resiliency for resources within a cluster; however, it is important to understand their differences and uses." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandesign.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="rzaigcompareprimary" />
|
|||
|
|
<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>Comparison between primary-backup and peer models </title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzaigcompareprimary"><a name="rzaigcompareprimary"><!-- --></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">Comparison between primary-backup and peer models </h1>
|
|||
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />Primary-backup CRGs and peer CRGs provide resiliency
|
|||
|
|
for resources within a cluster; however, it is important to understand their
|
|||
|
|
differences and uses.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
|||
|
|
<p> Clusters support two models for defining CRGs in your environment. Roles
|
|||
|
|
are defined for both primary-backup and peer models. In primary-backup model,
|
|||
|
|
they need to define an order. Nodes that are defined as backup nodes provide
|
|||
|
|
access to resources on the primary node in the event of a node failure. With
|
|||
|
|
the peer model, each node are equal in the role and can provide access for
|
|||
|
|
the resource; however there is no concept of order.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Primary-backup model</h4><p>With the primary-backup model,
|
|||
|
|
users must define the node as either a either primary, backup, or replicate
|
|||
|
|
role. These roles are defined and managed within the recovery domain. If a
|
|||
|
|
node has been defined as the primary access point for the resource, then other
|
|||
|
|
nodes provide backup if the primary node fails. </p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Peer model</h4><p><img src="./delta.gif" alt="Start of change" />Peer model CRGs eliminate
|
|||
|
|
the need to define an ordered recovery domain. For a peer model, nodes
|
|||
|
|
can be defined as either peer or replicate. If nodes defined as peer, then
|
|||
|
|
all the nodes in the recovery domain are equal and can provide the access
|
|||
|
|
point for the resource. <img src="./deltaend.gif" alt="End of change" /></p>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplandesign.htm" title="Identify your needs to determine how to design your cluster.">Design your cluster</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
|||
|
|
</html>
|