User manual NOVELL BUSINESS CONTINUITY CLUSTERING 1.2 ADMINISTRATION

[. . . ] novdocx (en) 7 January 2010 AUTHORIZED DOCUMENTATION Administration Guide for Novell Open Enterprise Server 2 Support Pack 1 for Linux* Novell® 1. 2 February 18, 2010 Business Continuity Clustering www. novell. com BCC 1. 2: Administration Guide for OES 2 SP1 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. [. . . ] If the source cluster can be contacted, the state of the resource is changed to offline. Any storage management unload script that is associated with the pool resource is run. The cluster scan for new devices command is executed on the peer cluster so that the cluster is aware of LUNs that are no longer available. On the destination peer cluster, the resource changes from secondary to primary so that it can be brought online. Any storage management load script that is associated with the pool resource is run. If a error is returned from the BCC load script, the resource is not brought online and remains in the offline, not comatose, state. The cluster scan for new devices command is executed on the destination peer cluster so that the cluster is aware of LUNs that are now available. Resources are brought online and load on the most preferred node in the cluster (that is, on the first node in the preferred node list). TIP: You can use the cluster migrate command to start resources on nodes other than the preferred node on the destination cluster. Resources appear as running and primary on the cluster where you have migrated them. 10. 1. 2 Migrating Cluster Resources between Clusters WARNING: Do not migrate resources for a test failover if the storage connection between the source and destination cluster is down. Possible disk problems and data corruption can occur if the down connection comes up and causes a divergence in data. This warning does not apply if resources are migrated during an actual cluster site failure. To manually migrate cluster resources from one cluster to another: 1 Start your Internet browser and enter the URL for iManager. 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. 3 In Roles and Tasks, click Clusters, then click the BCC Manager link. 4 Specify a cluster name, or browse and select the Cluster object of the cluster you want to manage the BCC from. Current Cluster is associated with the first table on the BCC Migrate page. It tells you what cluster you selected to manage the BCC from so that you understand the point of view that the status information is provided in the first table. For example, if the resource is assigned to a node in the cluster you are managing from, the cluster resource status is the same as if you were 92 BCC 1. 2: Administration Guide for OES 2 SP1 Linux novdocx (en) 7 January 2010 looking at the cluster itself, such as Running or Offline. If the cluster resource is not assigned to the cluster you are managing from (that is, not in the current cluster), then the status is shown as Secondary. 6 In the list of cluster, select the cluster where you want to migrate the selected resources, then click OK. [. . . ] At a terminal console prompt, enter yast2 novell-bcc 3 Deselect the Install Core Business Continuity Clustering Software and Configure Core Software option, select Remove Installed Software, then click Next. Removing Business Continuity Clustering Core Software 171 novdocx (en) 7 January 2010 172 BCC 1. 2: Administration Guide for OES 2 SP1 Linux novdocx (en) 7 January 2010 H Documentation Updates This section contains information about documentation content changes made to the Novell® Business Continuity Clustering 1. 2 Administration Guide for Linux since the initial 1. 2 release. If you are an existing user, review the change entries to readily identify modified content. This document was updated on the following dates: Section H. 1, "February 18, 2010, " on page 173 Section H. 2, "February 7, 2010 (BCC 1. 2. 0 Patch for OES 2 SP1 Linux), " on page 173 Section H. 3, "January 7, 2010, " on page 174 Section H. 4, "September 9, 2009, " on page 176 Section H. 5, "August 14, 2009, " on page 176 Section H. 6, "May 11, 2009, " on page 177 Section H. 7, "April 28, 2009, " on page 178 H H. 1 February 18, 2010 Updates were made to the following section. Section H. 1. 1, "Updating (Patching) BCC 1. 2. 0 on OES 2 SP1 Linux, " on page 173 H. 1. 1 Updating (Patching) BCC 1. 2. 0 on OES 2 SP1 Linux Location Change Step 5 on page 58 Step 5 on page 59 Restart Tomcat by entering the following command at a terminal console prompt: rcnovell-tomcat5 restart H. 2 February 7, 2010 (BCC 1. 2. 0 Patch for OES 2 SP1 Linux) Updates were made to the following sections. [. . . ]