Multi-Node EMC Documentum xplore 1.0 and 1.1 High-Availability Deployment Using Windows Server 2008 Failover Clustering

Size: px

Start display at page:

Download "Multi-Node EMC Documentum xplore 1.0 and 1.1 High-Availability Deployment Using Windows Server 2008 Failover Clustering"

Rudolf Rogers
5 years ago
Views:

1 Multi-Node EMC Documentum xplore 1.0 and 1.1 High-Availability Deployment Using Best Practices Planning Abstract The objective of this white paper is to describe the architecture and procedure for deploying multi-instance EMC Documentum Search Services in a high-availability environment using Windows Server 2008 Failover Clustering. Detailed step-by-step instructions are presented using a VMware environment. The same instructions apply to deployments where physical hosts are used. June 2011

2 Copyright 2011 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com VMware and ESX are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners. Part Number h Best Practices Planning 2

3 Table of Contents Executive summary... 4 Introduction... 4 Audience... 4 Architecture description... 4 Virtual machine creation and customization... 5 Adding a hard disk to HostA and HostB... 6 Preparing for adding disks... 6 Adding a shared storage disk... 6 Initializing the disk on HostA... 6 Creating a new cluster... 7 Creating a cluster service... 7 Configuring HostA... 7 Configuring HostB... 9 Creating a service/application in the cluster... 9 Installing Content Server on HostC... 9 Installing multi-instance xplore on HostA and HostB... 9 Installing primary and secondary Dsearch instances on HostA... 9 Installing primary and secondary Dsearch instances on HostB Updating the indexserverconfig.xml file Installing an index agent on HostC Updating the index agent configuration file Adding Dsearch services as a cluster resource Configuring the primary and secondary Dsearch services Adding the primary Dsearch service as a cluster resource Adding the secondary Dsearch service as a cluster resource Validation Operational consideration Conclusion Best Practices Planning 3

4 Executive summary An EMC Documentum repository can contain millions of objects. Finding the information you need is a major challenge. Full-text indexing is one solution to the problem of rapidly locating objects in a repository. Full-text indexing is a process that indexes all content files and properties in a repository. The created index can be searched rapidly to retrieve objects whose properties or associated content files contain the values for which you are searching. Businesses of all sizes and types continue to increase their dependency upon rapid access to stored data/information in their day-to-day activities. Most businesses will suffer significant losses if they cannot locate and access the required data/information, even for a short period of time. The high-availability deployment of Documentum xplore addresses the issue by improving the degree of operational continuity. Introduction Enterprise content management has become a key component for global companies to conduct business efficiently. A powerful search is one of the critical requirements; metadata searches as well as full-text searches of the content itself fulfill these requirements. This white paper describes the Documentum xplore high-availability deployment and gives a detailed setup example using Windows Server 2008 Failover Clustering. This white paper applies to both xplore 1.0 and 1.1. All instructions apply to both releases unless specifically stated. Audience This white paper is written for developers and IT staff who are considering how to deploy Documentum xplore in a high-availability environment. Architecture description Currently, xplore supports high-availability deployment using. In this configuration, only one xplore node (with possibly multiple xplore instances) is active (that is, indexing and executing search queries) at any point in time. In this specific deployment, there are two nodes on a failover cluster and two separate xplore instances are deployed on each node. On the Content Server machine, two index agents are deployed against two repositories. The following figure illustrates the different components involved in the deployment. Best Practices Planning 4

5 Domain HostA Cluster Environment xplore Primary Instance Content Server xplore Secondary Instance Repository-1 IndexAgent1 Repository-2 IndexAgent2 HostB xplore Primary Instance Share Data xplore Secondary Instance Figure 1. Deployment diagram The two hosts (HostA and HostB) in the cluster must be in the same domain and all the dynamic data is stored in shared storage so that the active xplore instance can access and change the shared data. In this paper, HostA is used as the active one in the cluster, while HostB is the passive one. When deploying the xplore instances on both hosts, it is recommended to follow the order: HostA (active) first, HostB (passive) second. Even if you want to separate the xplore instances onto multiple cluster environments, it is strongly recommended to follow the order above: first set up xplore multi-instances on all active machines in multiple cluster environments, then repeat the setup on all passive machines in a multi-cluster environment. In this deployment, a single VMware ESX server is used and all resources, such as boxes, hard disks, and network cards, are created on the ESX server machine. Virtual machine creation and customization The following table describes the selections for the three virtual machines. Table 1. Virtual machine selections Page Wizard Type Name and Location Resource Pool Datastore Guest Operating System Selection Typical. Choose a name and location you want to use. This example uses HostA, HostB, and HostC. Content Server will be installed on HostC. Select the resource pool for the virtual machine or, if there are no resource pools, the host. Choose Local datastore. Choose Windows Server 2008 Enterprise Edition. Best Practices Planning 5

