18
BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
eDirectory Organizational Units
(OUs)
Single OU container for all nodes.
As a best practice, place the
cluster container in an OU
separate from the rest of the tree.
Each cluster can be in a different
OU. Each cluster is in a single
OU container.
As a best practice, place each
cluster container in an OU
separate from the rest of the tree.
IP subnet
IP addresses for nodes and
cluster resources must be in a
single IP subnet.
Because the subnet spans
multiple locations, you must
ensure that your switches handle
gratuitous ARP (Address
Resolution Protocol).
IP addresses in a given cluster
are in a single IP subnet. Each
cluster can use the same or
different IP subnet.
If you use the same subnet for all
clusters in the cluster of clusters,
you must ensure that your
switches handle gratuitous ARP.
SBD partition
A single SBD is mirrored between
two sites by using host-based
mirroring, which limits the
distance between data centers to
10 km.
Each cluster has its own SBD.
Each cluster can have an on-site
mirror of its SBD for high
availability.
If the cluster of clusters uses
host-based mirroring, the SBD is
not mirrored between sites, which
minimizes the chance of LUNs at
both locations becoming primary.
Failure of the site interconnect if
using host-based mirroring
LUNs might become primary at
both locations (split brain
problem).
Clusters continue to function
independently.
Storage subsystem
Each cluster accesses only the
storage subsystem on its own
site.
Each cluster accesses only the
storage subsystem on its own
site.
Data-block replication between
sites
For information about data
replication solutions, see
Section 1.2.2, “Host-Based
versus Storage-Based Data
Mirroring,” on page 14
.
Yes; typically uses storage-based
mirroring, but host-based
mirroring is possible for distances
up to 10 km.
Yes; typically uses storage-based
mirroring, but host-based
mirroring is possible for distances
up to 10 km.
Clustered services
A single service instance runs in
the cluster.
Each cluster can run an instance
of the service.
Cluster resource failover
Automatic failover to preferred
nodes at the other site.
Manual failover to preferred
nodes on one or multiple clusters
(multiple-site fan-out failover).
Failover requires additional
configuration.
Capability
Stretch Cluster
Cluster of Clusters
Содержание BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION
Страница 4: ...4 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 36: ...36 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 56: ...56 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 64: ...64 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 70: ...70 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 132: ...132 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 146: ...146 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 152: ...152 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 166: ...166 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 174: ...174 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 176: ...176 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 184: ...184 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...