Installation and Setup
41
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
After the
trustees.xml
file has been modified on all NetWare nodes, the NetWare nodes
must be rebooted. This can be done in a rolling fashion. You should start with the node that has
the highest IP address first and work down in IP address order. This will speed the rate at which
the NCS master node acquires the change.
2.5.3 Configuring Cluster Resources for Business Continuity
Cluster resources can be configured for business continuity either at the same time they are created
or after they are created. Configuring a resource for business continuity consists of enabling that
resource for business continuity, adding load and unload script search and replace data specific to
the resource, and selecting peer clusters for the resource.
IMPORTANT:
In a business continuity cluster, you should have only one NSS pool for each LUN
that could be failed over to another cluster. This is necessary because in a business continuity cluster,
entire LUNs fail over to other clusters, rather than individual pools, which fail over to other nodes
within a cluster.
A cluster-enabled NSS pool must contain at least one volume before it can be enabled for BCC. You
will get an error message if you attempt to BCC-enable an NSS pool that does not contain a volume.
Also, if you have encrypted NSS volumes in your BCC, then all clusters in that BCC MUST be in
the same eDirectory tree. If not, then the clusters in the other eDirectory tree will not be able to
decrypt the NSS volumes. This rule applies to both NetWare and Linux BCCs
Enabling a Cluster Resource for Business Continuity
Cluster resources must be enabled for business continuity on the primary cluster before they can be
synchronized and appear as resources in the other clusters in the business continuity cluster.
Enabling a cluster resource makes it possible for that cluster resource or cluster pool resource to be
migrated to another cluster.
IMPORTANT:
Although you can add search and replace data that is resource-specific after you
enable a resource for business continuity, we recommend adding the search and replace data for the
entire cluster before you enable resources for business continuity. See
“Adding Resource Script
Search and Replace Values” on page 36
for instructions on adding search and replace data for the
entire cluster.
When you enable a resource for business continuity and that resource has been synchronized and
appears in the other clusters, the preferred nodes for the other clusters will by default be set to all
nodes in the cluster. If you want to change the resource’s preferred nodes for other clusters in your
BCC, you must manually do it. Changes to the preferred nodes list in the primary cluster do not
automatically replicate to the preferred nodes lists for other clusters in your BCC.
1
(Conditional) If you are creating a new cluster resource or cluster pool resource, follow the
instructions for creating a cluster resource or cluster pool resource using iManager in the
OES
Novell Cluster Services 1.8.2 Administration Guide for NetWare
, then continue with
Step 3
below.
If you have Business Continuity Clustering software installed and configured, at the end of the
resource creation process, the wizard for creating a cluster resource will display a page for
enabling the resource for business continuity.
