User manual NOVELL BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 ADMINISTRATION

[. . . ] Novell Business Continuity Clustering 1. 1 for NetWare Administration Guide novdocx (en) 11 December 2007 Novell Business Continuity Clustering for NetWare® 1. 1 ADMINISTRATION GUIDE February 15, 2008 www. novell. com novdocx (en) 11 December 2007 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. [. . . ] This is a recovery procedure that should be run when a cluster in a BCC is brought back into service. You should run this command when only one node is a member of the cluster. Bring up the remaining nodes in the cluster. CLUSTER VIEW Displays the node name, cluster epoch number, master node name, a list of nodes that are currently members of the cluster, and peer clusters if this cluster is a member of a Business Continuity Cluster. Lets you view the state and location of cluster resources and whether resources are primary or secondary. Lets you view the state and location of cluster resources and whether resources are primary or secondary. If the resource state is primary, the node where the resource is running is displayed. If the resource state is secondary, the cluster where the resource is located is displayed. Specifying -a will attempt to show the connection status of all clusters in the BCC. This command should not be used except under the direction of Novell Technical Services. CLUSTER RESOURCES {resource} CLUSTER STATUS CLUSTER CONNECTIONS {-a} CLUSTER REFRESH 2. 7 Business Continuity Cluster Failure Types There are several failure types associated with a business continuity cluster that you should be aware of. Understanding the failure types and knowing how to respond to each can help you more quickly recover a cluster. Some of the failure types and responses differ depending on whether you have implemented SAN-based mirroring or host-based mirroring. Promoting or demoting LUNs is sometimes necessary when responding to certain types of failures. NOTE: The terms promote and demote are used here in describing the process of changing LUNs to a state of primary or secondary, but your SAN vendor documentation might use different terms such as mask and unmask. Installation and Setup 49 novdocx (en) 11 December 2007 2. 7. 1 SAN-based Mirroring Failure Types and Responses SAN-based mirroring failure types and responses are described in the following sections: "Primary Cluster Fails but Primary SAN Does Not" on page 50 "Primary Cluster and Primary SAN Both Fail" on page 50 "Secondary Cluster Fails but Secondary SAN Does Not" on page 50 "Secondary Cluster and Secondary SAN Both Fail" on page 50 "Primary SAN Fails but Primary Cluster Does Not" on page 51 "Secondary SAN Fails but Secondary Cluster Does Not" on page 51 "Intersite SAN Connectivity Is Lost" on page 51 "Intersite LAN Connectivity Is Lost" on page 51 Primary Cluster Fails but Primary SAN Does Not This type of failure can be temporary (transient) or long-term. There should be an initial response and then a long-term response based on whether the failure is transient or long-term. If the former primary SAN has not been demoted to secondary, you might need to demote it manually. The former primary SAN must be demoted to secondary before bringing cluster servers back up. Consult your SAN hardware documentation for instructions on demoting and promoting SANs. You can use the cluster resetresources console command to change resource states to offline and secondary. Prior to bringing up the cluster servers, the administrator must ensure that the SAN is in a state in which the cluster resources cannot come online and cause a divergence in data. Divergence in data occurs when connectivity between SANs has been lost and both clusters assert that they have ownership of their respective disks. Primary Cluster and Primary SAN Both 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. Then bring up the former primary cluster servers and fail back the cluster resources. [. . . ] and Security Considerations (http://www. novell. com/ documentation/oes/nss_enu/data/bx8gp06. html). eDirectory 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) Security: Best Practices (http://www. novell. com/ documentation/idm/admin/data/b1bsw73. html) in the IDM Administration Guide. Configuring Access Control to iSCSI Targets (http:// www. novell. com/documentation/iscsi1_nak/iscsi/data/ h2mdblj1. html) and Enabling and Configuring iSCSI Initiator Security (http://www. novell. com/documentation/iscsi1_nak/ iscsi/data/hclny85e. html) in the iSCSI 1. 1. 3 Administration Guide for NetWare 6. 5. OpenWBEM should be configured on each node to allow only the necessary users. [. . . ]