Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION, Administration Manual

Page: 34 / 142

34 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8
no
vd
ocx
(e
n)
13
Ma
y 20
09
3.6.6 Naming Conventions for BCC-Enabled Resources
Develop a cluster-independent naming convention for BCC-enabled cluster resources. It can
become confusing if the cluster resource name refers to one cluster and is failed over to a peer
cluster.
You can use a naming convention for resources in your BCC as you create those resources.
Changing existing names of cluster resources is less straightforward and can be error prone.
For example, when cluster-enabling NSS pools the default naming conventions used by NSS are:
Cluster Resource:
poolname_SERVER
Cluster-Enabled Pool:
clustername _ poolname _POOL
Cluster-Enabled Volume:
clustername _ volumename
Virtual Server:
clustername _ poolname _SERVER
Instead, use names that are independent of the clusters and that are unique across all peer clusters.
For example, replace the
clustername with something static such as BCC.
Cluster Resource:
poolname_SERVER
Cluster-Enabled Pool:
BCC_ poolname _POOL
Cluster-Enabled Volume:
BCC_ volumename
Virtual Server:
BCC_ poolname _SERVER
Resources have an identity in each peer cluster, and the names are the same in each peer cluster. For
example,
Figure 3-2 shows the cluster resource identity in each of two peer clusters.
Figure 3-2
Cluster Resource Identity in Two Clusters
3.7 Cluster Design Guidelines
Your Novell Cluster Services solution for each of the peer clusters in the business continuity cluster
must consider the following configuration guidelines. Make sure your approach is consistent across
all peer clusters.
Š IP address assignments should be consistently applied within each peer cluster and for all
cluster resources.
Š
Ensure that IP addresses are unique across all BCC peer clusters.