6 CPU Memory Network Virtual Disk Capacity Ready to Complete Use the default setting if there is no special requirement. Use the default setting if there is no special requirement. Use the default setting if there is no special requirement. If you need a primary SCSI disk larger than 4 GB, enter the appropriate value in the Capacity field. Click OK to create the virtual machine. Adding a hard disk to HostA and HostB A hard disk should be added on both HostA and HostB as a shared resource for data storage. Note: For HostA, point the disk to a different location. For HostB, choose the same location as you did for HostA. Preparing for adding disks Zero out the disk by using the following commands: To create and zero out in one sweep, type: vmkfstools -c <size> -d eagerzeroedthick /vmfs/volumes/<mydir>/<mydisk>.vmdk To zero out an existing disk, type: vmkfstools [-w --writezeroes] /vmfs/volumes/<mydir>/<mydisk>.vmdk Connect to the ESX server by using SSH tools or telnet, and then run the commands. Adding a shared storage disk Perform the following steps: 1. Select the virtual machine you just created, and choose Edit Settings. 2. Click Add, select Hard Disk, and click Next. 3. Select Choose an existing virtual disk and select the disk you prepared. 4. Choose a new virtual device node with a new SCSI controller, for example choose SCSI (1:0). 5. Click Finish. 6. Select the new SCSI controller and click Change Controller Type. Make sure the controller is set to LsiLogic (the default). 7. In the same panel, set SCSI Bus Sharing to Virtual, and click OK. 8. Repeat steps 1 through 6 to add another virtual disk and choose SCSI (1:1) on the controller that was just created. Initializing the disk on HostA 1. Open Control Panel, and under Storage, click Disk Management. Best Practices Planning 6

2. If the Initialize and Convert Disk Wizard appears, click Next. If the wizard does not appear, skip to 6. 3. On the Select Disks to Initialize page, click Next. 4.

Note: In this deployment, the F: drive is used. 6. On the Format dialog box, type a name for your external hard drive, such as Quorum. Format the partition using NTFS.

7 2. If the Initialize and Convert Disk Wizard appears, click Next. If the wizard does not appear, skip to On the Select Disks to Initialize page, click Next. 4. On the Completing the Initialize and Convert Disk Wizard page, click Finish. 5. Right-click your external drive (which will probably be drive E or F), and then click Format. Note: In this deployment, the F: drive is used. 6. On the Format dialog box, type a name for your external hard drive, such as Quorum. Format the partition using NTFS. Verify that disks are formatted as NTFS and designated as MBR Basic. 7. Click OK again. Creating a new cluster In this section, you will learn how to configure a new Windows Server 2008 failover cluster. Creating a cluster service Configuring HostA 1. Click Start > All Programs > Administrative Tools, and then click Failover Cluster Management. 2. In the Action drop-down list, click Create a Cluster, as shown below, and then click OK. 3. Enter the names of the servers that will be in the cluster, and click Next. Best Practices Planning 7

8 4. Enter a name and IP address for the cluster, and click Next. 5. Review the Summary page to verify that all the information is correct, and then click Next. 6. Review any warnings or errors encountered during cluster creation, and then click Next. 7. Click Finish to complete the installation. Best Practices Planning 8

Configuring HostB If HostB is added to the cluster at the same time as HostA, no additional configuration is needed for HostB. The figure below shows the current state of the cluster.

Rename it as, for example, xplore service. 3. Use the following command to make the shared disk a resource and join the Available Storage group.

9 Configuring HostB If HostB is added to the cluster at the same time as HostA, no additional configuration is needed for HostB. The figure below shows the current state of the cluster. Creating a service/application in the cluster 1. Open Failover Cluster Management. 2. Right-click Service and Applications, then navigate to More Actions > Create Empty Service or Application. Rename it as, for example, xplore service. 3. Use the following command to make the shared disk a resource and join the Available Storage group. cluster res "Disk F:" /create /type:"physical Disk" /group:"available Storage" cluster res "Disk F:" /priv DiskPath="F:" 4. Right-click xplore service, add storage, and select the disk created in Step Right-click xplore service, add an IP address, and enter an IP address to be shared with both HostA and HostB. The IP address must belong to the domain network. Let s call the IP Shared_IP_Address. Installing Content Server on HostC Refer to the EMC Documentum Content Server Installation Guide to install Content Server on HostC. Installing multi-instance xplore on HostA and HostB Please refer to EMC Documentum xplore Deployment Guide to install the primary and secondary instances. Installing primary and secondary Dsearch instances on HostA In the Dsearch Data and Config Directory Information window, you must set Data Directory and Configuration Directory to the shared disk spaces. For example, here we set the xplore data and configuration directory on f:\xplore because hard disk F: is our shared disk. Best Practices Planning 9

