User manual NOVELL BUSINESS CONTINUITY CLUSTERING 1.2.1 ADMINISTRATION

[. . . ] novdocx (en) 7 January 2010 AUTHORIZED DOCUMENTATION Administration Guide for Novell Open Enterprise Server 2 Support Pack 2 for Linux* Novell® 1. 2. 1 February 18, 2010 Business Continuity Clustering www. novell. com BCC 1. 2. 1: Administration Guide for OES 2 SP2 Linux novdocx (en) 7 January 2010 Legal Notices Novell, Inc. , makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. , makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. 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. [. . . ] Synchronous: Ensure that this option is selected (checked) See Step 7b in "Adding Storage Management Configuration Information" on page 89 for more information and descriptions of the information in the value fields. 9 Under Script Parameters, click New, then specify the following: Name: Specify the variable name as CONTAINER_NAME. This value is case-sensitive and should be entered as CONTAINER_NAME Value: Specify the name of the EVMS CSM (Cluster Segment Manager) container. This value is casesensitive and should exactly match the container name. 10 Using a text editor, copy and paste the bcc_csm_util. pl script into the Script Parameters text box. The script is located in the /nsmi_scripts/linux/ directory on the Business Continuity Clustering CD or ISO image. The information you provide in the steps should be unique for each cluster. 10. 7 Verifying BCC Administrator User Trustee Rights and Credentials You must ensure that the BCC Administrator user is a LUM-enabled user. For instructions, see "Creating the BCC Group and Administrative User" on page 48. You must ensure that the user who manages your BCC (that is, the BCC Administrator user) is a trustee of the Cluster objects and has at least Read and Write rights to the All Attributes Rights property. For instructions, see "Assigning Trustee Rights for the BCC Administrator User to the Cluster Objects" on page 49. Configuring BCC for Peer Clusters 93 novdocx (en) 7 January 2010 In order for the BCC Administrator user to gain access to the cluster administration files (/admin/ novell/cluster) on other Linux cluster nodes in your BCC, you must add that user to the ncsgroup on each cluster node. For instructions, see "Adding the BCC Administrator User to the ncsgroup on Each Cluster Node" on page 49. 10. 8 Disabling BCC for a Peer Cluster Before you disable BCC for a given peer cluster, you must first disable BCC for each of the cluster resources running on that cluster. Make sure to remove the secondary peer clusters from the cluster resource's Assigned list before you disable BCC for the resource on the primary peer cluster. For information, see Section 12. 6, "Disabling BCC for a Cluster Resource, " on page 108. After you have disabled BCC for all resources running on that cluster, remove the secondary peer clusters from the Assigned list of preferred nodes for that cluster, then disable BCC for the cluster. 10. 9 What's Next Enable the cluster resources in each peer cluster that you want to be able to fail over between them. For information, see Chapter 10, "Configuring BCC for Peer Clusters, " on page 85. 94 BCC 1. 2. 1: Administration Guide for OES 2 SP2 Linux novdocx (en) 7 January 2010 Managing a Business Continuity Cluster 1 11 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 ServicesTM cluster to another, to modify peer credentials for existing clusters, and to generate reports of the cluster configuration and status. IMPORTANT: Identity Manager must be configured and running on one node in each peer cluster before any BCC enabled cluster resource changes are made. Make sure that the Identity Manager server is part of the cluster and that it is working properly whenever you make BCC configuration changes to the BCC-enabled cluster resources. For information, see Chapter 9, "Configuring the Identity Manager Drivers for BCC, " on page 71. For information about using console commands to manage your business continuity cluster, see Appendix A, "Console Commands for BCC, " on page 133. Section 11. 1, "Migrating a Cluster Resource to a Peer Cluster, " on page 95 Section 11. 2, "Bringing a Downed Cluster Back in Service, " on page 97 Section 11. 3, "Changing Peer Cluster Credentials, " on page 97 Section 11. 4, "Viewing the Current Status of a Business Continuity Cluster, " on page 98 Section 11. 5, "Generating a Cluster Report, " on page 99 Section 11. 6, "Resolving Business Continuity Cluster Failures, " on page 99 11. 1 Migrating a Cluster Resource to a Peer Cluster Although Novell Business Continuity Clustering provides an automatic failover feature that fails over resources between peer clusters, we recommend that you manually migrate cluster resources between the peer clusters instead. For information about configuring and using automatic failover for a business continuity cluster, see Appendix B, "Setting Up Auto-Failover, " on page 137. [. . . ] This document was updated on the following dates: Section H. 1, "February 18, 2010, " on page 177 Section H. 2, "February 7, 2010 (BCC 1. 2. 1 Patch for OES 2 SP2 Linux), " on page 178 Section H. 3, "February 5, 2010 (BCC 1. 2. 0 Patch for OES 2 SP1 Linux), " on page 178 Section H. 4, "January 7, 2010, " on page 179 Section H. 5, "September 9, 2009, " on page 181 Section H. 6, "August 14, 2009, " on page 182 Section H. 7, "May 11, 2009, " on page 182 Section H. 8, "April 28, 2009, " on page 183 H H. 1 February 18, 2010 Updates were made to the following sections. Section H. 1. 1, "Updating (Patching) BCC 1. 2. 0 on OES 2 SP1 Linux, " on page 177 Section H. 1. 2, "Updating (Patching) BCC 1. 2. 1 on OES 2 SP2 Linux, " on page 177 H. 1. 1 Updating (Patching) BCC 1. 2. 0 on OES 2 SP1 Linux Location Change Step 5 on page 62 Step 5 on page 63 Restart Tomcat by entering the following command at a terminal console prompt: rcnovell-tomcat5 restart H. 1. 2 Updating (Patching) BCC 1. 2. 1 on OES 2 SP2 Linux Location Change Step 6 on page 59 Step 5 on page 60 Restart Tomcat by entering the following command at a terminal console prompt: rcnovell-tomcat5 restart Documentation Updates 177 novdocx (en) 7 January 2010 H. 2 February 7, 2010 (BCC 1. 2. 1 Patch for OES 2 SP2 Linux) This guide was updated for the BCC 1. 2. 1 release for Novell Open Enterprise Server (OES) 2 SP2 Linux. Section H. 2. 1, "Installing Business Continuity Clustering, " on page 178 Section H. 2. 2, "Updating (Patching) BCC 1. 2. 1 on OES 2 SP2 Linux, " on page 178 Section H. 2. 3, "What's New for BCC 1. 2, " on page 178 H. 2. 1 Installing Business Continuity Clustering Location Change Section 4. 1, "Requirements This section was updated to reflect the requirements for BCC 1. 2. 1 on for BCC 1. 2. 1 for OES 2 SP2 OES 2 SP2 Linux. Linux, " on page 37 H. 2. 2 Updating (Patching) BCC 1. 2. 1 on OES 2 SP2 Linux This section is new. H. 2. 3 What's New for BCC 1. 2 Location Change Section 2. 1, "BCC 1. 2. 1 ISO This section is new. [. . . ]