2.4 Setting Up Novell Business Continuity Clustering Software

After you have installed and configured Identity Manager and the Business Continuity Clustering software, and you have configured file system mirroring, you need to set up the Novell Business Continuity Clustering software.

2.4.1 Configuring Identity Manager Drivers for the Business Continuity Cluster

The Identity Manager preconfigured templates for iManager that were installed when you ran the Business Continuity Clustering installation must be configured so you can properly manage your business continuity cluster. The preconfigured templates include the following:

  • Cluster Resource Synchronization: This template must always be configured, even in a single-tree business continuity cluster.

  • User Object Synchronization: Configuring this template is necessary only if you have more than one eDirectory tree in your business continuity cluster. See Section A.0, Implementing a Multiple-Tree BCC for more information.

The Identity Manager engine and eDirectory driver must be installed on one node in each cluster. The node where Identity Manager is installed must have an eDirectory full replica with at least read/write access to all eDirectory objects that will be synchronized between clusters. For information about the full replica requirements, see Section 2.1.3, Novell eDirectory 8.8.

Configuring the Identity Manager Drivers and Templates

  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 DirXML Utilities, then click the New Driver link.

  4. Choose to place the new driver in a new driver set, then click Next.

    Both the User Object Synchronization driver and the Cluster Resource Synchronization driver can be added to the same driver set.

  5. Specify the driver set name, context, and the server that the driver set will be associated with.

    The server is the same server where you installed the Identity Manager engine and eDirectory driver.

  6. Choose to not create a new partition for the driver set, then click Next.

  7. Choose to import a preconfigured driver from the server, select the Identity Manager preconfigured template for cluster resource synchronization, then click Next.

    The template name is BCCClusterResourceSynchronization.xml.

  8. Fill in the values on the wizard page as prompted, then click Next.

    Each field contains an example of the type of information that should go into the field. Descriptions of the information required are also included with each field.

    • Driver name: Enter a unique name for this driver to identify its function. For example, Cluster1SyncCluster2. If you use both preconfigured templates, you must specify different driver names for each driver template.

    • Name of SSL Certificate: If you do not have an SSL certificate, leave this value set to the default. The certificate is created later in the configuration process. See Creating SSL Certificates for instructions on creating SSL certificates.

    • DNS name of other IDM node: Specify the DNS name or IP address of the Identity Manager server in the other cluster.

    • Port number for this driver: If you have a business continuity cluster that consists of three or four clusters, you must specify unique port numbers for each driver template set. The default port number is 2002.

      You must specify the same port number for the same template in the other cluster. For example, if you specify 2003 as the port number for the resource synchronization template, you must specify 2003 as the port number for the resource synchronization template in the peer driver for the other cluster.

    • Full Distinguished Name (DN) of the cluster this driver services: For example, Cluster1.siteA.Novell.

    • Fully Distinguished Name (DN) of the landing zone container: Specify the context of the container where the cluster pool and volume objects in the other cluster are placed when they are synchronized to this cluster.

      This container is referred to as the landing zone. The NCP server objects for the virtual server of a BCC enabled resource are also placed in the landing zone.

      IMPORTANT:The context must already exist and must be specified using dot format without the tree name. For example, siteA.Novell.

      Prior to performing this step, you could create a separate container in eDirectory specifically for these cluster pool and volume objects. You would then specify the context of the new container in this step.

    The IDM Driver object must have sufficient rights to any object it reads or writes in the following containers:

    • The Identity Manager driver set container.

    • The container where the Cluster object resides.

    • The container where the server objects reside.

      If server objects reside in multiple containers, this must be a container high enough in the tree to be above all containers that contain server objects.

      Best practice is to have all server objects in one container.

    • The container where the cluster pool and volume objects are placed when they are synchronized to this cluster.

      This container is referred to as the landing zone. The NCP server objects for the virtual server of a BCC enabled resource are also placed in the landing zone.

    You can do this by making the IDM Driver object security equivalent to another User object with those rights. See Step 9.

    IMPORTANT:If you choose to include User object synchronization, exclude the Admin User object from being synchronized. See Step 7 in Section A.4, Synchronizing the BCC-Specific Identity Manager Drivers for information about synchronizing User objects when adding new clusters to the business continuity cluster.

  9. Make the IDM Driver object security equivalent to an existing User object:

    1. Click Define Security Equivalences, then click Add.

    2. Browse to and select the desired User object, then click OK.

    3. Click Next, and then click Finish.

  10. Repeat Step 1 through Step 9 above on the other clusters in your business continuity cluster.

    This includes creating a new driver and driver set for each cluster.

    IMPORTANT:If you have upgraded to Identity Manager 3 and click either the cluster resource synchronization driver or the user object synchronization driver, a message is displayed prompting you to convert the driver to a new architecture. Click OK to convert the driver.

