User manual NOVELL BUSINESS CONTINUITY CLUSTERING 1.0 ADMINISTRATION

[. . . ] Novell Business Continuity Cluster Services 1. 0 Administration Guide novdocx (ENU) 10 August 2006 Novell Business Continuity Clustering 1. 0 ADMINISTRATION GUIDE May 22, 2006 www. novell. com novdocx (ENU) 10 August 2006 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. 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. 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. [. . . ] 10c Click the User Sync driver icon, then click Migrate from eDirectory. 10d Click Add, browse to and select the context that contains the User objects, then click OK. 11 (Optional) If you choose to include user object synchronization, exclude the Admin User object from being synchronized. 12 If the other clusters in your business continuity cluster are in different eDirectory trees, perform Step 1 through Step 11 for each cluster that is in a separate tree. Creating SSL Certificates You must create an an SSL certificate for the cluster resource synchronization driver, and if you have configured user object synchronization, an SSL certificate for the user object synchronization driver. For example, creating an SSL certificate for the cluster resource synchronization driver creates the certificate for the cluster resource synchronization drivers on both clusters. To create an SSL certificate: 1 Start Internet Explorer 5 or later and enter the URL for iManager. Replace server_ip_address with the IP address or DNS name of the NetWare 6. 5 server that has iManager and the DirXML preconfigured templates for iManager installed. 3 In the left column, click DirXML Management, then click NDS2NDS Driver Certificates. You must specify the driver name (including the context) you supplied in Step 8 on page 30 for the current tree. Use the following format when specifying the driver name: DriverName. DriverSet. OrganizationalUnit. OrganizationName Ensure there are no spaces (beginning or end) in the specified context, and do not use the following format: cn=DriverName. ou=OrganizationalUnitName. o=OrganizationName 32 Novell Business Continuity Cluster Services 1. 0 Administration Guide novdocx (ENU) 10 August 2006 Synchronizing DirXML Drivers After creating BCC-specific DirXML drivers and SSL certificates, if you are adding a new cluster to an existing business continuity cluster, you must synchronize the BCC-specific DirXML drivers. If BCC-specific DirXML drivers are not synchronized, clusters can't be enabled for business continuity. This is not necessary unless you are adding a new cluster to an existing business continuity cluster. To synchronize BCC-specific DirXML drivers: 1 Start Internet Explorer 5 or later and enter the URL for iManager. Replace server_ip_address with the IP address or DNS name of the NetWare 6. 5 server that has iManager and the DirXML preconfigured templates for iManager installed. 3 In the left column, click DirXML Management, then click the Overview link. 6 If you chose to include User object synchronization, repeat the above steps, and in Step 5 click the User Sync icon. Preventing DirXML Synchronization Loops If you have three or more clusters each in separate eDirectory trees in your business continuity cluster, you should set up DirXML user object and cluster resource object synchronization in a manner that prevents DirXML synchronization loops. DirXML synchronization loops can cause excessive network traffic and slow server communication and performance. For example, in a three cluster business continuity cluster, a DirXML synchronization loop occurrs when cluster one is configured to synchronize with cluster two, cluster two is configured to synchronize with cluster three, and cluster three is configured to synchronize back to cluster one. This is illustrated in Figure 2-3 below. Figure 2-3 Three Cluster DirXML Synchronization Loop Cluster One Di nc rX Sy M L L M Sy rX nc Di DirXML Sync Cluster Three Cluster Two Installation and Setup 33 novdocx (ENU) 10 August 2006 A preferred method is to make cluster one a DirXML synchronization master in which cluster one synchronizes with cluster two and cluster two and cluster three both synchronize with cluster one. This is illustrated in Figure 2-4 below. Figure 2-4 Three Cluster DirXML Synchronization Master Cluster One M rX Di L Sy nc L Di rX M nc Sy Cluster Three Cluster Two You could also have cluster one synchronize with cluster two, cluster two synchronize with cluster three, and cluster three synchronize back to cluster two as is illustrated in Figure 2-5 below. Figure 2-5 Alternate Three Cluster DirXML Synchronization Scenario Cluster One Di rX M L Sy nc DirXML Sync Cluster Three Cluster Two 2. 9. 3 Configuring Clusters for Business Continuity This procedure consists of "Enabling Clusters for Business Continuity" on page 35 "Adding Cluster Peer Credentials" on page 35 "Adding Resource Script Search and Replace Values" on page 36 These tasks must be performed on each separate cluster that you want to be part of the business continuity cluster. 34 Novell Business Continuity Cluster Services 1. 0 Administration Guide novdocx (ENU) 10 August 2006 Enabling Clusters for Business Continuity If you want to enable the ability for a cluster to fail over selected resources or all cluster resources to another cluster, you must enable business continuity on that cluster. [. . . ] Because Novell Cluster ServicesTM can migrate a service and its virtual IP address from one node to another, the virtual IP network must migrate to the same node as the service. If multiple virtual IP addresses belong to a given virtual IP network, one of two events must occur: All services associated with the virtual IP addresses on a given virtual IP network must fail over together. The virtual IP addresses on a given virtual IP network must go unused, thereby wasting a portion of the available address space. 52 Novell Business Continuity Cluster Services 1. 0 Administration Guide novdocx (ENU) 10 August 2006 Neither of these situations is desirable. Fortunately, the use of host masks remedies both. 3. 5 Configuring Virtual IP Addresses The routers in a virtual IP address configuration must be running the RIP I or RIP II protocols. [. . . ]