Managing A Business Contiuity Cluster; Migrating A Cluster Resource To A Peer Cluster; Understanding Bcc Resource Migration - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION Administration Manual

Managing a Business Contiuity
7
Cluster
This section can help you effectively manage a business continuity cluster with the Novell
Business Continuity Clustering software. It describes how to migrate cluster resources from one
Novell Cluster Services
TM
generate reports of the cluster configuration and status.
For information about using console commands to manage your business continuity cluster, see
Appendix A, "Console Commands for BCC," on page
Section 7.1, "Migrating a Cluster Resource to a Peer Cluster," on page 83
Section 7.2, "Changing Cluster Peer Credentials," on page 84
Section 7.3, "Viewing the Current Status of a Business Continuity Cluster," on page 85
Section 7.4, "Generating a Cluster Report," on page 86
Section 7.5, "Disabling Business Continuity Cluster Resources," on page 86
Section 7.6, "Resolving Business Continuity Cluster Failures," on page 87
7.1 Migrating a Cluster Resource to a Peer
Cluster
Although Novell Business Continuity Clustering provides an automatic failover feature that fails
over resources between peer clusters, we recommend that you manually migrate cluster resources
between the peer clusters instead. For information about configuring and using automatic failover
for a business continuity cluster,
Section 7.1.1, "Understanding BCC Resource Migration," on page 83
Section 7.1.2, "Migrating Cluster Resources between Clusters," on page 84

7.1.1 Understanding BCC Resource Migration

If the node where a resource is running fails, if the entire cluster fails, or if you just want to migrate
the resource to another cluster, you can manually start the cluster resource on another cluster in the
business continuity cluster. If the source cluster site fails, you must go to the destination cluster site
to manually migrate or bring up resources at that site. Each resource starts on its preferred node on
the destination cluster.
Migrating a pool resource to another cluster causes the following to happen:
1. If the source cluster can be contacted, the state of the resource is changed to offline.
2. The resource changes from primary to secondary on the source cluster.
3. Any SAN script that is associated with the pool resource is run.
4. On the destination cluster, the resource changes from secondary to primary so that it can be
brought online.
cluster to another, to modify peer credentials for existing clusters, and to
Appendix C, "Setting Up Auto-Failover," on page
123.

Managing a Business Contiuity Cluster

7
®
133.
83