Creating SSL Certificates

It is recommended that you create an SSL certificate for the Cluster Resource Synchronization driver. Creating one certificate creates that certificate for a driver pair. For example, creating an SSL certificate for the Cluster Resource Synchronization driver also creates the certificate for the Cluster Resource Synchronization drivers on the other clusters.

To create an SSL certificate:

  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 DirXML Utilities, then click NDS-to-NDS Driver Certificates.

  4. Specify the requested driver information for this cluster, then click Next.

    You must specify the driver name (including the context) you supplied in Step 8 for this cluster. Use the following format when specifying the driver name:

    DriverName.DriverSet.OrganizationalUnit.OrganizationName
    

    Ensure that there are no spaces (beginning or end) in the specified context, and do not use the following format:

    cn=DriverName.ou=OrganizationalUnitName.o=OrganizationName
    
  5. Specify the requested driver information for the driver in the other cluster.

    Use the same format specified in Step 4.

  6. Click Next, then click Finish.

Synchronizing Identity Manager Drivers

After creating the BCC-specific Identity Manager drivers and SSL certificates, if you are adding a new cluster to an existing business continuity cluster, you must synchronize the BCC-specific Identity Manager drivers. If the BCC-specific Identity Manager drivers are not synchronized, clusters cannot be enabled for business continuity. Synchronizing the Identity Manager drivers is not necessary unless you are adding a new cluster to an existing business continuity cluster.

NOTE:DirXML is now called Identity Manager in the latest releases.

To synchronize the BCC-specific Identity Manager drivers:

  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 DirXML, then click the DirXML Overview link.

  4. Search for and find the BCC driver set.

  5. Click the red Cluster Sync icon for the driver you want to synchronize, then click the Migrate from eDirectory button.

  6. Click Add, browse to and select the Cluster object for the new cluster you are adding to the business continuity cluster, then click OK.

    Selecting the Cluster object causes the BCC-specific Identity Manager drivers to synchronize.

If you have multiple eDirectory trees in your BCC, see Section A.4, Synchronizing the BCC-Specific Identity Manager Drivers.

Preventing Identity Manager Synchronization Loops

If you have three or more clusters in your business continuity cluster, you should set up synchronization for the User objects and Cluster Resource objects in a manner that prevents Identity Manager synchronization loops. Identity Manager synchronization loops can cause excessive network traffic and slow server communication and performance.

For example, in a three-cluster business continuity cluster, an Identity Manager synchronization loop occurs when Cluster One is configured to synchronize with Cluster Two, Cluster Two is configured to synchronize with Cluster Three, and Cluster Three is configured to synchronize back to Cluster One. This is illustrated in Figure 2-3 below.

Figure 2-3 Three-Cluster Identity Manager Synchronization Loop

A preferred method is to make Cluster One an Identity Manager synchronization master in which Cluster One synchronizes with Cluster Two, and Cluster Two and Cluster Three both synchronize with Cluster One. This is illustrated in Figure 2-4 below.

Figure 2-4 Three-Cluster Identity Manager Synchronization Master

You could also have Cluster One synchronize with Cluster Two, Cluster Two synchronize with Cluster Three, and Cluster Three synchronize back to Cluster Two as illustrated in Figure 2-5.

Figure 2-5 Alternate Three-Cluster Identity Manager Synchronization Scenario

To change your BCC synchronization scenario:

  1. In the Connections section of the Business Continuity Cluster Properties page, select one or more peer clusters that you want a cluster to synchronize to, then click Edit.

