Business Continuity Cluster Failure Types - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR OPEN ENTERPRISE SERVER 1 SP2 LINUX Administration Manual

Console Command
cluster resetresources
cluster view
cluster resources [resource]
cluster status
cluster connections [-a]
cluster refresh

2.6 Business Continuity Cluster Failure Types

There are several failure types associated with a business continuity cluster that you should be aware
of. Understanding the failure types and knowing how to respond to each can help you more quickly
recover a cluster. Some of the failure types and responses differ depending on whether you have
implemented SAN-based mirroring or host-based mirroring. Promoting or demoting LUNs is
sometimes necessary when responding to certain types of failures.
NOTE: The terms promote and demote are used here in describing the process of changing LUNs to
a state of primary or secondary, but your SAN vendor documentation might use different terms such
as mask and unmask.

Section 2.6.1, "SAN-Based Mirroring Failure Types and Responses," on page 55

Section 2.6.2, "Host-based Mirroring Failure Types and Responses," on page 56
54 Novell Business Continuity Clustering 1.1 Administration Guide for Linux
Description
Changes the state of all resources on this cluster to
offline and secondary. This is a recovery procedure
that should be run when a cluster in a BCC is brought
back into service.
You should run this command when only one node is
a member of the cluster.
1. After a failure, bring up one node in the cluster.
All other nodes should remain powered off.
2. Run the
cluster resetresources
command.
3. Bring up the remaining nodes in the cluster.
Displays the node name, cluster epoch number,
master node name, a list of nodes that are currently
members of the cluster, and peer clusters if this
cluster is a member of a Business Continuity Cluster.
Lets you view the state and location of cluster
resources and whether resources are primary or
secondary. You can optionally specify a specific
resource name.
Lets you view the state and location of cluster
resources and whether resources are primary or
secondary. If the resource state is primary, the node
where the resource is running is displayed. If the
resource state is secondary, the cluster where the
resource is located is displayed.
Displays the connection status of the cluster.
Specifying attempts to show the connection status
-a
of all clusters in the BCC.
This command should not be used except under the
direction of Novell Support.