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. [. . . ] NOTE: The script is necessary only for Linux POSIX file systems, and not for NSS pools. 1 Start your Internet browser and enter the URL for iManager. The URL is http://server_ip_address/nps/iManager. html. Replace server_ip_address with the IP address or DNS name of the server that has iManager and the Identity Manager preconfigured templates for iManager installed. 92 BCC 1. 2. 1: Administration Guide for OES 2 SP2 Linux novdocx (en) 7 January 2010 2 Specify your username and password, specify the tree where you want to log in, then click Login. 3 In Roles and Tasks, click Clusters, then click the Cluster Options link. 4 Specify a cluster name, or browse and select one. 5 Under Cluster Objects, select the business-continuity-enabled cluster resource that contains the Reiser or Ext3 file system, then click Details. Cluster resources that are enabled for business continuity have the BCC label on the resource type icon. 6 Click the Business Continuity tab, then click Storage Management. 7 Under BCC Load Scripts, click New to bring up a wizard that lets you create a new script. 8 In the wizard, specify the following information: Name: Convert CSM container. Description: Converts the EVMS Cluster Segment Manager (CSM) container so the specified container is available on the secondary cluster. CIM Enabled: Ensure that this option is deselected (not checked). Synchronous: Ensure that this option is selected (checked) See Step 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. You assigned this name to the EVMS CSM container when you created it. 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. 12 Repeat Step 1 through Step 11 for the peer clusters in your BCC. The information you provide in the steps should be unique for each cluster. 10. 7 Verifying BCC Administrator User Trustee Rights and Credentials You must ensure that the BCC Administrator user is a LUM-enabled user. [. . . ] 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. Additions were made to the following sections. 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. [. . . ]