In order for a cluster to appear in the list of possible peer clusters, that cluster must have the following:

  • Business Continuity Clustering software installed.

  • Identity Manager installed.

  • The BCC-specific Identity Manager drivers configured and running.

  • Be enabled for business continuity.

2.4.2 Configuring Clusters for Business Continuity

The following tasks must be performed on each separate Novell Cluster Services cluster that you want to be part of the business continuity cluster:

NOTE:Identity Manager must be configured and running before configuring clusters for business continuity.

Enabling Clusters for Business Continuity

If you want to enable a cluster to fail over selected resources or all cluster resources to another cluster, you must enable business continuity on that cluster.

  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. This server should be in the same eDirectory tree as the cluster you are enabling for business continuity.

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

  3. Ensure that the BCC-specific Identity Manager drivers are running.

    1. In the left column, click DirXML, then click the DIRXML Overview link.

    2. Search the eDirectory Container or tree for the BCC-specific Identity Manager drivers.

    3. For each driver, click the upper right corner of the driver icon to see if a driver is started or stopped.

    4. If the driver is stopped, start it by selecting Start.

  4. In the left column, click Clusters, then click the Cluster Options link.

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

  6. Click the Properties button, then click the Business Continuity tab.

  7. Ensure that the Enable Business Continuity Features check box is selected.

  8. Repeat Step 1 through Step 7 for the other cluster that this cluster will migrate resources to.

  9. Continue with Step 1 in the Adding Cluster Peer Credentials section.

Adding Cluster Peer Credentials

In order for one cluster to connect to a second cluster, the first cluster must be able to authenticate to the second cluster. To make this possible, you must add the username and password of the user that the selected cluster will use to connect to the selected peer cluster.

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.

  1. In the Connections section of the Business Continuity Cluster Properties page, select the peer cluster, then click Edit.

    In order for a cluster to appear in the list of possible peer clusters, that cluster must have the following:

    • Business Continuity Clustering software installed.

    • Identity Manager installed.

    • The BCC-specific Identity Manager drivers configured and running.

    • Be enabled for business continuity.

  2. Add the administrator username and password that the selected cluster will use to connect to the selected peer cluster.

    When adding the administrator username, do not include the context for the user. For example, use bccadmin instead of bccadmin.prv.novell.

    Rather than using the Admin user to administer your BCC, you should consider creating another user with sufficient rights to the appropriate contexts in your eDirectory tree to manage your BCC. For information, see Section 2.2.3, Configuring a BCC Administrator User and Group.

  3. Repeat Step 1 and Step 2 for the other cluster that this cluster will migrate resources to.

  4. Continue with Step 1 in the Adding Resource Script Search and Replace Values section.

Adding Resource Script Search and Replace Values

To enable a resource for business continuity, certain values (such as IP addresses) specified in resource load and unload scripts need to be changed in corresponding resources in the other clusters. You need to add the search and replace strings that are used to transform cluster resource load and unload scripts from this cluster to another cluster.

HINT:You can see the IP addresses that are currently assigned to resources by entering the ip addr show command at the Linux server console of cluster servers. You must be logged in as root to use this command.

The search and replace data is cluster-specific, and it is not synchronized via Identity Manager between the clusters in the business continuity cluster.

To add resource script search and replace values:

  1. In the Resource Replacement Script section of the Business Continuity Cluster Properties page, click New.

  2. Add the desired search and replace values, then click OK.

    The search and replace values you specify here apply to all resources in the cluster that have been enabled for business continuity.

    For example, if you specified 10.1.1.1 as the search value and 192.168.1.1 as the replace value, the resource with the 10.1.1.1 IP address in its scripts is searched for in the primary cluster and, if found, the 192.168.1.1 IP address is assigned to the corresponding resource in the secondary cluster.

    You can also specify global search and replace addresses for multiple resources in one line. This can be done only if the last digits in the IP addresses are the same in both clusters. For example, if you specify 10.1.1. as the search value and 192.168.1. as the replace value, the software finds the 10.1.1.1, 10.1.1.2, 10.1.1.3 and 10.1.1.4 addresses, and then replaces them with the 192.168.1.1, 192.168.1.2, 192.168.1.3, and 192.168.1.4 addresses, respectively.

