Bcc Deployment Scenarios; Two-Site Business Continuity Cluster Solution - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION Administration Manual

Table of Contents

Novell Business Continuity Clustering software provides the following advantages over typical

cluster-of-clusters solutions:

Supports up to four clusters with up to 32 nodes each.

Integrates with shard storage hardware devices to automate the failover process through

standards-based mechanisms such as SMI-S.

Uses Novell Identity Manager technology to automatically synchronize and transfer cluster-

related eDirectory objects from one cluster to another, and between trees.

Provides the capability to fail over as few as one cluster resource, or as many as all cluster

resources.

Includes intelligent failover that allows you to perform site failover testing as a standard

practice.

Provides scripting capability that allows enhanced storage management control and

customization of migration and fail over between clusters.

Provides simplified business continuity cluster configuration and management by using the

browser-based Novell iManager management tool. iManager is used for the configuration and

monitoring of the overall system and for the individual resources.

1.4 BCC Deployment Scenarios

There are several Business Continuity Clustering deployment scenarios that can be used to achieve

the desired level of disaster recovery. Three possible scenarios include:

Section 1.4.1, "Two-Site Business Continuity Cluster Solution," on page 22

Section 1.4.2, "Multiple-Site Business Continuity Cluster Solution," on page 23

Section 1.4.3, "Low-Cost Business Continuity Cluster Solution," on page 24

The two-site business continuity cluster deploys two independent clusters at geographically separate

sites. Each cluster can support up to 32 nodes. The clusters can be designed in one of two ways:

Active Site/Active Site: Two active sites where each cluster supports different applications

and services. Either site can take over for the other site at any time.

Active Site/Passive Site: A primary site in which all services are normally active, and a

secondary site which is effectively idle. The data is mirrored to the secondary site, and the

applications and services are ready to load if needed.

The active/active deployment option is typically used in a company that has more than one large site

of operations. The active/passive deployment option is typically used when the purpose of the

secondary site is primarily testing by the IT department. Replication of data blocks is typically done

by SAN hardware, but it can be done by host-based mirroring for synchronous replication over short

distances up to 10 km.

BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8

Table of Contents

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