Installing primary and secondary Dsearch instances on HostB These procedures are the same as the ones for HostA. You must stop the xplore instances on HostA in advance.

10 Installing primary and secondary Dsearch instances on HostB These procedures are the same as the ones for HostA. You must stop the xplore instances on HostA in advance. The same base locations should be used for xplore data and configuration directories. Updating the indexserverconfig.xml file All xplore instances must be shut down before modifying indexserverconfig.xml files. Replace the local IP address with Share_IP_Address. So update indexserverconfig.xml as follows: <node xdb-listener-port="9330" primarynode="true" status="normal" url=" Shared_IP_Address:9300/dsearch/" admin-rmi-port="9331" hostname=" Shared_IP_Address" name="primarydsearch"> If xplore 1.1 is used, on both HostA and HostB, open $xplore_installation\jboss4.3.0\server\dctmserver_dsearchnode2\deploy\dsearch.war\web- INF\classes\indexserver-bootstrap.properties and update as follows. xhive-connection-string=xhive\:// Shared_IP_Address \:9330 Start multi-instance xplore on either HostA or HostB. Then xplore will generate an XhiveDatabase.bootstrap file under F:\xPlore\config. After seeing that, stop all xplore instances again. UpdateXhiveDatabase.bootstrap as shown below: Best Practices Planning 10

<node name="primary" host=" Shared_IP_Address" port="9330"> </node> <node name="dsearchnode2" host=" Shared_IP_Address" port="9430"> </node> Note: In the indexserverconfig.xml and XhiveDatabase.

11 <node name="primary" host=" Shared_IP_Address" port="9330"> </node> <node name="dsearchnode2" host=" Shared_IP_Address" port="9430"> </node> Note: In the indexserverconfig.xml and XhiveDatabase.bootstrap files, make sure all nodes are updated to use Shared_IP_Address. You can start the xplore instances now. Installing an index agent on HostC Please refer to the EMC Documentum xplore Deployment Guide to install an index agent on HostC. Note: You must set the Cluster IP address in the following step. Updating the index agent configuration file Append the following path to the exporter element of the file indexagent.xml. <local_content_area> //IPAddress/c$/ess/jboss4.2.0/server/DctmServer_Indexagent/data/Indexagent </local_content_area> Best Practices Planning 11

The IP address should be the address of host on which the index agent data is located. Make sure that both HostA and HostB are able to access the same UNC location.

12 The IP address should be the address of host on which the index agent data is located. Make sure that both HostA and HostB are able to access the same UNC location. Adding Dsearch services as a cluster resource Configuring the primary and secondary Dsearch services 1. Stop the Dsearch service in Service Manager if it is not already stopped. 2. Right-click the service name and select Properties. Best Practices Planning 12

3. Select the Startup type as Manual on the General tab. Adding the primary Dsearch service as a cluster resource 1. Open Failover Cluster Management. 2.

13 3. Select the Startup type as Manual on the General tab. Adding the primary Dsearch service as a cluster resource 1. Open Failover Cluster Management. 2. Right-click xplore service, add a resource (for example, Primary Dsearch ), select Generic Service from the drop-down list, and click Next. Best Practices Planning 13

14 3. Select the service from the list, and click Next. 4. On the Dependencies tab, add the shared Disk F: and the IP Address to the list on the right, and click Next. Best Practices Planning 14

15 Adding the secondary Dsearch service as a cluster resource This configuration is almost the same as for the primary instance. But on the Dependencies tab, in addition to adding shared Disk F: and the IP Address, add the primary Dsearch instance to the list. Validation 1. Create a document in Content Server. API>create,c,dm_document f d67 API>setcontent,c,l,text SET>I'm dancing now. My name is Jack, Wang.... OK API>save,c,l... OK API>?,c,select r_object_id,object_name from dm_document search document contains 'dance' r_object_id object_name f d67 (1 row affected) 2. Run the following search clause: API>?,c,select r_object_id,object_name from dm_document search document contains 'dance' r_object_id object_name f d67 (1 row affected) 3. Check all of the log files on the running host. For example, dsearch.log should have the following entry: Best Practices Planning 15

<event timestamp="2009-10-29 18:24:23,906" level="info" thread="http-0.0.0.0-9300-1" logger="com.emc.documentum.core.fulltext.indexserver.search.

