Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION Manual page 14

Table of Contents

Advertisement

Implementation Comparison
Table 1-1
Advantages
Disadvantages
14
Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
Disaster Recovery Implementation Comparison
Stretch Cluster
It automatically fails over.
It is easier to manage than
separate clusters.
Failure of site interconnect can
result in LUNs becoming primary
at both locations (split brain
problem) if host-based mirroring
is used.
An SBD partition must be
mirrored between sites.
It accommodates only two sites.
All IP addresses must reside in
the same subnet.
The eDirectory partition must
span the cluster.
Cluster of Clusters
The chance of LUNs at both
locations becoming primary is
minimized.
eDirectory partitions don't need
to span the cluster.
Each cluster can be in a
separate eDirectory tree.
IP addresses for each cluster
can be on different IP subnets.
It accommodates more than two
sites and cluster resources can
fail over to separate clusters
(multiple-site fan-out failover
support).
SBD partitions are not mirrored
between sites.
Resource configurations must be
kept in sync manually.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Table of Contents