64 lines
5.2 KiB
HTML
64 lines
5.2 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="Managing the processing of cluster resource groups" />
|
|
<meta name="abstract" content="When a node failure occurs, a failover will occur. When sequencing of CRGs occurs, all device CRGs fail over first, then all data CRGs and lastly application CRGs. For peer CRG, there is no sequence order, but each node is notified when a failure occurs." />
|
|
<meta name="description" content="When a node failure occurs, a failover will occur. When sequencing of CRGs occurs, all device CRGs fail over first, then all data CRGs and lastly application CRGs. For peer CRG, there is no sequence order, but each node is notified when a failure occurs." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptselements.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsfailover.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsswitchover.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsrecoverydomain.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsexitprograms.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="rzaigconceptscrgmanageprocessing" />
|
|
<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>Managing the processing of cluster resource groups</title>
|
|
</head>
|
|
<body id="rzaigconceptscrgmanageprocessing"><a name="rzaigconceptscrgmanageprocessing"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Managing the processing of cluster resource groups</h1>
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />When a node failure occurs, a failover will
|
|
occur. When sequencing of CRGs occurs, all device CRGs fail over first, then
|
|
all data CRGs and lastly application CRGs. For peer CRG, there is no sequence
|
|
order, but each node is notified when a failure occurs.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
|
<p><img src="./delta.gif" alt="Start of change" />You can verify that the cluster resource group has completed
|
|
failover or switchover by checking the status of the CRG.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
<p>You can also use blocking to hold the application until the data is available
|
|
to be processed. While the data-resilient cluster resource groups are being
|
|
processed, you may want to block access to the data represented by the data
|
|
CRG. You can block access by using the <a href="../apis/qxdablok.htm"><span class="apiname">Block EDRS Access (QxdaBlockEDRS)</span> API </a> and
|
|
the <a href="../apis/qxdachek.htm"><span class="apiname">Check
|
|
EDRS Block Status (QxdaCheckEDRSBlock)</span> API</a>. If a failover
|
|
or switchover should occur, you can block and unblock access from within the
|
|
cluster resource group exit program using these APIs.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigconceptselements.htm" title="An iSeries cluster is a collection of one or more systems or partitions that work together as a single system. Use this information to understand the elements and their relationship to each other.">The elements of a cluster</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaigconceptsfailover.htm" title="Failover occurs when a server in a cluster automatically switches over to one or more backup servers in the event of a system failure.">Failover</a></div>
|
|
<div><a href="rzaigconceptsrecoverydomain.htm" title="A recovery domain is a subset of cluster nodes that are grouped together in a cluster resource group (CRG) for a common purpose such as performing a recovery action or synchronizing events.">Recovery domain</a></div>
|
|
<div><a href="rzaigconceptsexitprograms.htm" title="A cluster resource group exit program is called after a cluster-related event for a CRG occurs.">Cluster resource group exit programs</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzaigconceptsswitchover.htm" title="Switchover happens when you manually switch access to a resource from one server to another.">Switchover</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |