99 lines
6.6 KiB
HTML
99 lines
6.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="task" />
|
||
|
|
<meta name="DC.Title" content="Tips: Cluster partitions" />
|
||
|
|
<meta name="abstract" content="Use these tips for cluster partitions." />
|
||
|
|
<meta name="description" content="Use these tips for cluster partitions." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootpartitionerrors.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootchangepartitionednodes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/clcntdltc.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="rzaigtroubleshoottipclusterpartitions" />
|
||
|
|
<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>Tips: Cluster partitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigtroubleshoottipclusterpartitions"><a name="rzaigtroubleshoottipclusterpartitions"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Tips: Cluster partitions</h1>
|
||
|
|
<div><p>Use these tips for cluster partitions.</p>
|
||
|
|
<ol><li class="stepexpand"><span>The rules for restricting operations within a partition are designed
|
||
|
|
to make merging the partitions feasible. Without these restrictions, reconstructing
|
||
|
|
the cluster requires extensive work.</span></li>
|
||
|
|
<li class="stepexpand"><span>If the nodes in the primary partition have been destroyed, special
|
||
|
|
processing may be necessary in a secondary partition. The most common scenario
|
||
|
|
that causes this condition is the loss of the site that made up the
|
||
|
|
primary partition. Use the example in recovering from partition errors and
|
||
|
|
assume that Partition 1 was destroyed. In this case, the primary node for
|
||
|
|
Cluster Resource Groups B, C, and D must be located in Partition 2. The simplest
|
||
|
|
recovery is to use Change Cluster Node Entry to set both Node A and Node B
|
||
|
|
to failed. See changing partitioned nodes to failed for more information about
|
||
|
|
how to do this. Recovery can also be achieved manually. In order to do this,
|
||
|
|
perform these operations:</span><ol type="a"><li><span>Remove Nodes A and B from the cluster in Partition 2. Partition
|
||
|
|
2 is now the cluster.</span></li>
|
||
|
|
<li><span>Establish any logical replication environments needed in the new cluster.
|
||
|
|
IE. Start Cluster Resource Group API/CL command, and so on.</span></li>
|
||
|
|
</ol>
|
||
|
|
<p>Since nodes have been removed from the cluster definition in Partition
|
||
|
|
2, an attempt to merge Partition 1 and Partition 2 will fail. In order to
|
||
|
|
correct the mismatch in cluster definitions, run the <a href="../apis/clcntdltc.htm"><span class="apiname">Delete Cluster (QcstDeleteCluster)</span> API</a> on
|
||
|
|
each node in Partition 1. Then add the nodes from Partition 1 to the cluster,
|
||
|
|
and reestablish all the cluster resource group definitions, recovery domains,
|
||
|
|
and logical replication. This requires a great deal of work and is also prone to errors.
|
||
|
|
It is very important that you do this procedure only in a site loss situation.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Processing a start node operation is dependent on the status of
|
||
|
|
the node that is being started: </span> <p>The node either failed or an
|
||
|
|
End Node operation ended the node:</p>
|
||
|
|
<ol type="a"><li><span>Cluster resource services is started on the node that is being
|
||
|
|
added</span></li>
|
||
|
|
<li><span>Cluster definition is copied from an active node in the cluster
|
||
|
|
to the node that is being started.</span></li>
|
||
|
|
<li><span>Any cluster resource group that has the node being started in
|
||
|
|
the recovery domain is copied from an active node in the cluster to the node
|
||
|
|
being started. No cluster resource groups are copied from the node that is
|
||
|
|
being started to an active node in the cluster.</span></li>
|
||
|
|
</ol>
|
||
|
|
<p>The node is a partitioned node:</p>
|
||
|
|
<ol type="a"><li><span>The cluster definition of an active node is compared to the
|
||
|
|
cluster definition of the node that is being started. If the definitions are
|
||
|
|
the same, the start will continue as a merge operation. If the definitions
|
||
|
|
do not match, the merge will stop, and the user will need to intervene.</span></li>
|
||
|
|
<li><span>If the merge continues, the node that is being started is set
|
||
|
|
to an active status.</span></li>
|
||
|
|
<li><span>Any cluster resource group that has the node being started in
|
||
|
|
the recovery domain is copied from the primary partition of the cluster resource
|
||
|
|
group to the secondary partition of the cluster resource group. Cluster resource
|
||
|
|
groups may be copied from the node that is being started to nodes that are
|
||
|
|
already active in the cluster.</span></li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigtroubleshootpartitionerrors.htm" title="Certain cluster conditions are easily corrected. If a cluster partition has occurred, you can learn how to recover. This topic also tells you how to avoid a cluster partition and gives you an example of how to merge partitions back together.">Partition errors</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaigtroubleshootchangepartitionednodes.htm" title="Sometimes, a partitioned condition is reported when there really was a node outage. This can occur when cluster resource services loses communications with one or more nodes, but cannot detect if the nodes are still operational. When this condition occurs, a simple mechanism exists for you to indicate that the node has failed.">Change partitioned nodes to failed</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../apis/clcntdltc.htm">Delete Cluster (QcstDeleteCluster) API</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|