16 <event timestamp=" :24:23,906" level="info" thread="http " logger="com.emc.documentum.core.fulltext.indexserver.search.searchserver" timeinmillisecs=" "> <message><![cdata[queryid=primaryess$6bb8afba-ee9c-4b92-b72a-0fe8bcc68886,querystring=declare option xhive:fts-analyzer-class 'com.emc.documentum.core.fulltext.indexserver.core.index.xhive.indexserveranalyzer'; for $i score $s in collection('/ccrepository/ess/data') /dmftdoc[( ( (dmftinternal/i_all_types = '030f ') ) and ( (dmftversions/iscurrent = 'true') ) ) and ( (. ftcontains ( 'dance' ) )) ] order by $s descending return <dmrow>{if ($i/dmftinternal/r_object_id) then $i/dmftinternal/r_object_id else <r_object_id/>}{if ($i/dmftsecurity/ispublic) then $i/dmftsecurity/ispublic else <ispublic/>}{if ($i/dmftinternal/r_object_type) then $i/dmftinternal/r_object_type else <r_object_type/>}{if ($i/dmftmetadata/*/owner_name) then $i/dmftmetadata/*/owner_name else <owner_name/>}{if ($i/dmftvstamp/i_vstamp) then $i/dmftvstamp/i_vstamp else <i_vstamp/>}{if ($i/dmftsecurity/acl_name) then $i/dmftsecurity/acl_name else <acl_name/>}{if ($i/dmftsecurity/acl_domain) then $i/dmftsecurity/acl_domain else <acl_domain/>}</dmrow> is running]]></message> </event> 4. Move the resource group from the host where it is running to the other host. 5. Run the same search clause as above, and then check all logs. 6. If you perform this search after the resource index server came online, dsearch.log should have the following entry: <event timestamp=" :26:07,687" level="info" thread="http " logger="com.emc.documentum.core.fulltext.indexserver.search.searchserver" timeinmillisecs=" "> <message ><![CDATA[QueryID=PrimaryESS$c f29-bc87-30d5ff6f69f1,querystring=declare option xhive:fts-analyzer-class 'com.emc.documentum.core.fulltext.indexserver.core.index.xhive.indexserveranalyzer'; for $i score $s in collection('/ccrepository/ess/data') /dmftdoc[( ( (dmftinternal/i_all_types = '030f ') ) and ( (dmftversions/iscurrent = 'true') ) ) and ( (. ftcontains ( 'dance' ) )) ] order by $s descending return <dmrow>{if ($i/dmftinternal/r_object_id) then $i/dmftinternal/r_object_id else <r_object_id/>}{if ($i/dmftsecurity/ispublic) then $i/dmftsecurity/ispublic else <ispublic/>}{if ($i/dmftinternal/r_object_type) then $i/dmftinternal/r_object_type else <r_object_type/>}{if ($i/dmftmetadata/*/owner_name) then $i/dmftmetadata/*/owner_name else <owner_name/>}{if ($i/dmftvstamp/i_vstamp) then $i/dmftvstamp/i_vstamp else <i_vstamp/>}{if ($i/dmftsecurity/acl_name) then $i/dmftsecurity/acl_name else <acl_name/>}{if ($i/dmftsecurity/acl_domain) then $i/dmftsecurity/acl_domain else <acl_domain/>}</dmrow> is running]]></message> </event> 7. If you perform this search before the index server resource came online, or while it is pending, this error message will be displayed: API>?,c,select r_object_id,object_name from dm_document search document contains 'dancing' r_object_id object_name (0 rows affected) [DM_FULLTEXT_E_SEARCH_NEW_FAIL] error: "dmftsearchnew failed with error: ESS_DMS earch::executesearch (0) : Communication Exception. Failed to perform URL: errorcode: 52: Server returned nothing (no headers, no data), General Exception, error code : -2" Best Practices Planning 16

17 Operational consideration If a failover occurs while the active xplore node is indexing, some documents might fail to be indexed because it takes a few seconds for the passive xplore node to start up. In this case, EMC recommends that you use ftintegrity to find the documents that failed to be indexed. For information about using ftintegrity, refer to the EMC Documentum xplore Administration Guide. Conclusion In this white paper, we presented a high-availability deployment of multi-instance Documentum xplore through an overview of the architecture and through detailed step-by-step instructions for deployment using. Although VMware is used as an example for the description of the deployment procedure, this white paper can be used as a reference for deploying on physical machines as well. Best Practices Planning 17

Setup for Microsoft Cluster Service Update 1 Release for ESX Server 3.5, ESX Server 3i version 3.5, VirtualCenter 2.5

Setup for Microsoft Cluster Service Update 1 Release for ESX Server 3.5, ESX Server 3i version 3.5, VirtualCenter 2.5 Setup for Microsoft Cluster Service Setup for Microsoft Cluster Service Revision: 041108