1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. BUSINESS CONTINUITY CLUSTERING 1.1 SP2 -...
  6. Administration manual

Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION Administration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
AUTHORIZED DOCUMENTATION
Administration Guide for NetWare
6.5 SP8
®
Novell
®
Business Continuity Clustering
1.1 SP2
August 14, 2009
www.novell.com
BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION

Summary of Contents for Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION

  • Page 1 AUTHORIZED DOCUMENTATION Administration Guide for NetWare 6.5 SP8 ® Novell ® Business Continuity Clustering 1.1 SP2 August 14, 2009 www.novell.com BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...
  • Page 2 Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Trademarks For Novell Trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
  • Page 4 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 5: Table Of Contents

    Novell Business Continuity Clusters ........
  • Page 6 4.1.4 Novell Cluster Services 1.8.5 for NetWare ....... . 39 4.1.5...
  • Page 7 6.2.3 Adding Search-and-Replace Values to the Resource Replacement Script ..74 6.2.4 Adding SAN Management Configuration Information ......75 6.2.5 Verifying BCC Administrator User Trustee Rights and Credentials .
  • Page 8 Novell Cluster Services Configuration and Setup ....... . . 140...
  • Page 9 E.1.1 Console Commands for BCC ......... 141 E.1.2 Installing Business Continuity Clustering .
  • Page 10 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 11: About This Guide

    Documentation Updates The latest version of this Novell Business Continuity Clustering 1.1 SP2 Administration Guide for NetWare 6.5 SP8 (same as OES 2 SP1 NetWare) is available on the Business Continuity Clustering Documentation Web site (http://www.novell.com/documentation/bcc/index.html) under BCC for OES 2 SP1.
  • Page 12 OES 2 SP1 Documentation Web site (http://www.novell.com/documentation/oes2/index.html). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

  • Page 13: Overview

    Section 1.1, “Disaster Recovery Implications,” on page 13 Section 1.2, “Disaster Recovery Implementations,” on page 14 Section 1.3, “Novell Business Continuity Clusters,” on page 21 Section 1.4, “BCC Deployment Scenarios,” on page 22 Section 1.5, “Key Concepts,” on page 25 1.1 Disaster Recovery Implications...

  • Page 14: Disaster Recovery Implementations

    Moving applications and services to the Internet frees corporations from the restrictions of traditional LAN-based applications. ® ® By using Novell exteNd Director portal services, iChain , and ZENworks , all services, applications, and data can be rendered through the Internet, allowing for loss of service at one site but still providing full access to the services and data by virtue of the ubiquity of the Internet.

  • Page 15: Stretch Clusters Vs. Cluster Of Clusters

    This section describes each deployment type, then compares the capabilities of each. Novell Business Continuity Clustering automates some of the configuration and processes used in a cluster of clusters. For information, see Section 1.3, “Novell Business Continuity Clusters,”...
  • Page 16 Stretch Clusters A stretch cluster consists of a single cluster where the nodes are located in two geographically separate data centers. All nodes in the cluster must be in the same Novell eDirectory tree, which requires the eDirectory replica ring to span data centers. The IP addresses for nodes and cluster resources in the cluster must share a common IP subnet.
  • Page 17 A cluster of clusters provides the ability to fail over selected cluster resources or all cluster resources from one cluster to another cluster. For example, the cluster resources in one cluster can fail over to separate clusters by using a multiple-site fan-out failover approach. A given service can be provided by multiple clusters.
  • Page 18 Comparison of Stretch Clusters and Cluster of Clusters Table 1-2 compares the capabilities of a stretch cluster and a cluster of clusters. Comparison of Stretch Cluster and Cluster of Clusters Table 1-2 Capability Stretch Cluster Cluster of Clusters Number of clusters Two or more Number of geographically Two or more...
  • Page 19 Capability Stretch Cluster Cluster of Clusters Data-block replication between Yes; typically uses storage-based Yes; typically uses storage-based sites mirroring, but host-based mirroring, but host-based mirroring is possible for distances mirroring is possible for distances For information about data up to 10 km. up to 10 km.
  • Page 20 Table 1-3 illustrates why a cluster of cluster solution is less problematic to deploy than a stretch cluster solution. Manual configuration is not a problem when using Novell Business Continuity Clustering for your cluster of clusters. Advantages and Disadvantages of Stretch Clusters versus Cluster of Clusters...

  • Page 21: Novell Business Continuity Clusters

    1.3 Novell Business Continuity Clusters A Novell Business Continuity Clustering cluster is an automated cluster of Novell Cluster Services clusters. It is similar to what is described in “Cluster of Clusters” on page...

  • Page 22: Bcc Deployment Scenarios

    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.

  • Page 23: Multiple-Site Business Continuity Cluster Solution

    Figure 1-3 shows a two-site business continuity cluster that uses storage-based data replication between the sites. BCC uses eDirectory and Identity Manager to synchronize cluster information between the two clusters. Two-Site Business Continuity Cluster Figure 1-3 Two independent clusters at geographically separate sites Building A Building B...

  • Page 24: Low-Cost Business Continuity Cluster Solution

    Figure 1-4 depicts a four-site business continuity cluster that uses storage-based data replication between the sites. BCC uses eDirectory and Identity Manager to synchronize cluster information between the two clusters. Multiple-Site Business Continuity Cluster Figure 1-4 Four independent clusters in geographically separate sites Building D Building C...

  • Page 25: Key Concepts

    Section 1.5.4, “BCC Drivers for Identity Manager,” on page 25 1.5.1 Business Continuity Clusters A cluster of two to four Novell Cluster Services clusters that are managed together by Business Continuity Clustering software. All nodes in every peer cluster are running the same operating system.
  • Page 26 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 27: What's New For Bcc 1.1 Sp2

    2.1 What’s New for BCC 1.1 SP2 Business Continuity Clustering 1.1 SP2 for NetWare SP8 provides the following enhancements and changes: Support for NetWare 6.5 SP8 (same as Novell Open Enterprise Server (OES) 2 SP1 NetWare) Support for Novell Cluster Services 1.8.5 for NetWare Support for Identity Manager 3.5.1...
  • Page 28 Automatic failover No need for administrator intervention Based on a configurable minimum number of nodes or a percentage of nodes Extensible monitoring framework Disabled by default BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 29: Planning A Business Continuity Cluster

    Planning a Business Continuity Cluster ® Use the guidelines in this section to design your Novell Business Continuity Clustering solution. The success of your business continuity cluster depends on the stability and robustness of the individual peer clusters. BCC cannot overcome weaknesses in a poorly designed cluster environment.

  • Page 30: Lan Connectivity Guidelines

    When configuring Spanning Tree Protocol (STP), ensure that Portfast is enabled, or consider Rapid Spanning Tree. The default settings for STP inhibit the heartbeat for over 30 seconds whenever there is a change in link status. Test your STP configuration with Novell Cluster Services running to make sure that a node is not cast out of the cluster when a broken link is restored.

  • Page 31: San Connectivity Guidelines

    The primary objective of SAN (storage area network) connectivity in a cluster is to provide solid and stable connectivity between cluster nodes and the storage system. Before installing Novell Cluster Services and Novell Business Continuity Clustering, make sure the SAN configuration is established and verified.

  • Page 32: Storage Design Guidelines

    3.6 eDirectory Design Guidelines Your Novell eDirectory solution for each of the peer clusters in the business continuity cluster must consider the following configuration elements. Make sure your approach is consistent across all peer clusters.

  • Page 33: Cluster Context

    3.6.2 Cluster Context Place each cluster in a separate Organizational Unit (OU). All server objects and cluster objects for a given cluster should be in the same OU. Cluster Resources in Separate OUs Figure 3-1 3.6.3 Partitioning and Replication Partition the cluster OU and replicate it to dedicated eDirectory servers holding a replica of the ®...

  • Page 34: Cluster Design Guidelines

    Cluster Resource Identity in Two Clusters Figure 3-2 3.7 Cluster Design Guidelines Your Novell Cluster Services solution for each of the peer clusters in the business continuity cluster must consider the following configuration guidelines. Make sure your approach is consistent across all peer clusters.
  • Page 35 ID 1 to volume . Cluster-enabled volumes use _ADMIN high volume IDs, starting from 254 in decending order. Novell Client uses the volume ID to access a volume. When existing clusters are configured and enabled within the same business continuity cluster, the volume IDs for the existing shared volumes might also share the same volume IDs.
  • Page 36 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 37: Installing Business Continuity Clustering

    Section 4.5, “What’s Next,” on page 53 4.1 Requirements for BCC 1.1 SP2 for NetWare The requirements in this section must be met prior to installing Novell Business Continuity Clustering software. Section 4.1.1, “Business Continuity Clustering Licensing,” on page 38 Section 4.1.2, “Business Continuity Cluster Component Locations,”...

  • Page 38: Business Continuity Clustering Licensing

    4.1.1 Business Continuity Clustering Licensing Novell Business Continuity Clustering software requires a license agreement for each business continuity cluster. For purchasing information, see Novell Business Continuity Clustering (http:// www.novell.com/products/businesscontinuity/howtobuy.html). 4.1.2 Business Continuity Cluster Component Locations Figure 4-1 illustrates where the various components needed for a business continuity cluster are installed.

  • Page 39: Netware 6.5 Sp8 (Oes 2 Sp1 Netware)

    4.1.4 Novell Cluster Services 1.8.5 for NetWare You need two to four clusters with Novell Cluster Services™ 1.8.5 (the version that ships with NetWare 6.5 SP8 (same as OES 1 SP2 NetWare) installed and running on each node in the cluster.

  • Page 40: Novell Edirectory 8.8

    To add or change peer cluster credentials, you must access iManager on a server that is in the same eDirectory tree as the cluster where you are adding or changing peer credentials. 4.1.5 Novell eDirectory 8.8 Novell eDirectory 8.8 is supported with Business Continuity Clustering 1.1 Support Pack 1. See the eDirectory 8.8 documentation (http://www.novell.com/documentation/edir88/index.html) for more information.

  • Page 41: Slp

    “Identity Manager Management Utilities” on page 42 Downloading the Bundle Edition The bundle edition is a limited release of Novell Identity Manager 3.5.1 for NetWare 6.5 SP8 (same as OES 2 SP1 NetWare) that allows you to use the Identity Manager software, the eDirectory driver, and the Identity Manager management tools for Novell iManager 2.7.2.
  • Page 42 Identity Manager Management Utilities The Identity Manager management utilities must be installed on the same server as Novell iManager. The Identity Manager utilities and iManager can be installed on a cluster node, but installing them on a non-cluster node is the recommended configuration. For information about iManager requirements for BCC, see Section 4.1.8, “Novell iManager 2.7.2,”...

  • Page 43: Novell Imanager 2.7.2

    4.1.8 Novell iManager 2.7.2 Novell iManager 2.7.2 (the version released with NetWare 6.5 SP8 (OES 2 SP1 NetWare)) must be installed and running on a server in the eDirectory tree where you are installing Business Continuity Clustering software. You need to install the BCC plug-in, the Clusters plug-in, and the Storage Management plug-in in order to manage the BCC in iManager.

  • Page 44: Windows Workstation

    4.1.11 OpenWBEM OpenWBEM must be configured to start in , and be running when you manage the autoexec.ncf cluster with Novell iManager. For information on setup and configuration, see the OES 2: OpenWBEM Services Administration Guide (http://www.novell.com/documentation/oes2/ mgmt_openwbem_lx_nw/data/front.html). Port 5989 is the default setting for secure HTTP (HTTPS) communications. If you are using a firewall, the port must be opened for CIMOM communications.

  • Page 45: Shared Disk Systems

    See your storage system vendor documentation for more information on configuring LUN masking. When you create a Novell Cluster Services system that uses a shared storage system, it is important to remember that all of the servers that you grant access to the shared device, whether in the cluster or not, have access to all of the volumes on the shared storage space unless you specifically prevent such access.

  • Page 46: Ports

    Web browser, click Tools > Options > Languages, then set the first language preference in the list to a supported language. Refer to the Novell iManager documentation (http://www.novell.com/documentation/imanager27/) for information about supported languages. Web Browser Character Encoding Setting Supported language codes are Unicode (UTF-8) compliant.

  • Page 47: Bash

    4.2 Downloading the Business Continuity Clustering Software Before you install Novell Business Continuity Clustering, download and copy the software to a directory on your Windows workstation. To download Novell Business Continuity Clustering 1.1 SP2 for NetWare 6.5 SP8, go to the Novell Business Continuity Clustering download site (http:// download.novell.com/Download?buildid=bdkmSxRgKVk~).

  • Page 48: Assigning Trustee Rights For The Bcc Administrator User To The Cluster Objects

    You must also ensure that the BCC Administrator user has file system rights to the directory of each of the nodes in your BCC. This is necessary because _ADMIN:\Novell\Cluster volume is virtual, and is created each time the server starts. For this reason, you cannot...

  • Page 49: Assigning Trustee Rights For The Bcc Administrator User To The Sys:\Tmp Directory

    This can be done in a rolling fashion. You should start with the node that has the highest IP address first and work down in IP address order. This speeds the rate at which the Novell Cluster Services master node acquires the change. 4.3.4 Assigning Trustee Rights for the BCC Administrator User...

  • Page 50: Installing And Configuring The Novell Business Continuity Clustering Software

    4.4 Installing and Configuring the Novell Business Continuity Clustering Software It is necessary to run the Novell Business Continuity Clustering installation program when you want Install the Business Continuity Clustering engine software on cluster nodes for the clusters that will be part of a business continuity cluster.

  • Page 51: Installing The Bcc Engine

    Windows server later in the installation. Novell Business Continuity Clustering: Installs the core Business Continuity Clustering engine files. This core software must be installed on all nodes in each Novell Cluster Services cluster that will be part of a business continuity cluster.

  • Page 52: Installing The Identity Manager Templates

    This lets you keep your cluster up and running and lets your users continue to access the network while cluster nodes are being restarted. 9 Repeat the above steps for each Novell Cluster Services cluster that will be part of the business continuity cluster.

  • Page 53: What's Next

    Identity Manager Templates for Windows iManager Servers: Installs the templates on the local Windows iManager server. You will be asked to specify the path to Tomcat (a default path is provided) on the Windows server later in the installation. 4 Do one of the following: NetWare iManager Server: If you chose to install the Identity Manager iManager templates on a NetWare server, specify the name of the eDirectory tree and the fully distinguished name for the server where you want to install the templates.
  • Page 54 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 55: Upgrading Business Continuity Clustering For Netware

    BCC 1.1 SP2 for NetWare requires that every node in each peer cluster be upgraded to NetWare 6.5 SP8 (same as OES 2 SP1 NetWare) with the latest patches for NetWare and Novell Cluster Services. For information, see the following resources: NetWare: “Upgrading to OES 2 SP1...

  • Page 56: Performing A Rolling Cluster Upgrade

    8b Update NetWare 6.5 from version SP5 or SP6 to version SP8, and apply the latest patches for NetWare and Novell Cluster Services. For information, see the NetWare Installation Guide (http://www.novell.com/ documentation/oes2/inst_oes_nw/data/b7211uh.html)
  • Page 57 NPM files, and then re-installing the correct iManager NPMs, as described in TID 3009687: You must specify an IP address; iManager plug-ins not working after update to SP6 (http://www.novell.com/support/php/ search.do?cmd=displayKC&docType=kc&externalId=3009687). Novell Archive and Version Services ( arkmgmt.npm Novell Cluster Services ( ncsmgmt.npm Novell Storage Services nssmgmt.npm...

  • Page 58: Upgrading Clusters From Bcc 1.0 To Bcc 1.1 Sp2 For Netware

    5.3 Upgrading Clusters from BCC 1.0 to BCC 1.1 SP2 for NetWare Upgrading from BCC 1.0 to BCC 1.1 SP2 while leaving the BCC configuration in place is a two- phased process where you must perform an intermediate upgrade to BCC 1.1 SP1 on NetWare 6.5 SP6 as follows: Initial Configuration Intermediate Configuration...
  • Page 59 For information, see “Updating an OES NetWare Server” (http://www.novell.com/ documentation/oes/install-nw/data/b7211uh.html) in the OES NetWare Installation Guide. See the Business Continuity Clustering 1.1 Readme file (http://www.novell.com/ documentation/bcc/pdfdoc/readme/readme111.pdf) for instructions on mandatory patches. 3c Issue the command on the node. cluster join 3d Upgrade Business Continuity Clustering from version 1.0 to 1.1 SP1 by installing BCC...

  • Page 60: Upgrading The Bcc Cluster From 1.1 Sp1 To 1.1 Sp2

    IMPORTANT: Make sure the administrator username meets the requirements specified in Section 4.3, “Configuring a BCC Administrator User,” on page 10 Verify that Novell Cluster Services and BCC 1.1 SP1 appear to be functioning correctly by performing the following tests: 10a Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and verify that it migrates correctly.
  • Page 61 OES 2 SP1 Readme (http:// www.novell.com/documentation/oes2/oes_readme/data/readme.html). NOTE: The DirXML plug-ins will be replaced by Identity Manager 3.5.1 plug-ins in Step 5 on page 3c1 In iManager, uninstall the old iManager plug-ins for Novell Cluster Services ), NSS ( ), Archive and Version Services (ncsmgmt.npm nssmgmt.npm...
  • Page 62 BCC Cluster from 1.0 to 1.1 SP1,” on page 12 Start the new Identity Manager drivers for each peer cluster. 13 Verify that Novell Cluster Services and BCC 1.1 SP2 appear to be functioning correctly by performing the following tests: 13a Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and verify that it migrates correctly.

  • Page 63: Upgrading Clusters From Bcc 1.1 Sp1 To Sp2 For Netware

    3 Upgrade NetWare 6.5 from version SP6 to SP8, and apply the latest patches for NetWare and Novell Cluster Services. You can perform a script upgrade by using NWCONFIG. For information, see “3.0 Upgrading to OES 2 SP1 NetWare” (http://www.novell.com/ documentation/oes2/inst_oes_nw/data/b7211uh.html) in the OES 2 SP1: NetWare Installation Guide.

  • Page 64: Authorizing The Bcc Administrator User

    NOTE: The DirXML plug-ins will be replaced by Identity Manager 3.5.1 plug-ins in Section 5.4.3, “Upgrading Identity Manager,” on page 4a In iManager, uninstall the old iManager plug-ins for Novell Cluster Services ), NSS ( ), Archive and Version Services ( (ncsmgmt.npm...

  • Page 65: Upgrading Identity Manager

    Section 4.1.7, “Identity Manager 3.5.1 Bundle Edition,” on page Make sure that the Identity Manager node meets the 3.5.1 upgrade requirements. For information, see “Upgrading” (http://www.novell.com/documentation/idm35/install/data/ ampxjxi.html) in the Identity Manager 3.5.1 Installation Guide. For information about installing or upgrading Identity Manager, see the Identity Manager 3.51...

  • Page 66: Verifying The Bcc Upgrade

    4 Start the new Identity Manager drivers for each peer cluster. 5.4.5 Verifying the BCC Upgrade Verify that Novell Cluster Services and BCC 1.1 SP2 appear to be functioning correctly by performing the following tests: 1 Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and verify that it migrates correctly.

  • Page 67: Configuring Business Continuity Clustering Software

    Business Continuity Cluster The Identity Manager preconfigured templates for iManager that were installed when you ran the Novell 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: A set of policies, filters, and objects that synchronize cluster resource information between any two of the peer clusters.

  • Page 68: Configuring The Identity Manager Drivers And Templates

    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. BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...
  • Page 69 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.

  • Page 70: Creating Ssl Certificates

    6.1.2 Creating SSL Certificates It is recommended that you create an SSL certificate for the Cluster Resource Synchronization driver. Creating one certificate creates the 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.

  • Page 71: Preventing Identity Manager Synchronization Loops

    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 B.5, “Synchronizing the BCC- Specific Identity Manager Drivers,”...
  • Page 72 Three-Cluster Identity Manager Synchronization Master Figure 6-2 Cluster Cluster Cluster Three 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 6-3. Alternate Three-Cluster Identity Manager Synchronization Scenario Figure 6-3 Cluster...

  • Page 73: Configuring Clusters For Business Continuity

    6.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: Section 6.2.1, “Enabling Clusters for Business Continuity,” on page 73 Section 6.2.2, “Adding Cluster Peer Credentials,”...

  • Page 74: Adding Cluster Peer Credentials

    When adding the administrator username, do not include the context for the user. For example, instead of bccadmin 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.

  • Page 75: Adding San Management Configuration Information

    To add resource script search-and-replace values: 1 In iManager, click Clusters > Cluster Options, select the Cluster object, click Properties, then select the Busines Continuity. 2 In the Resource Script Replacements section of the Business Continuity Cluster Properties page, click New. 3 Add the desired search-and-replace values.
  • Page 76 You can also add commands and Perl scripts to the resource scripts to call other scripts. Any command that can be run at the NetWare 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.
  • Page 77 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. 7c Click Apply and OK on the Script Details page, then click OK on the Resource Properties page to save your script changes.

  • Page 78: Verifying Bcc Administrator User Trustee Rights And Credentials

    You must also ensure that the BCC Administrator user has file system rights to the directory of all nodes in your BCC. This is necessary because _ADMIN:\Novell\Cluster the_ADMIN volume is virtual, and is created each time the server starts. For this reason, you cannot assign eDirectory trustee rights to the volume.

  • Page 79: Adding Resource Script Search-And-Replace Values

    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.

  • Page 80: Selecting Peer Clusters For The Resource

    To add resource script search-and-replace values specific to this resource: 1 In the Resource Replacement Script 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.

  • Page 81: Adding San Array Mapping Information

    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.
  • Page 82 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 83: Managing A Business Contiuity Cluster

    Managing a Business Contiuity 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 cluster to another, to modify peer credentials for existing clusters, and to generate reports of the cluster configuration and status.

  • Page 84: Migrating Cluster Resources Between Clusters

    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.

  • Page 85: Viewing The Current Status Of A Business Continuity Cluster

    6 Edit the administrator username and password that the selected cluster will use to connect to the selected peer cluster, then click OK. When specifying a username, you do not 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.

  • Page 86: Using Console Commands To View The Cluster Status

    7.3.2 Using Console Commands to View the Cluster Status 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 7.4 Generating a Cluster Report 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.

  • Page 87: Resolving Business Continuity Cluster Failures

    If BCC enabled resources need to be BCC disabled, remove the secondary peer clusters from the resource’s assigned list, then disable BCC only from the primary cluster, either by using iManager or command line. Do not BCC disable the same resource from multiple peer clusters. To disable BCC for a cluster resource: 1 Start your Internet browser and enter the URL for iManager.

  • Page 88: San-Based Mirroring Failure Types And Responses

    NOTE: The terms promote and demote are used here in describing the process of changing LUNs to a state of primary or secondary, but your SAN vendor documentation might use different terms such as mask and unmask. Section 7.6.1, “SAN-Based Mirroring Failure Types and Responses,” on page 88 Section 7.6.2, “Host-Based Mirroring Failure Types and Responses,”...

  • Page 89: Host-Based Mirroring Failure Types And Responses

    Secondary Cluster Fails but Secondary SAN Does Not No additional response is necessary for this failure other than recovering the secondary cluster. When you bring the secondary cluster back up, the LUNs are still in a secondary state to the primary SAN.
  • Page 90 Primary Cluster Fails but Primary SAN Does Not Response for this failure is the same as for SAN-based mirroring described in Primary Cluster Fails but Primary SAN Does Not Section 7.6.1, “SAN-Based Mirroring Failure Types and Responses,” on page 88. Do not disable MSAP (Multiple Server Activation Prevention), which is enabled by default.
  • Page 91 Intersite LAN Connectivity Is Lost Users might not be able to access servers in the primary cluster but can possibly access servers in the secondary cluster. If both clusters are up, nothing additional is required. An error is displayed. Wait for connectivity to resume.
  • Page 92 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 93: Virtual Ip Addresses

    Regardless of their virtual nature, virtual IP addresses and virtual NICs behave like physical IP addresses and physical NICs, and they are similarly configured by using either the INETCFG server-based utility or the Novell Remote Manager Web-based utility. Section 8.1, “Virtual IP Address Definitions and Characteristics,” on page 93 Section 8.2, “Virtual IP Address Benefits,”...

  • Page 94: Characteristics

    8.1.2 Characteristics Virtual IP addresses are unique in that they are bound to a virtual “ether” medium instead of to a “physical” network medium such as Ethernet. In other words, the virtual IP address space is different than the physical IP address space. As a result, virtual IP network numbers need to be different from physical IP network numbers.
  • Page 95 The following figure illustrates a multihomed server with all nodes running a dynamic routing protocol. Multihomed Server Running a Dynamic Routing Protocol Figure 8-1 Server 1.1.1.1 2.2.2.1 1.1.1.2 2.2.2.2 Router 1 Router 2 3.3.3.1 3.3.3.2 3.3.3.3 Client In this network, the server is a multihomed server hosting a critical network service. For simplicity, assume that all nodes are running some dynamic routing protocol.
  • Page 96 Multihomed Server Using Virtual IP Addresses Figure 8-2 4.4.4.1 (Virtual IP) Server 1.1.1.1 2.2.2.1 1.1.1.2 2.2.2.2 Router 1 Router 2 3.3.3.1 3.3.3.2 3.3.3.3 Client In this configuration, if the 1.1.1.1 interface were to fail, the client would ultimately learn the new route through Router 2 and would correctly forward packets to Router 2 instead of Router 1.

  • Page 97: Unlimited Mobility

    8.2.2 Unlimited Mobility Unlike physical IP addresses, which are limited in their mobility, virtual IP addresses are highly mobile. The degree of mobility is determined by the number of servers that an IP address on a specific server could be moved to. In other words, if you choose a physical IP address as an IP address of a network resource, you are limiting the set of potential servers to which this resource could transparently fail over to.

  • Page 98: Reducing The Consumption Of Additional Ip Addresses

    IP address or, a unique virtual IP address. Furthermore, consider that each virtual IP address belongs to a virtual IP network whose route is being advertised by a single node within a cluster. Because Novell Cluster Services can migrate a service and its virtual IP address from one node to another, the virtual IP network must migrate to the same node as the service.

  • Page 99: Configuring Virtual Ip Addresses

    4. If the cluster resource is a clustered-enabled pool or volume, the IP address of that resource ® needs to be changed to the virtual IP address. You can do this by using ConsoleOne , Novell Remote Manager, or iManager. This change is not needed for any non-volume cluster resources like DHCP.

  • Page 100: Displaying Bound Virtual Ip Addresses

    8.4.1 Displaying Bound Virtual IP Addresses To verify that a virtual IP address is bound, enter at the server display secondary ipaddress console of the cluster server where the virtual IP address is assigned. This displays all bound virtual IP addresses. A maximum of 256 virtual IP addresses can be bound. 100 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 101: Troubleshooting Business Continuity Clustering 1.1

    Troubleshooting Business Continuity Clustering 1.1 ® This section contains the following topics to help you troubleshoot Novell Business Continuity Clustering 1.1. Section 9.1, “Cluster Connection States,” on page 101 Section 9.2, “Driver Ports,” on page 103 Section 9.3, “Excluded Users,” on page 103 Section 9.4, “Security Equivalent User,”...
  • Page 102 Ping the peer cluster to see if it is up to the selected peer cluster. and reachable. Ensure that BCC is running on the peer cluster and that Novell Cluster Services is running on the servers in the peer cluster.

  • Page 103: Driver Ports

    2 Using an editor, open the file that is referenced in the message that appears. You can get additional information on how to use the log file by entering at the help log NetWare server console. 9.2 Driver Ports If your Identity Manager driver or drivers won’t start, check for a port number conflict. Identity Manager driver port numbers must not be the same as other driver port numbers in the cluster or ports being used by other services such as Apache.

  • Page 104: Security Equivalent User

    To see the excluded users list: 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.

  • Page 105: Certificates

    If SSL certificates are not present or have not been created, Identity Manager drivers might not start or function properly. Novell recommends using SSL certificates for encryption and security. NOTE: You should create or use a different certificate than the default (dummy) certificate (BCC Cluster Sync KMO) that is included with BCC.

  • Page 106: Bcc Startup Flags

    This is helpful for reporting problems to Novell Support. 9.8 Problems with Installing BCC on NetWare Occasional problems might exist when installing BCC software on NetWare cluster servers.

  • Page 107: Identity Manager Drivers Do Not Synchronize Objects From One Cluster To Another

    Selecting the Auto Start option is recommended. Unknown communications problems. Section 9.11, “Tracing Identity Manager Communications,” on page 108. -670 errors in the DSTrace logs. See TID # 10090395 (http://support.novell.com/docs/Tids/ Solutions/10090395.html) This is commonly caused by loading before SAS, which causes problems when rconag6.nlm Identity Manager tries to load.

  • Page 108: Tracing Identity Manager Communications

    This is because BCC and iManager use the tree key to encrypt the credentials. Setting credentials by using iManager in a different tree uses an invalid tree encryption. LIBC has not been updated. See TID # 2974119 (http://support.novell.com/docs/Readmes/ InfoDocument/2974119.html). A firewall is blocking port 5988 or 5989 (CIM).

  • Page 109: Administration Of Peer Clusters Not Functional

    On the resource object, change the NCS:BCC State attribute to 0 to set the resource to the primary state. Also, increment the NCS:Revision attribute one number so that Novell Cluster Services recognizes that the resource properties have been updated. See...

  • Page 110: Resource Script Search-And-Replace Functions Do Not Work

    To resolve this problem, edit the resource unload script and change the line to NUDP DEL name ip . Unlike the command, the command does not wait for all NCP NUDP ODEL name ip ODEL connections to close. This makes it much faster. NOTE: The cluster resource must be brought offline and then back online for changes to the unload script to take effect.

  • Page 111: The Ip Address, Virtual Server Dn, Or Pool Name Does Not Appear On The Imanager Cluster Configuration Page

    If you get an error in iManager with a blank error string (no text appears with the error message) while attempting to bring a resource online, it is possible that Novell Cluster Services views the resource as secondary even though BCC has changed the resource to primary and iManager shows the resource as primary.

  • Page 112: Mapping Drives In Login Scripts

    SLP Server Name is the name being advertised in SLP as specified in the resource load script. This method requires a client reboot. TID 10057730 (http://support.novell.com/docs/Tids/Solutions/10057730.html) information on modifying the server cache Time To Live (TTL) value on the Novell Client 9.23 Mapping Drives to Home Directories by Using the %HOME_DIRECTORY Variable...

  • Page 113: Bcc Error Codes

    #!ICE -b -D LDAP -d cn=root,ou=servers,o=lab -w novell -S LDIF -f #@ -s0 -w20 version: 1 dn: cn=HOMES_REF, ou=servers,o=lab changetype: modify replace: hostServer hostServer: cn=BCC_CLUSTER_HOMES_SERVER,ou=From_BCCP,ou=servers,o=lab The first line in the sample script instructs NSMI to run the ICE utility. The -b parameter automatically closes the ICE window.
  • Page 114 1017 Invalid BCC API version. 1018 Could not find a pool for the specified cluster resource. 1019 Error managing the SAN via the Novell SAN Management Interface. 1020 CIM Client error. 1021 Error creating a system resource (mutex, semaphore, etc.).

  • Page 115: Security Considerations

    Section 10.3, “General Security Guidelines,” on page 120 Section 10.4, “Security Information for Dependent Products,” on page 120 10.1 Security Features ® The following table contains a summary of the security features of Novell Business Continuity Clustering 1.2: Business Continuity Clustering 1.2 Security Features...

  • Page 116: Security Configuration

    10.2 Security Configuration The following subsections provide a summary of security-related configuration settings for Business Continuity Clustering 1.1: Section 10.2.1, “BCC Configuration Settings,” on page 116 Section 10.4, “Security Information for Dependent Products,” on page 120 10.2.1 BCC Configuration Settings The following table lists the BCC configuration settings that are security-related or impact the security of BCC: BCC Security Configuration Settings...

  • Page 117: Changing The Ncs: Bcc Setings Attribute In The Bcc Xml Configuration

    XML Configuration WARNING: You should not change the configuration settings for the NCS:BCC Settings attribute unless instructed to do so by Novell Support. Doing so can have adverse affects on your cluster nodes and BCC. The following XML for the NCS:BCC Settings attribute is saved on the local Cluster object in eDirectory.
  • Page 118 <idlePriorityThreshold>3</idlePriorityThreshold> <initialNormalThreads>3</initialNormalThreads> <initialPriorityThreads>2</initialPriorityThreads> <ipcResponseTimeout>15</ipcResponseTimeout> <maximumPriorityThreads>20</maximumPriorityThreads> <minimumPriorityThreads>2</minimumPriorityThreads> <resourceOfflineTimeout>300</resourceOfflineTimeout> <resourceOnlineTimeout>300</resourceOnlineTimeout> <scanForNewDevicesDelay>5</scanForNewDevicesDelay> </bccSettings> Table 10-3 provides additional information on each setting: BCC XML Settings Table 10-3 Setting Description Default Value The name of the LUM-enabled group that bccgroup <adminGroupName> BCC uses on Linux. <authorizationCacheTTL>...

  • Page 119: Disabling Ssl For Inter-Cluster Communication

    To turn off SSL for inter-cluster communication, or to specify a different communication port, you need to modify the Novell Cluster Services Cluster object that is stored in eDirectory by using an ®...

  • Page 120: General Security Guidelines

    The changes do not take effect until either a reboot of each cluster node, or a restart of the Business Continuity Clustering software on each cluster node. The following table provides an example of possible combinations of scheme and port specifier for tag for values of the NCS:BCC Peers attribute: <address>...
  • Page 121 “Enabling and Configuring iSCSI Initiator Security” in the OES 2 SP 1: iSCSI 1.1.3 for NetWare Administration Guide. Novell Cluster Services for NetWare In the OES 2 SP2: Novell Cluster Services 1.8.5 for NetWare Administration Guide, see “Configuration Requirements”. Novell Storage Services for NetWare...
  • Page 122 122 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 123: A Console Commands For Bcc

    Console Commands for BCC ® Novell Business Continuity Clustering (BCC) provides server console commands to help you perform certain BCC management tasks. Some of the commands can also be used to manage Novell Cluster Services clusters. Table A-1 lists the server console commands for managing a business continuity cluster and gives a brief description of each command.
  • Page 124 Console Command Description Enables Business Continuity Clustering for the cluster enable [resource] 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.
  • Page 125 Console Command Description cluster refresh This command should not be used except under the direction of Novell Support. Console Commands for BCC 125...
  • Page 126 126 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 127: B Implementing A Multiple-Tree Bcc

    ® (SP) 2 for NetWare 6.5 SP8 (same as Novell Open Enterprise Server (OES) 2 SP1 NetWare), the information is also useful for configuring and managing BCC in a multiple-tree environment. This section contains additional instructions and information for multiple-tree BCC implementations.

  • Page 128: Ssl Certificates For Drivers

    The BCCAdmin user needs administrator rights in the container where the User objects reside so that User objects can be synchronized between eDirectory trees. For information, see Section 4.1.5, “Novell eDirectory 8.8,” on page B.1.3 SSL Certificates for Drivers In a multiple-tree business continuity cluster, you should create separate SSL certificates for the Cluster Resource Synchronization driver and for the User Object Synchronization driver.

  • Page 129: Creating Ssl Certificates

    Descriptions of the information required are also included with each field. Additional information for the wizard page fields can be found in “Importing the Sample Driver Configuration” (http://www.novell.com/documentation/dirxmldrivers/edirectory/data/ bozojif.html) in the Identity Manager Driver for eDirectory Implementation Guide. 9 In the left column of the iManager page, click Identity Manager, then click Identity Manager Overview.

  • Page 130: Synchronizing The Bcc-Specific Identity Manager Drivers

    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.

  • Page 131: Preventing Identity Manager Synchronization Loops

    B.6 Preventing Identity Manager Synchronization Loops If you have three or more clusters each in separate eDirectory trees in your business continuity cluster, you should set up IDM User object and Cluster Resource object synchronization in a manner that prevents Identity Manager synchronization loops. Identity Manager synchronization loops can cause excessive network traffic and slow server communication and performance.

  • Page 132: Migrating Resources To Another Cluster

    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 B-3. Alternate Three-Cluster Identity Manager Synchronization Scenario Figure B-3 Cluster IDM Sync Cluster Cluster Three...

  • Page 133: C Setting Up Auto-Failover

    Setting Up Auto-Failover ® Auto-failover is available beginning in Novell Business Continuity Clustering 1.1. To set up the auto-failover feature, you must enable it, then configure the auto-failover settings. WARNING: Auto-failover is disabled by default and is not recommended. It should only be enabled after a thorough examination and review of your network and geographic site infrastructure.

  • Page 134: Creating An Auto-Failover Policy

    8 Click the Auto-Failover link just under the tabs. 9 Select the Enable Automatic Failover of Business Continuity Cluster Resources check box, then click Apply. 10 Continue with Section C.2, “Creating an Auto-Failover Policy,” on page 134 to create a failover policy.
  • Page 135 These conditions can be combined in any order to construct a more robust rule that helps to avoid an undesired failover. For failover to occur, each condition of only one rule must be satisfied for the specified cluster or clusters. For rules with monitor conditions automatically created by using the Cluster Membership Monitoring Settings table, you can add a condition that tests if the connection to the peer cluster is up.

  • Page 136: Adding Or Editing Monitor Configurations

    The nodepnt and nodecnt monitors do not support optional parameters. 6 Click Apply to save your settings. NOTE: See the BCC NDK documentation (http://developer.novell.com/documentation/cluster/ index.html?page=/documentation/cluster/ncss_enu/data/bktitle.html) for more information on creating custom failover policies. 136 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8...

  • Page 137: D Configuring Host-Based File System Mirroring For Nss Pools

    For information about storage-based mirroring, consult your storage system vendor or see the storage system vendor documentation. Host-based synchronous mirroring functionality is included with the Novell Storage Services (NSS) file system (NSS mirroring) that is part of NetWare 6.5. NSS mirroring is a checkpoint-based synchronous mirroring solution.

  • Page 138: Creating And Mirroring Nss Partitions On Shared Storage

    Section D.2, “Creating NSS Volumes,” on page 139 Section D.3, “Novell Cluster Services Configuration and Setup,” on page 140 Section D.4, “Checking NSS Volume Mirror Status,” on page 140 D.1 Creating and Mirroring NSS Partitions on Shared Storage NSS provides a software RAID 1 configuration option that mirrors NSS pool partitions. The partitions are automatically created by the NSS management tools when you create a pool and when you mirror the pool.

  • Page 139: Creating Nss Volumes

    You can select one or all of the advertising protocols. NCP™ is the protocol used by Novell clients, CIFS is the protocol used by Microsoft clients, and AFP is the protocol used by Macintosh clients. Selecting any of the protocols causes lines to be added to the pool resource load and unload scripts to activate the selected protocols on the cluster.

  • Page 140: Novell Cluster Services Configuration And Setup

    “Configuring a Cluster Resource for (Cluster Enabling) an NSS Pool and Its Volumes” in the OES 2 SP2: Novell Cluster Services 1.8.5 for NetWare Administration Guide. When you cluster-enable a shared disk pool, the commands to start and stop the pool resource are automatically added to the resource load and unload scripts.

  • Page 141: E Documentation Updates

    If you are a new user, simply read the guide in its current state. Refer to the publication date, which appears on the title page, to determine the release date of this guide. For the most recent version of the Novell Business Continuity Clustering 1.1 for NetWare Administration Guide, see the Business Continuity Clustering Documentation Web site (http:// www.novell.com/documentation/bcc/).

  • Page 142: E.1.3 Upgrading Business Continuity Clustering For Netware

    E.1.3 Upgrading Business Continuity Clustering for NetWare Location Change Section 5.2, “Disabling BCC This section is new. 1.0, Upgrading Servers to NetWare 6.5 SP8, then Enabling BCC 1.1 SP2,” on page 56 E.2 April 28, 2009 Updates were made to the following sections. The changes are explained below. Section E.2.1, “Converting BCC Clusters from NetWare to Linux,”...

Table of Contents