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. [. . . ] For this reason, you should use caution when disabling BCC for an entire cluster. CLUSTER DISABLE {resource} CLUSTER ENABLE {resource} Enables 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 enabled for Business Continuity Clustering. When BCC-enabling a resource, previous versions of the CLI would not set the peer clusters where the resource was assigned to run. The only way to set peer clusters for a resource was through iManager. The new version of the cluster CLI automatically sets all the clusters in the BCC on a resource. Assigning a resource to specific clusters still must be done through iManager. CLUSTER MIGRATE {source/resource} {destination/node name} Migrates the specified resource from the specified source cluster to the specified target (destination) cluster. Specifying * for the resource name will migrate all BCC-enabled resources. Specifying * for the node name will bring the resource online at the most preferred node. 48 Novell Business Continuity Clustering 1. 1 for NetWare Administration Guide novdocx (en) 11 December 2007 BCC Console Commands Description CLUSTER RESETRESOURCES Changes the state of all resources on this cluster to offline and secondary. 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. After a failure, bring up one node in the cluster. All other nodes should remain powered off. 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. You can optionally specify a specific resource name. 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. Displays the connection status of the cluster. 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. [. . . ] 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. For more information, see Changing the Authentication Method (http://www. novell. com/ documentation/oes/cimom/data/bv4xqz9. html) in the OpenWBEM Services Administration Guide for OES. Identity Manager (IDM) iSCSI OpenWBEM Security Considerations 95 novdocx (en) 11 December 2007 Product Name Links to Security Information Linux User Management (LUM) Linux User Management Technology Guide (http:// www. novell. com/documentation/oes/lumadgd/data/ bookinfo. html#bookinfo). C. 3 Other Security Considerations Servers should be kept in a physically secure location with access by authorized personnel only. The corporate network should be physically secured against eavesdropping or packet sniffing. [. . . ]