1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 -...
  6. Manual

Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Novell
Business Continuity Clustering
for NetWare
®
w w w . n o v e l l . c o m
1 . 1
A D M I N I S T R A T I O N G U I D E
F e b r u a r y 1 5 , 2 0 0 8

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION

Summary of Contents for Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION

  • Page 1 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide Novell Business Continuity Clustering for NetWare ® w w w . n o v e l l . c o m 1 . 1 A D M I N I S T R A T I O N G U I D E...
  • 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 5: Table Of Contents

    2.1.3 Novell Cluster Services 1.8.2 for NetWare ....... . 20 2.1.4...
  • Page 6 Displaying Bound Virtual IP Addresses ........80 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 7 A Implementing a Multiple-Tree BCC Copying User Objects Using IDM ..........81 Configuring User Object Synchronization .
  • Page 8 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 9: About This Guide

    BCC 1.1 Documentation Web site (http://www.novell.com/documentation/ bcc11/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. ® , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party A trademark symbol ( trademark.
  • Page 10 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 11: Overview

    1.2 Disaster Recovery Implementations There are two main Novell Cluster Services implementations that you can use to achieve your desired level of disaster recovery. These include a stretch cluster and a cluster of clusters. The Novell Business Continuity Cluster product automates some of the configuration and processes used in a cluster of clusters.

  • Page 12: Stretch Clusters Vs. Cluster Of Clusters

    Typically, replication of data blocks between SANs is performed by SAN hardware, but it can be done by host-based mirroring for synchronous replication over short distances. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 13 Cluster of Clusters Figure 1-2 Two independent clusters at geographically separate sites Building A Building B Ethernet Switch Ethernet Switch eDirectory DirXML Server Server Server Server Server Server Server Server Fibre Channel Fibre Channel Switch Switch Disk blocks Fibre Channel Fibre Channel Disk Arrays Disk Arrays...
  • Page 14 An SBD partition must be mirrored between sites. It accommodates only two sites. All IP addresses must reside in the same subnet. The eDirectory partition must span the cluster. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 15: Novell Business Continuity Clusters

    1.2.2 Novell Business Continuity Clusters Novell Business Continuity Clusters is a cluster of clusters similar to what is described above, except that the cluster configuration, maintenance, and synchronization have been automated by adding specialized software. Novell Business Continuity Clustering software is an integrated set of tools to automate the setup and maintenance of a Business Continuity infrastructure.

  • Page 16: Usage Scenarios

    The first option is typically used when the purpose of the secondary site is primarily testing by the IT department. The second option is typically used in a company that has more than one large site of operations. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 17 Two-Site Business Continuity Cluster Figure 1-3 Two independent clusters at geographically separate sites Building A Building B Ethernet Switch Ethernet Switch eDirectory DirXML Server Server Server Server Server Server Server Server Fibre Channel Fibre Channel Switch Switch Disk blocks Fibre Channel Fibre Channel Disk Arrays Disk Arrays...
  • Page 18 In either case, snapshot technology can allow for asynchronous replication over long distances. However, the lower cost solution does not necessarily have the performance associated with higher-end Fibre Channel storage arrays. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 19: Installation And Setup

    Installation and Setup ® This section covers the following information to help you install, set up, and configure Novell Business Continuity Clustering for your specific needs: Section 2.1, “Requirements,” on page 19 Section 2.2, “Installing Identity Manager,” on page 21 Section 2.3, “Installing Novell Business Continuity Cluster Software,”...

  • Page 20: Novell Edirectory 8.8

    2.1.3 Novell Cluster Services 1.8.2 for NetWare Two to four clusters with Novell Cluster Services™ 1.8.2 (the version that ships with NetWare 6.5 Support Pack 5) or later installed and running on each node in the cluster. Each cluster must have a unique name, even if the clusters reside in different Novell eDirectory™...

  • Page 21: Openwbem

    SAN) is required for each cluster in the business continuity cluster. See “Shared Disk System Requirements” in the OES Novell Cluster Services 1.8.2 Administration Guide for NetWare. 2.1.10 Link Speeds For real-time mirroring, link speeds should be 1 GB or better, the fibre-channel cable length between sites should be less than 200 kilometers, and the links should be dedicated.
  • Page 22 IDM 3.0.1 is supported with BCC 1.1 Support Pack 1 and is included with the IDM 3.0.1 Bundle Edition. Instructions for installing and configuring the IDM 3.0.1 Bundle Edition can be found with IDM 3.0.1 Bundle Edition Documentation (http://www.novell.com/documentation/oes/implgde/ index.html?page=/documentation/oes/implgde/data/b4dgr2g.html#b4dgr2k). Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 23: Installing Novell Business Continuity Cluster Software

    2.3 Installing Novell Business Continuity Cluster Software It is necessary to run the Novell Business Continuity Clustering installation program when you want Install the Business Continuity Cluster engine software on cluster nodes for the clusters that will be part of a business continuity cluster.
  • Page 24 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 procedure for each cluster that will be part of the business continuity cluster. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 25: Business Continuity Cluster Component Locations

    Cluster Site 2 Figure 2-1 uses the following abbreviations: BCC eng. -- Business Continuity Cluster engine NCS -- Novell Cluster Services IDM eng. -- Identity Manager engine IDM eDir Driver -- Identity Manager eDirectory Driver NW 6.5 -- NetWare 6.5 2.4 Configuring File System Mirroring...

  • Page 26: Configuring Nss Mirroring

    When you create a Novell Cluster Services system that utilizes shared storage space (a Storage Area Network or SAN), it is important to remember that all servers attached 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 27 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 Installation and Setup...
  • Page 28 Checking NSS Volume Mirror Status After you have configured NSS mirroring with Novell Cluster Services, you should check to ensure that it is working properly in a cluster environment. 1 Ensure that the volumes on the cluster-enabled pool are mounted on the assigned server by entering volumes at the server console.

  • Page 29: Configuring San-Based Mirroring

    After you have installed and configured IDM and the Business Continuity Cluster software, and you have configured file system mirroring, you need to set up Novell Business Continuity Cluster software. Instructions contained in this section for setting up Novell Business Continuity Cluster software consists of: “Configuring Business-Continuity-Specific IDM Drivers”...
  • Page 30 Step 1 on page 32 for instructions on creating SSL certificates. DNS name of other IDM node: Specify the DNS name or IP address of the IDM server in the other cluster. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 31 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 specificly for these cluster pool and volume objects. You would then specify the context of the new container in this step.
  • Page 32 2 Enter your username and password. 3 In the left column, click DirXML, then click the DirXML Overview link. 4 Search for and find the BCC driver set. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 33 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, then click Selecting the cluster object will cause the BCC-specific cluster IDM drivers to synchronize.
  • Page 34 In order for a cluster to appear in the list of possible peer clusters, that cluster must: Have Business Continuity Cluster software installed. Have IDM installed. Have business continuity-specific IDM drivers configured and running. Be enabled for business continuity. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 35: Configuring Clusters For Business Continuity

    2.5.2 Configuring Clusters for Business Continuity This procedure consists of “Enabling Clusters for Business Continuity” on page 35 “Adding Cluster Peer Credentials” on page 35 “Adding Resource Script Search and Replace Values” on page 36 These tasks must be performed on each separate cluster that you want to be part of the business continuity cluster.
  • Page 36 When adding the administrator username, do not include the context for the user. For example, bccadmin could be used instead of something like bccadmin.prv.novell. NOTE: 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 37 You can also specify global search and replace addresses for multiple resources in one line. This can be used 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.
  • Page 38 Synchronous: If this check box is left unchecked, multiple scripts can be run concurrently. Checking the box causes scripts to run individually, one after another. Most SAN vendors do not support running multiple scripts concurrently. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 39 You must also ensure that the BCC administrative user has file system rights to the _ADMIN:\Novell\Cluster directory of all nodes in your BCC. This is necessary because the_ADMIN volume is virtual, and is created each time the server starts. For this reason, you can’t assign eDirectory trustee rights to the _Admin volume.
  • Page 40 To assign BCC administrative user file system rights to the _ADMIN:\Novell\Cluster directory: 1 Open the sys:/etc/trustrees.xml file 2 Add a trustee entry for the BCC Administrative user that assigns Read, Write, Modify, and File Scan (RWMF) rights to the _ADMIN:\Novell\Cluster directory.

  • Page 41: Configuring Cluster Resources For Business Continuity

    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 using iManager in the Novell Cluster Services 1.8.2 Administration Guide for NetWare, then continue with Step 3 below.
  • Page 42 You should contact Novell Technical 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 43: Managing A Novell Business Continuity Cluster

    2.6 Managing a Novell Business Continuity Cluster After you have installed, set up, and configured Novell Business Continuity Cluster 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...

  • Page 44: Migrating A Cluster Resource To Another Cluster

    Section 2.6.6, “Business Continuity Cluster Console Commands,” on page 47 2.6.1 Migrating a Cluster Resource to Another Cluster 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 Appendix B, “Setting Up Auto-Failover,”...

  • Page 45: Changing Cluster Peer Credentials

    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 don’t need to include the Novell eDirectory context for the user name.

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

    2 Enter your username and password. 3 In the left column, click Clusters, then click the Cluster Manager link. 4 Specify a cluster name or browse and select one. 5 Click the Run Report button. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 47: Disabling Business Continuity Cluster Resources

    Some of the commands can be used both with Novell Cluster Services and with Novell Business Continuity Clustering. The following table lists the BCC-related server console commands and gives a brief description of each command.
  • Page 48 (destination) cluster. Specifying * for the resource name will migrate all BCC-enabled resources. Specifying * for the node name will bring the resource online at the most preferred node. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 49: Business Continuity Cluster Failure Types

    BCC. CLUSTER REFRESH This command should not be used except under the direction of Novell Technical Services. 2.7 Business Continuity Cluster Failure Types There are several failure types associated with a business continuity cluster that you should be aware of.

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

    Bring the secondary SAN back up and follow your SAN vendor's instructions to remirror. When you bring the secondary cluster back up, the LUNs will still be in a secondary state to the primary SAN. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

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

    Primary SAN Fails but Primary Cluster Does Not When the primary SAN fails, the primary cluster will also fail. Bring the primary SAN back up and follow your SAN vendor’s instructions to remirror and, if necessary promote the former primary SAN back to primary.
  • Page 52 Additional response is the same as for SAN-based mirroring described above. Intersite LAN Connectivity is Lost Response for this failure is the same as for SAN-based mirroring described above. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 53: Upgrading Bcc

    Upgrading BCC ® ® BCC 1.0 supports only Novell Cluster Services for NetWare . This section covers two upgrade scenarios: Section 3.1, “Upgrading BCC 1.0 to BCC 1.1 for NetWare,” on page 53 Section 3.2, “Upgrading BCC 1.0 to BCC 1.1 for Linux,” on page 55 3.1 Upgrading BCC 1.0 to BCC 1.1 for NetWare...

  • Page 54: Installing Or Upgrading Idm

    After upgrading NetWare and IDM, you must install BCC 1.1 on all cluster nodes that will be part of your BCC. See Section 2.3, “Installing Novell Business Continuity Cluster Software,” on page 23 for information on installing BCC 1.1. The BCC 1.1 installation program autodetects if BCC 1.0 is installed and performs the necessary updates to convert BCC 1.0 to BCC 1.1.

  • Page 55: Verifying San Scripts

    NetWare Cluster to Linux (http://www.novell.com/documentation/oes/cluster_admin_lx/data/ bu1b1x8.html) in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. Clusters containing NetWare and Linux servers are only supported in a BCC as a temporary means to convert a cluster from NetWare to Linux. Part of the temporary conversion state includes a restriction that only one mixed cluster can exist in your BCC.
  • Page 56 BCC. You can only migrate or fail over NSS pool/volume resources between clusters in a mixed BCC. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 57: Troubleshooting Bcc 1.1

    Troubleshooting BCC 1.1 ® This section contains the following topics to help you troubleshoot Novell Business Continuity Clustering (BCC) 1.1. Section 4.1, “Cluster Connection States,” on page 57 Section 4.2, “Driver Ports,” on page 59 Section 4.3, “Excluded Users,” on page 59 Section 4.4, “Security Equivalent User,”...
  • Page 58 ® To view the log file on NetWare 1 Enter log +copy syslog. 2 Using an editor, open the file that is referenced in the message that appears. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 59: Driver Ports

    You can get additional information on how to use the log file by entering help log at the NetWare server console. 4.2 Driver Ports If your IDM driver or drivers won’t start, check for a port number conflict. IDM driver port numbers must not conflict (be the same) with other driver port numbers in the cluster or ports being used by other services (Apache, etc.).

  • Page 60: Security Equivalent User

    2 Enter your username and password. 3 In the left column, click DirXML, then click the DirXML Overview link. 4 Choose Search Entire Tree, then click Search. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 61: Certificates

    If SSL certificates are not present or have not been created, IDM 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 62: Bcc Startup Flags

    Linux On Linux, there are two options: To use the v and t flags, edit the /etc/init.d/novell-bcc file and change the NOVELL_BCCD_ARGS= line to NOVELL_BCCD_ARGS=-flags. Replace flags with any combination of v and/or t. This could include v, vt, t, or tv.

  • Page 63: Idm Drivers For Cluster Synchronization Do Not Start

    To resolve this and similar problems, rename the c:\program files\common files\novell directory on the Windows machine where the installation is being run and restart the BCC 1.1 installation program. 4.9 IDM Drivers for Cluster Synchronization Do Not Start If the IDM drivers for cluster synchronization will not start, the problem may be caused by one of the following conditions: A certificate has not been created.

  • Page 64: Tracing Idm

    The trace file is located at sys:/system/dstrace.log. You might want to delete this file before starting a trace so the events logged in the file are specific to the actions you are tracing. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 65: Peer Cluster Communication Not Working

    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 66: Dumping Syslog On Netware

    If the IP address for a virtual (NCP) server does not change properly, the problem may be caused by one of the following conditions: The IP address has been changed only on the load and unload script pages. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

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

    You must also change the IP address on the protocols page for the virtual server. Changing the IP address on the protocols page will cause the load and unload scripts to automatically update. The virtual server has an extra IP address. ®...

  • Page 68: Blank Error String Imanager Error Appears While Bringing A Resource Online

    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 69: Mapping Drives To Home Directories Using The %Home_Directory Variable

    LDIF/ICE and the NSMI script, you must have two NCF files: one for the SAN, and one for LDIF/ICE. The NSMI script must then call each NCF file separately. A sample NSMI script is included below. #!ICE -b -D LDAP -d cn=root,ou=servers,o=lab -w novell -S LDIF -f #@ -s0 -w20 version: 1...

  • Page 70: Bcc Error Codes

    Failure to add the wait will cause the temporary LDIF file to be deleted before ICE can read it. This will cause ICE to fail. 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. 4.25 BCC Error Codes The following table lists the different BCC error codes by number and gives a brief description for each error code.
  • Page 71 Error Code Number Message 1020 CIM Client error 1021 Error creating a system resource (mutex, semaphore, etc.) 1022 File IO error 1023 No Data 1024 Not a member of cluster 1025 Invalid token in script 1026 Invalid or unknown cluster 1027 The NSMI script is too long.
  • Page 72 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 73: Virtual Ip Addresses

    Section 5.1.2, “Characteristics,” on page 74 5.1.1 Definitions Virtual driver: The vnic.lan driver provided by Novell. Virtual board (NIC): Any board configured to use the virtual driver. Virtual IP address: Any IP address that is bound to a virtual board.

  • Page 74: Characteristics

    Also, because all other real links are forcibly made to act as intermediate links, their failures are easily worked around by the dynamic routing protocols. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...
  • Page 75 The following figure illustrates a multihomed server with all nodes running a dynamic routing protocol. Multihomed Server Running a Dynamic Routing Protocol Figure 5-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 76 The resilience against interface failures provided by virtual IP addresses depends on the fault resilience provided by the dynamic routing protocols, as well as on fault recovery features such as retransmissions built into the application logic. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 77: Unlimited Mobility

    5.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 be transparently failed-over to.

  • Page 78: Reducing The Consumption Of Additional Ip Addresses

    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. If multiple virtual IP...

  • Page 79: Configuring Virtual Ip Addresses

    The virtual IP addresses on a given virtual IP network must go unused, thereby wasting a portion of the available address space. Neither of these situations is desirable. Fortunately, the use of host masks remedies both. 5.5 Configuring Virtual IP Addresses The routers in a virtual IP address configuration must be running the RIP I or RIP II protocols.

  • Page 80: Displaying Bound Virtual Ip Addresses

    IP address is assigned. This will display all bound virtual IP addresses. A maximum of 256 virtual IP addresses can be bound. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 81: A Implementing A Multiple-Tree Bcc

    DirXML to quickly copy the 10,000 users to the new tree. For more information on copying User objects using IDM, see Migrating or Copying User objects (http://www.novell.com/documentation/idmdrivers/index.html?page=/documentation/idmdrivers/ edirectory/data/brj81j4.html) in the Identity Manager Driver for eDirectory Implementation Guide.

  • Page 82: Creating Ssl Certificates

    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: Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 83: Synchronizing Idm Drivers

    cn=DriverName.ou=OrganizationalUnitName.o=OrganizationName A.4 Synchronizing IDM Drivers After creating BCC-specific IDM drivers and SSL certificates, if you are adding a new cluster to an existing business continuity cluster in a multiple eDirectory tree BCC, you must synchronize the BCC-specific IDM drivers for the Cluster and User objects. If BCC-specific IDM drivers are not synchronized, clusters can’t be enabled for business continuity.
  • Page 84 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 is illustrated in Figure 2-5 below. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 85: Migrating Resources To Another Cluster

    Alternate Three-Cluster IDM Synchronization Scenario Figure A-3 Cluster DirXML Sync Cluster Cluster Three 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 Business Continuity Cluster software installed.
  • Page 86 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 87: B Setting Up Auto-Failover

    Setting Up Auto-Failover Auto-Failover is available in Business Continuity Clustering 1.1 and later. 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 88: Creating An Auto-Failover Policy

    1 Under Failover Policy Configuration, select a policy and click Edit to further refine that rule. Click Delete to remove that rule, or click New to create a new rule that you can add the additional failover conditions to. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 89: Adding Or Editing Monitor Configurations

    2 Select the cluster that you want the rule to apply to, or select All to apply the policy to all clusters. 3 Under Conditions, choose the type of condition and the appropriate values. To add multiple conditions to the rule, click the Add button below the condition. You can use the default setting of Monitor if you don't want to apply the cluster up or cluster down criteria to this policy.
  • Page 90 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. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 91: C Security Considerations

    Security Considerations This section contains specific instructions on how to configure and maintain a Business Continuity Cluster in the most secure way possible. It contains the following subsections: Section C.1, “Security Features,” on page 91 Section C.2, “Security Configuration,” on page 91 Section C.3, “Other Security Considerations,”...

  • Page 92: Bcc Configuration Settings

    WARNING: You should not change these configuration settings unless instructed to do so by Novell Technical Services. Doing so may have adverse affects on your cluster nodes and BCC. The following XML is saved on the NCS:BCC Settings attribute on the local cluster object in eDirectory.
  • Page 93 <scanForNewDevicesDelay>5</scanForNewDevicesDelay> </bccSettings> On linux, the above XML is written to /etc/opt/novell/bcc/bccsettings.xml. It should be noted that on linux this file might be overritten by BCC at any time. Therefore, any changes to this file on linux will be ignored and lost. All changes should be made in eDirectory.
  • Page 94 The changes will not take effect until either a reboot of each cluster node, or by a restart of BCC software on each cluster node. The following table provides an example of possible combinations of scheme and port specifier for the <address> tag for values of the NCS:BCC Peers attribute: Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 95: Security Information For Other Products

    Security for eDirectory is provided by NICI. See the NICI 2.7x Administration Guide (http://www.novell.com/documentation/ nici27x/nici_admin_guide/data/a20gkue.html) Identity Manager (IDM) Security: Best Practices (http://www.novell.com/ documentation/idm/admin/data/b1bsw73.html) in the IDM Administration Guide. iSCSI Configuring Access Control to iSCSI Targets (http:// www.novell.com/documentation/iscsi1_nak/iscsi/data/ h2mdblj1.html) Enabling and Configuring iSCSI Initiator Security (http://www.novell.com/documentation/iscsi1_nak/...

  • Page 96: Other Security Considerations

    If a server is accessible from outside the corporate network, a local server firewall should be employed to prevent direct access by a would-be intruder. Audit logs should be kept and analyzed periodically. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

  • Page 97: D Documentation Updates

    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/index.html).

  • Page 98: Troubleshooting Bcc 1.1

    Location Change Section 4.4, “Security The NCP server objects for the virtual server of a BCC enabled resource Equivalent User,” on page 60 will also be placed in the landing zone. Novell Business Continuity Clustering 1.1 for NetWare Administration Guide...

Table of Contents