IMPORTANT:Make sure to use a trailing dot in the search and replace value. If a trailing dot is not used, 10.1.1 could be replaced with an IP value such as 192.168.100 instead of 192.168.1.

You can select the Use Regular Expressions check box to use wildcard characters in your search and replace values. The following links provide information on regular expressions and wildcard characters:

You can find additional information on regular expressions and wildcard characters by searching the Web.

Adding SAN Management Configuration Information

You can create scripts and add commands that are specific to your SAN hardware. These scripts and commands might be needed to promote mirrored LUNs to primary on the cluster where the pool resource is being migrated to, or demote mirrored LUNs to secondary on the cluster where the pool resource is being migrated from.

You can also add Perl scripts and add commands to scripts to call other scripts. Any command that can be run at the Linux server console can be used. The scripts or commands you add are stored in eDirectory. If you add commands to call outside scripts, those scripts must exist on every server in the cluster.

To add SAN management configuration information:

  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 Cluster Options link.

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

  5. Under Cluster Objects, select a cluster resource that is enabled for business-continuity, then click Details.

    Cluster resources that are enabled for business continuity have the BCC label on the resource type icon.

  6. Click the Business Continuity tab, then click SAN Management.

  7. Create BCC SAN management load and unload scripts:

    1. Under BCC Load Scripts, click New to bring up a page that lets you create a script to promote mirrored LUNs on a cluster.

      You can also delete a script, edit a script by clicking Details, or change the order in which load scripts execute by clicking the Move Up and Move Down links.

    2. Specify the values on the SAN Management Script Details page.

      Descriptions of the information required for the page fields and options include:

      • Name and Description: Specify a name, and if desired, a description of the script you are creating.

      • CIMOM IP/DNS: If you are not using a template and if you selected the CIM Client check box on the previous page, specify the IP address or DNS name for your SAN. This is the IP address or DNS name that is used for SAN management.

      • Namespace: If you selected the CIM Client check box on the previous page, accept the default namespace, or specify a different namespace for your SAN.

        Namespace determines which models and classes are used with your SAN. Consult your SAN documentation to determine which namespace is required for your SAN.

      • Username and Password: If you checked the CIM Client check box on the previous page, specify the username and password that is used to connect to and manage your SAN.

      • Port: If you selected the CIM Client check box on the previous page, accept the default port number or specify a different port number. This is the port number that CIMOM (your SAN manager) uses. Consult your SAN documentation to determine which port number you should use.

      • Secure: If you selected the CIM Client check box on the previous page, select or deselect the Secure check box depending whether you want SAN management communication to be secure (HTTPS) or unsecure (HTTP).

      • Script Parameters: If desired, specify variables and values for the variables that are used in the SAN management script.

        To specify a variable, click New, then provide the variable name and value in the fields provided. Click OK to save your entries. You can specify additional variables by clicking New again and providing variable names and values. You can also edit and delete existing script parameters by clicking the applicable link.

      • Script Parameters Text Box: Use this text box to add script commands to the script you are creating.

        These script commands are specific to your SAN hardware. You can add a Perl script, or any commands that can be run on Linux or NetWare (depending on your platform). If you add commands to call outside scripts, those scripts must exist on every server in the cluster.

      • CIM Enabled: Select this box if your SAN supports SMI-S and you did not select the CIM Client check box on the previous page. This causes the CIM-specific fields to become active on this page.

      • Synchronous: If this check box is not selected, multiple scripts can be run concurrently. Selecting the box causes scripts to run individually, one after another. Most SAN vendors do not support running multiple scripts concurrently.

      • Edit Flags: This is an advanced feature, and should not be used except under the direction of Novell Support.

    3. Click Apply and OK on the Script Details page, then click OK on the Resource Properties page to save your script changes.

      IMPORTANT:After clicking Apply and OK on the Script Details page, you are returned to the Resource Properties page (with the Business Continuity tab selected). If you do not click OK on the Resource Properties page, your script changes are not saved.

IMPORTANT:The CIMOM daemons on all nodes in the business continuity cluster should be configured to bind to all IP addresses on the server.

Business Continuity Clustering connects to the CIMOM by using the master IP address for the cluster. Because the master IP address moves to other nodes during a failover or migration, the CIMOM must be configured to bind to all IP addresses (secondary and primary), rather than just the primary IP address of the host.

