Planning a Business Continuity Cluster
35
no
vd
ocx
(e
n)
13
Ma
y 20
09
Volume IDs must be unique across all peer clusters. Each cluster node automatically assigns
volume ID 0 to volume
SYS
and volume ID 1 to volume
_ADMIN
. Cluster-enabled volumes use
high volume IDs, starting from 254 in decending order. Novell Client uses the volume ID to
access a volume.
When existing clusters are configured and enabled within the same business continuity cluster,
the volume IDs for the existing shared volumes might also share the same volume IDs. To
resolve this conflict, manually edit the load script for each volume that has been enabled for
business continuity and change the volume IDs to unique values for each volume in the
business continuity cluster.
BCC configuration should consider the configuration requirements for each of the services
supported across all peer clusters.
Create failover matrixes for each cluster resource so that you know what service is supported
and which nodes are the preferred nodes for failover within the same cluster and among the
peer clusters.
Summary of Contents for BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION
Page 4: ...4 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 10: ...10 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 26: ...26 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 36: ...36 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 54: ...54 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 82: ...82 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 92: ...92 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 122: ...122 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 126: ...126 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...