User manual NOVELL BUSINESS CONTINUITY CLUSTERING 1.1 SP1 9-21-2010 ADMINISTRATION GUIDE FOR NOVELL OPEN ENTERPRISE SERVER 1 SP2 LINUX

[. . . ] AUTHORIZED DOCUMENTATION Administration Guide for Novell Open Enterprise Server 1 SP2 Linux Novell® Business Continuity Clustering 1. 1 SP1 September 21, 2010 www. novell. com 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. [. . . ] 3 In the left column, click Clusters, then click the BCC Manager link. 4 Specify a cluster name, or browse and select one. 5 Select one or more cluster resources, then click BCC Migrate. 6 Select the cluster where you want to migrate the selected resources, then click OK. The resources migrate to their preferred node on the destination cluster. If you select Any Configured Peer as the destination cluster, the Business Continuity Clustering software chooses a destination cluster for you. The destination cluster that is chosen is the first cluster that is up in the peer clusters list for this resource. Migrating a pool resource to another cluster causes the following to happen: 1. If the source cluster can be contacted, the state of the resource is changed to offline. The resource changes from primary to secondary on the source cluster. Any SAN script that is associated with the pool resource is run. On the destination cluster, the resource changes from secondary to primary so that it can be brought online. A custom Perl script can be created for disk mapping on Fibre Channel SANs. The purpose of this script is to make the LUNs in the SAN available to the destination cluster. A reverse script is also created for testing purposes so pool resources can be migrated back to the source cluster. The cluster scan for new devices command is executed on the destination cluster so that the cluster is aware of LUNs that are now available. Resources are brought online and load on the their most preferred node in the cluster. Resources appear as running and primary on the cluster where you have migrated them. WARNING: Do not migrate resources for a test failover if the peer (LAN) connection between the source and destination cluster is down. Possible disk problems and data corruption could occur. This warning does not apply if resources are migrated during an actual cluster site failure. Installation and Setup 49 2. 5. 2 Changing Cluster Peer Credentials Changing cluster peer credentials consists of changing the username and password for the administrative user that the selected cluster will use to connect to a selected peer cluster. You might need to do this if the administrator username or password changes for any clusters in the business continuity cluster. [. . . ] Table C-4 provides an example of possible combinations of scheme and port specifier for the <address> tag for values of the NCS:BCC Peers attribute: Table C-4 Example of Scheme and Port Specifier Values for the NCS:BCC Peers Attribute Value Protocol Used Port Used 10. 1. 1. 10 10. 1. 1. 10:1234 http://10. 1. 1. 10 http://10. 1. 1. 10:1234 https://10. 1. 1. 10 https://10. 1. 1. 10:1234 HTTPS HTTPS HTTP HTTP HTTPS HTTPS 5989 1234 5988 1234 5989 1234 C. 2. 2 Security Information for Other Products Table C-5 provides links to security-related information for other products that impact the security of BCC: Security Considerations 93 Table C-5 Security Information for Other Products Product Name Links to Security Information NSS "Securing Access to NSS Volumes, Directories, and Files" (http://www. novell. com/documentation/oes/nss_enu/data/ bv8n39l. html#bv8n39l). 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 Identity Manager 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. [. . . ]