You can do this by editing the openwbem.conf file. See Changing the OpenWBEM CIMOM Configuration in the OpenWBEM Services Administration Guide for OES for more information.

Enabling Reiser and Ext3 File Systems to Run on Secondary Clusters

If you are using Reiser or Ext3 file systems in cluster resources on the clusters in your BCC and you want to migrate or fail over those file systems to other clusters, you must add a script to convert the EVMS CSM (Cluster Segment Manager) container for the file system. Without the script, the file system cannot be mounted and the cluster resource cannot be brought online on another cluster.

NOTE:The script is necessary for only Reiser and Ext3 file systems, and not for NSS pools.

  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 Cluster Options link.

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

  5. Under Cluster Objects, select the business-continuity-enabled cluster resource that contains the Reiser or Ext3 file system, then click Details.

    Cluster resources that are enabled for business continuity have the BCC label on the resource type icon.

  6. Click the Business Continuity tab, then click SAN Management.

  7. Under BCC Load Scripts, click New to bring up a wizard that lets you create a new script.

  8. In the wizard, specify the following information:

    • Name: Convert CSM container.

    • Description: Converts the EVMS Cluster Segment Manager (CSM) container so the specified container is available on the secondary cluster.

    • CIM Enabled: Ensure that this option is deselected (not checked).

    • Synchronous: Ensure that this option is selected (checked)

    See Step 7.b in Adding SAN Management Configuration Information for more information and descriptions of the information in the value fields.

  9. Under Script Parameters, click New, then specify the following:

    • Name: Specify the variable name as CONTAINER_NAME. This value is case-sensitive and should be entered as

      CONTAINER_NAME
      
    • Value: Specify the name of the EVMS CSM (Cluster Segment Manager) container. You assigned this name to the EVMS CSM container when you created it. This value is case-sensitive and should exactly match the container name.

  10. Using a text editor, copy and paste the bcc_csm_util.pl script into the Script Parameters text box.

    The script is located in the /nsmi_scripts/linux/ directory on the Business Continuity Clustering 1.1 CD or ISO image.

  11. Click Apply to save your changes.

  12. Repeat Step 1 through Step 11 for the peer clusters in your BCC.

    The information you provide in the steps should be unique for each cluster.

Verifying BCC Administrator User Trustee Rights and Credentials

You must ensure that the BCC Administrator user is a LUM-enabled user. For instructions, see Creating the BCC Group and Administrative User.

You must ensure that the user who manages your BCC (that is, the BCC Administrator user) is a trustee of the Cluster objects and has at least Read and Write rights to the All Attributes Rights property. For instructions, see Assigning Trustee Rights for the BCC Administrator User to the Cluster Objects.

In order for the BCC Administrator user to gain access to the cluster administration files (/admin/novell/cluster) on other Linux cluster nodes in your BCC, you must add that user to the ncsgroup on each cluster node. For instructions, see Adding the BCC Administrator User to the ncsgroup on Each Cluster Node.

2.4.3 Configuring Cluster Resources for Business Continuity

Cluster resources can be configured for business continuity after they are created. Configuring a resource for business continuity consists of enabling that resource for business continuity, adding load and unload scripts’ search and replace data specific to the resource, and selecting peer clusters for the resource.

IMPORTANT:In a business continuity cluster, you should have only one NSS pool for each LUN that could be failed over to another cluster. This is necessary because in a business continuity cluster, entire LUNs fail over to other clusters, rather than individual pools, which fail over to other nodes within a cluster.

A cluster-enabled NSS pool must contain at least one volume before its cluster resource can be enabled for business continuity. You get an error message if you attempt to enable the resource for business continuity if its NSS pool does not contain a volume.

Also, if you have encrypted NSS volumes in your BCC, then all clusters in that BCC must be in the same eDirectory tree. If not, then the clusters in the other eDirectory tree cannot decrypt the NSS volumes. This rule applies to both NetWare and Linux BCCs.

Enabling a Cluster Resource for Business Continuity

Cluster resources must be enabled for business continuity on the primary cluster before they can be synchronized and appear as resources in the other clusters in the business continuity cluster. Enabling a cluster resource makes it possible for that cluster resource or cluster pool resource to be migrated to another cluster.

