After you have installed, set up, and configured Novell Business Continuity Clustering software and resources, some additional information can be useful to help you effectively manage your business continuity cluster. This information consists of instructions for migrating resources from one cluster to another, changing existing cluster peer credentials, and generating a business continuity report that provides cluster configuration and status information.
See the following sections for this additional information:
Although there is now an automatic failover feature for Novell Business Continuity Clustering, it is recommended that you manually migrate resources from one cluster to another cluster. See Section B.0, Setting Up Auto-Failover. 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.
HINT:You can use the cluster migrate command to start resources on nodes other than the preferred node on the destination cluster.
To manually migrate cluster resources from one cluster to another:
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.
Specify your username and password, specify the tree where you want to log in, then click .
In the left column, click , then click the link.
Specify a cluster name, or browse and select one.
Select one or more cluster resources, then click .
Select the cluster where you want to migrate the selected resources, then click .
The resources migrate to their preferred node on the destination cluster. If you select 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.
Migrating a pool resource to another cluster causes the following to happen:
If the source cluster can be contacted, the state of the resource is changed to offline.
The resource changes from primary to secondary on the source cluster.
Any SAN script that is associated with the pool resource is run.
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.
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.
Resources are brought online and load on the their most preferred node in the cluster.
Resources appear as running and primary on the cluster where you have migrated them.
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.
Changing cluster peer credentials consists of changing the username and password for the administrative user that the selected cluster will use to connect to a selected peer cluster. You might need to do this if the administrator username or password changes for any clusters in the business continuity cluster.
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.
IMPORTANT:In order to add or change cluster peer credentials, you must access iManager on a server that is in the same eDirectory tree as the cluster you are adding or changing peer credentials for.
Specify your username and password, specify the tree where you want to log in, then click .
In the left column, click , then click the link.
Specify a cluster name, or browse and select one.
Click and select a peer cluster.
Edit the administrator username and password that the selected cluster will use to connect to the selected peer cluster, then click .
When specifying a username, you don’t need to include the Novell eDirectory context for the user name.
NOTE:If the business continuity cluster has clusters in multiple eDirectory trees, and you specify a common username and password, each eDirectory tree in the business continuity cluster must have the same username and password.
You can view the current status of your business continuity cluster by using either iManager or the server console of a cluster in the business continuity cluster.
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.
Specify your username and password, specify the tree where you want to log in, then click .
In the left column, click , then click the link.
Specify a cluster name, or browse and select one.
Using this page, you can see if all cluster peer connections are up or if one or more peer connections are down. You can also see the status of the BCC resources in the business continuity cluster.
At the server console of a server in the business continuity cluster, enter the following commands to get different kinds of status information:
cluster view
cluster status
cluster connections
You can generate a report for each cluster in the business continuity cluster to list information on a specific cluster, such as current cluster configuration, cluster nodes, and cluster resources. You can print or save the report by using your browser.
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.
Specify your username and password, specify the tree where you want to log in, then click .
In the left column, click , then click the link.
Specify a cluster name, or browse and select one.
Click the button.
After enabling a resource for business continuity, it is possible to disable it. You might want to do this if you accidentally enabled the resource for business continuity, or if you no longer want a specific resource to potentially run on another cluster.
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.
Specify your username and password, specify the tree where you want to log in, then click .
In the left column, click , then click the link.
Specify the cluster name, or browse and select it.
Select the desired cluster resource from the list of Cluster objects
Click the link, then click the tab.
Deselect the check box, then click .
Wait for Identity Manager to synchronize the changes.
This could take from 30 seconds to one minute, depending on your configuration.
Delete the Cluster Resource object on the clusters where you no longer want the resource to run.
IMPORTANT:If you disable Business Continuity Clustering for a cluster by using either iManager or the cluster disable console command, the cluster resources in that cluster that that have been enabled for business continuity are automatically disabled for business continuity. If you re-enable Business Continuity Clustering for the cluster, you must again re-enable each of its cluster resources that you want to be enabled for business continuity.
This can be a time-consuming process if you have many cluster resources that are enabled for business continuity. For this reason, you should use caution when disabling Business Continuity Clustering for an entire cluster.
Novell Business Continuity Clustering (BCC) Services provides some server console commands to help you perform certain business continuity cluster-related tasks. Some of the commands can be used both with Novell Cluster Services and with Novell Business Continuity Clustering. Table 2-1 lists the BCC-related server console commands and gives a brief description of each command. For other cluster console commands, see Console Commands for Novell Cluster Services
in the NW6.5 SP8: Novell Cluster Services 1.8.5 Administration Guide.
To execute a cluster console command, enter cluster followed by the command. For example, if this cluster is a member of a business continuity cluster, and you want to see this cluster's peer clusters, enter cluster view at the server console. You can also enter cluster help at the console prompt to get information on the commands and their functions.
Table 2-1 Console Commands for Novell Business Continuity Clustering
|
Console Command |
Description |
|---|---|
|
cluster credentials [cluster] |
Lets you change the administrator username and password that this cluster uses to connect to the specified peer cluster. The cluster you specify must be a member of a cluster that has already been enabled for Business Continuity Clustering. |
|
cluster disable [resource] |
Disables Business Continuity Clustering for the specified resource. The resource you specify must be a member of a cluster that has already been enabled for Business Continuity Clustering. If no resource is specified, the entire cluster is disabled for Business Continuity Clustering. If you disable Business Continuity Clustering for a cluster by using the cluster disable console command, it is also disabled for those cluster resources that have been enabled for Business Continuity Clustering. If you re-enable Business Continuity Clustering for the cluster, you must re-enable each individual cluster resource that you want to be enabled for business continuity. This can be a time-consuming process if you have many cluster resources that are enabled for business continuity. For this reason, you should use caution when disabling Business Continuity Clustering for an entire cluster. |
|
cluster enable [resource] |
Enables Business Continuity Clustering for the specified resource. The resource you specify must be a member of a cluster that has already been enabled for Business Continuity Clustering. If no resource is specified, the entire cluster is enabled for Business Continuity Clustering. When enabling a resource for business continuity, previous versions of the CLI would not set the peer clusters where the resource was assigned to run. The only way to set peer clusters for a resource was through iManager. The new version of the cluster CLI automatically sets all the clusters in the BCC on a resource. Assigning a resource to specific clusters still must be done through iManager. |
|
cluster migrate [source/resource] [destination/nodename] |
Migrates the specified resource from the specified source cluster to the specified target (destination) cluster. Specifying * for the resource name migrates all BCC-enabled resources. Specifying * for the node name brings the resource online at the most preferred node. |
|
cluster resetresources |
Changes the state of all resources on this cluster to offline and secondary. This is a recovery procedure that should be run when a cluster in a BCC is brought back into service. You should run this command when only one node is a member of the cluster.
|
|
cluster view |
Displays the node name, cluster epoch number, master node name, a list of nodes that are currently members of the cluster, and peer clusters if this cluster is a member of a Business Continuity Cluster. |
|
cluster resources [resource] |
Lets you view the state and location of cluster resources and whether resources are primary or secondary. You can optionally specify a specific resource name. |
|
cluster status |
Lets you view the state and location of cluster resources and whether resources are primary or secondary. If the resource state is primary, the node where the resource is running is displayed. If the resource state is secondary, the cluster where the resource is located is displayed. |
|
cluster connections [-a] |
Displays the connection status of the cluster. Specifying -a attempts to show the connection status of all clusters in the BCC. |
|
cluster refresh |
This command should not be used except under the direction of Novell Support. |