Table of Contents
Advertisement
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:
Cluster-Enabled Pool:
Cluster-Enabled Volume:
Virtual 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:
Cluster-Enabled Pool:
Cluster-Enabled Volume:
Virtual Server:
Resources have an identity in each peer cluster, and the names are the same in each peer cluster. For
example,
Figure 3-2
Figure 3-2
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.
34
BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8
poolname_SERVER
clustername_poolname_POOL
clustername_volumename
clustername_poolname_SERVER
poolname_SERVER
BCC_poolname_POOL
BCC_volumename
BCC_poolname_SERVER
shows the cluster resource identity in each of two peer clusters.
Cluster Resource Identity in Two Clusters
Advertisement
Table of Contents
Need help?
Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION and is the answer not in the manual?
Questions and answers