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 C.0, Setting Up Auto-Failover.

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.

    A custom Perl script can be created for disk mapping on Fibre Channel SANs. The purpose of this script is to make the LUNs in the SAN available to the destination cluster. A reverse script is also created for testing purposes so pool resources can be migrated back to the source cluster.

  5. The cluster scan for new devices command is executed on the destination cluster so that the cluster is aware of LUNs that are now available.

  6. Resources are brought online and load on the most preferred node in the cluster.

    HINT:You can use the cluster migrate command to start resources on nodes other than the preferred node on the destination cluster.

  7. Resources appear as running and primary on the cluster where you have migrated them.

7.1.2 Migrating Cluster Resources between Clusters

WARNING:Do not migrate resources for a test failover if the peer (LAN) connection between the source and destination cluster is down. Possible disk problems and data corruption could occur. This warning does not apply if resources are migrated during an actual cluster site failure.

To manually migrate cluster resources from one cluster to another:

  1. Start your Internet browser and enter the URL for iManager.

    The URL is http://server_ip_address/nps/iManager.html. Replace server_ip_address with the IP address or DNS name of the server that has iManager and the Identity Manager preconfigured templates for iManager installed.

  2. Specify your username and password, specify the tree where you want to log in, then click Login.

  3. In the left column, click Clusters, then click the BCC Manager link.

  4. Specify a cluster name, or browse and select one.

  5. Select one or more cluster resources, then click BCC Migrate.

  6. Select the cluster where you want to migrate the selected resources, then click OK.

    The resources migrate to their preferred node on the destination cluster. If you select Any Configured Peer as the destination cluster, the Business Continuity Clustering software chooses a destination cluster for you. The destination cluster that is chosen is the first cluster that is up in the peer clusters list for this resource.