IMPORTANT:Although you can add search and replace data that is resource-specific after you enable a resource for business continuity, we recommend adding the search and replace data for the entire cluster before you enable resources for business continuity. See Adding Resource Script Search and Replace Values for instructions on adding search and replace data for the entire cluster.

When you enable a resource for business continuity and that resource has been synchronized and appears in the other clusters, the preferred nodes for the other clusters are by default set to all nodes in the cluster. If you want to change the resource’s preferred nodes for other clusters in your BCC, you must manually do it. Changes to the preferred nodes list in the primary cluster do not automatically replicate to the preferred nodes lists for other clusters in your BCC.

  1. (Conditional) If you are creating a new cluster resource or cluster pool resource, follow the instructions for creating a cluster resource or cluster pool resource by using iManager in the Setting Up Cluster Services section of the OES 1 SP2: Novell Cluster Services 1.8.2 Administration Guide for Linux, then continue with Step 2.

  2. Enable a cluster resource or cluster pool resource for business continuity:

    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 Cluster Options link.

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

    5. Select the desired cluster resource from the list of Cluster objects.

    6. Click the Details link, then click the Business Continuity tab.

  3. Ensure that the Enable Business Continuity Features check box is selected.

  4. Continue with Step 1 in the Adding Resource Script Search and Replace Values section.

Adding Resource Script Search and Replace Values

If you did not previously add search and replace data specific to the entire cluster, you must now add it for this resource.

IMPORTANT:Adding resource script search and replace values for the entire cluster is recommended rather than adding those values for individual cluster resources. You should contact Novell Support prior to adding search and replace values for individual cluster resources.

To enable a resource for business continuity, certain values (such as IP addresses, DNS names, and tree names) specified in resource load and unload scripts need to be changed in corresponding resources in the other clusters. You need to add the search and replace strings that are used to transform cluster resource load and unload scripts from this cluster to another cluster.

The search and replace data you add is resource-specific, and it is not synchronized via Identity Manager between the clusters in the business continuity cluster.

To add resource script search and replace values specific to this resource:

  1. In the Resource Script Replacements section of the page, click New.

    If a resource has already been configured for business continuity, you can click Edit to change existing search and replace values or click Delete to delete them.

  2. Add the desired search and replace values, then click OK.

    The search and replace values you specify here apply to only to the resource you are enabling for business continuity. If you want the search and replace values to apply to any or all cluster resources, add them to the entire cluster instead of just to a specific resource.

    See Adding Resource Script Search and Replace Values for more information on resource script search and replace values and adding those values to the entire cluster.

  3. Do one of the following:

You can select the Use Regular Expressions check box to use wildcard characters in your search and replace values. The following links provide information on regular expressions and wildcard characters:

You can find additional information on regular expressions and wildcard characters by searching the Web.

IMPORTANT:If you change the resource-specific search and replace data after inti ti ally adding it, you must update the resource load script and unload script in one of the other clusters by editing it and adding a space or a comment to it. This causes the script to be updated with the new search and replace data.

You can also update the IP address on the cluster protocols page in iManager to cause IP address search and replace values to be updated for both load and unload scripts. This might require you to go back and change the IP addresses specified in the resource load and unload scripts in the source cluster to their original values.

Selecting Peer Clusters for the Resource

Peer clusters are the other clusters that this cluster resource can be migrated to. The cluster or clusters that you select determine where the resource can be manually migrated. If you decide to migrate this resource to another cluster, you must migrate it to one of the clusters that has been selected.

  1. Select the other clusters that this resource can be migrated to.

  2. Do one of the following:

    • If you are creating a new non-pool cluster resource that contains a Reiser or Ext3 file system, click Finish.

    • If this is an existing non-pool cluster resource that contains a Reiser or Ext3 file system, click Apply.

    • If you are creating a new cluster pool resource, click Next, then add the SAN management configuration information. For information, see Adding SAN Management Configuration Information.

    • If this is an existing cluster pool resource, add the SAN management configuration information. For information, see Adding SAN Management Configuration Information.

Adding SAN Array Mapping Information

For information on adding SAN array mapping information, see Adding SAN Management Configuration Information.