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

Novell BUSINESS CONTINUITY CLUSTERING 1.0 - ADMINISTRATION Manual

Hide thumbs Also See for BUSINESS CONTINUITY CLUSTERING 1.0 - ADMINISTRATION:
Table of Contents

Advertisement

Quick Links

Download this manual
Novell
Business Continuity Clustering
w w w . n o v e l l . c o m
1 . 0
A D M I N I S T R A T I O N G U I D E
M a y 2 2 , 2 0 0 6

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell BUSINESS CONTINUITY CLUSTERING 1.0 - ADMINISTRATION

Summary of Contents for Novell BUSINESS CONTINUITY CLUSTERING 1.0 - ADMINISTRATION

  • Page 1 Novell Business Continuity Cluster Services 1.0 Administration Guide Novell Business Continuity Clustering w w w . n o v e l l . c o m 1 . 0 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 Client is a trademark of Novell, Inc. Novell Cluster Services is a trademark of Novell, Inc. Novell Directory Services and NDS are registered trademarks of Novell, Inc. in the United States and other countries. Novell Storage Services is a trademark of Novell, Inc.

  • Page 5: Table Of Contents

    Managing Novell Business Continuity Clustering ........39...
  • Page 6 Displaying Bound Virtual IP Addresses ........54 Novell Business Continuity Cluster Services 1.0 Administration Guide...

  • Page 7: About This Guide

    In this 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. When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash.
  • Page 8 Novell Business Continuity Cluster Services 1.0 Administration Guide...

  • Page 9: 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 10: Stretch Clusters Vs. Cluster Of Clusters

    A cluster of clusters consists of two or more clusters in which each cluster is located in a geographically separate area. A cluster of clusters provides the ability to fail over selected or all cluster resources from one cluster to another cluster. Typically, replication of data blocks between Novell Business Continuity Cluster Services 1.0 Administration Guide...
  • Page 11 SANs is performed by SAN hardware, but it can be done by host-based mirroring for synchronous replication over short distances. Cluster of Clusters Figure 1-2 Two independent clusters at geographically separate sites Building A Building B Ethernet Switch Ethernet Switch eDirectory DirXML Server...
  • Page 12 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 Cluster Services 1.0 Administration Guide...

  • Page 13: 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 14: Usage Scenarios

    Two active sites each supporting different applications/services. Either site can take over for the other site at any time. Novell Business Continuity Cluster Services 1.0 Administration Guide...
  • Page 15 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. Two Site Business Continuity Cluster Figure 1-3 Two independent clusters at geographically separate sites...
  • Page 16 Cluster Site 1 Cluster Sites 2, 3, and 4 Using Novell’s Portal Services, iChain®, and ZENworks® products, 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. Data and services continue to be available from the other mirrored sites.

  • Page 17: 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: “Requirements” on page 17 “Installing the DirXML 1.1a Engine” on page 18 “Installing the DirXML 1.1a Management Utilities” on page 19 “Copying User Objects Using DirXML”...

  • Page 18: Installing The Dirxml 1.1A Engine

    DirXML, see the DirXML 1.1a Administration Guide (http:// www.novell.com/documentation/dirxml11a/dirxml/data/a2iii88.html). To install the DirXML Starter Pack: 1 At the NetWare 6.5 server, insert the DirXML CD into the CD drive. Novell Business Continuity Cluster Services 1.0 Administration Guide...

  • Page 19: Installing The Dirxml 1.1A Management Utilities

    2 At the GUI server console, click Novell > Install and then click Add. If the GUI server console isn't running, launch it by entering STARTX at the console. 3 In the Path to Install From field, browse to and select nw\product.ni on the DirXML CD and then click OK twice.
  • Page 20 2 From the GUI server console, click Novell > Install > Add. If the GUI server console isn't running, launch it by entering STARTX at the console. 3 In the Path to Install From field, browse to and select DirXML_STRTR_PCK\nw\product.ni on the DirXML CD, then click OK.

  • Page 21: Installing The Dirxml Management Utilities On A Windows Server

    Identity Manager management utilities. See Installing Identity Manager on NetWare (http:// www.novell.com/documentation/dirxml20/admin/data/abaa2oj.html#abaa2oj) in the Novell Nsure Identity Manager 2.0.2 Administration Guide. Identity Manager must be installed on one node in each cluster. The node where Identity Manager is installed must have an eDirectory replica with at least read/write access to all eDirectory objects that will be synchronized between clusters.

  • Page 22: Copying User Objects Using Dirxml

    2.6 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 the cluster nodes that will be part of a business continuity cluster.

  • Page 23: Running The Business Continuity Cluster Installation Program

    2.6.2 Running the Business Continuity Cluster Installation Program To install Novell Business Continuity Clustering, download and copy the software to a directory on your Windows workstation, then complete the following steps: 1 From the directory on your Windows workstation where you just copied the Business Continuity software, run install.exe.

  • Page 24: Business Continuity Cluster Component Locations

    Disk Arrays Disk Arrays Cluster Site 1 Cluster Site 2 Figure 2-1 uses the following abbreviations: BCC eng. -- Business Continuity Cluster engine NCS -- Novell Cluster Services NW 6.5 -- NetWare 6.5 Novell Business Continuity Cluster Services 1.0 Administration Guide...

  • Page 25: Installing Perl

    2.7 Installing Perl Perl scripts are included with the Novell Business Continuity Clustering product and add functionality that lets you manage your business continuity cluster using cluster-specific commands either at the NetWare server console or in a DOS window on a Windows workstation.

  • 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 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 28: Lun Masking

    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 an assigned server by entering volumes at the server console.

  • Page 29: Setting Up Novell Business Continuity Cluster Software

    After you have installed and configured DirXML, the Business Continuity Cluster software, and Perl, 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: “Ensuring that Clusters and Trees are Resolvable”...
  • Page 30 Name of SSL Certificate: If you do not have an SSL certificate, leave this value set to the default. The certificate will be created later in the configuration process. See Step 1 on page 32 for instructions on creating SSL certificates. Novell Business Continuity Cluster Services 1.0 Administration Guide...
  • Page 31 2001 as the port number for the resource synchronization template in the other clusters. Full Distinguished Name (DN) of this cluster : For example, Cluster1.siteA.Novell. Full Distinguished Name (DN) of other cluster : Enter the fully Distinuished Name (DN) of the cluster in the other tree that is to be mirrored.
  • Page 32 Use the following format when specifying the driver name: DriverName.DriverSet.OrganizationalUnit.OrganizationName Ensure there are no spaces (beginning or end) in the specified context, and do not use the following format: cn=DriverName.ou=OrganizationalUnitName.o=OrganizationName Novell Business Continuity Cluster Services 1.0 Administration Guide...
  • Page 33 Synchronizing DirXML Drivers After creating BCC-specific DirXML drivers and SSL certificates, if you are adding a new cluster to an existing business continuity cluster, you must synchronize the BCC-specific DirXML drivers. If BCC-specific DirXML drivers are not synchronized, clusters can't be enabled for business continuity.

  • Page 34: Configuring Clusters For Business Continuity

    “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. Novell Business Continuity Cluster Services 1.0 Administration Guide...
  • Page 35 Enabling Clusters for Business Continuity If you want to enable the ability for a cluster to fail over selected resources or all cluster resources to another cluster, you must enable business continuity on that cluster. 1 Start Internet Explorer 5 or later and enter the URL for iManager. The URL is http://server_ip_address/nps/imanager.html.

  • Page 36: Configuring Cluster Resources For Business Continuity

    When specifying a username, include the Novell eDirectory context for it. If you selected multiple peer clusters, specify a common administrator username and password for the selected peer clusters. Each cluster can then use the same username and password to connect to multiple peer clusters.
  • Page 37 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.7 Administration Guide, then continue with Step 3 below.
  • Page 38 Any data or information added here is stored in eDirectory. If you add commands to call outside scripts, those scripts must exist on every server in the cluster. Novell Business Continuity Cluster Services 1.0 Administration Guide...

  • Page 39: Managing Novell Business Continuity Clustering

    2.10 Managing Novell Business Continuity Clustering 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 to another, changing existing cluster peer credentials, and generating a business continuity report that provides cluster configuration and status information.

  • Page 40: 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, include the Novell eDirectory context for the user name. Novell Business Continuity Cluster Services 1.0 Administration Guide...

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

    If you selected multiple peer clusters, specify a common administrator username and password for the selected peer clusters. Each cluster can then use the same username and password to connect to multiple peer clusters. If you specify a common username and password, each eDirectory tree in the business continuity cluster must have the same administrator username and password.

  • Page 42: 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 43: Business Continuity Cluster Failure Types

    BCC Console Commands Description CLUSTER DISABLE {resource} Disables Business Continuity Clustering for the specified resource. The resource you specify must be a member of a cluster that has already been enabled for Business Continuity Clustering. If no resource is specified, the entire cluster is disabled for Business Continuity Clustering.

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

    SAN vendor’s instructions to remirror. Then bring the secondary cluster back up. When you bring the secondary SAN and cluster back up, resources will still be in a secondary state. Novell Business Continuity Cluster Services 1.0 Administration Guide...

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

    Intersite SAN Connectivity Is Lost Recover your SANs first, then remirror from the good side to the bad side. 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.
  • Page 46 You must run the Cluster Scan For New Devices command on both clusters to ensure remirroring takes place. 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 Cluster Services 1.0 Administration Guide...

  • Page 47: Virtual Ip Addresses

    Virtual IP Addresses With the release of NetWare® 6.5, Novell® has enhanced the TCP/IP stack to support virtual IP addresses. This new feature is another high-availability offering that enables administrators to easily manage the name-to-IP address associations of business services. It complements the existing load balancing and fault tolerance features of the TCP/IP stack and enhances the availability of servers that reside on multiple subnets.

  • Page 48: Virtual Ip Address Benefits

    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 Cluster Services 1.0 Administration Guide...
  • Page 49 The following figure illustrates a multihomed server with all nodes running a dynamic routing protocol. Multihomed Server Running a Dynamic Routing Protocol Figure 3-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's sake, assume that all nodes are running some dynamic routing protocol.
  • Page 50 If one of the subnets that a server interfaces to fails completely or is taken out of service for maintenance, the routing protocols reroute the packets addressed to the virtual IP address through one of the other active subnets. Novell Business Continuity Cluster Services 1.0 Administration Guide...

  • Page 51: Unlimited Mobility

    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. 3.2.2 Unlimited Mobility Unlike physical IP addresses which are limited in their mobility, virtual IP addresses are highly mobile.

  • Page 52: 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 53: Configuring Virtual Ip Addresses

    Neither of these situations is desirable. Fortunately, the use of host masks remedies both. 3.5 Configuring Virtual IP Addresses The routers in a virtual IP address configuration must be running the RIP I or RIP II protocols. For a business continuity cluster, RIP II is the preferred protocol and should be used whenever possible. In NetWare, this can be accomplished by configuring the NetWare RIP Bind Options to use RIP I and RIPII, or RIPII only.

  • Page 54: Displaying Bound Virtual Ip Addresses

    To verify that a virtual IP address is bound, enter display secondary ipaddress at the server console of the cluster server where the virtual 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 Cluster Services 1.0 Administration Guide...

Table of Contents