Storage Foundation and High Availability Solutions 7.3.1 HA and DR Solutions Guide for Microsoft SharePoint 2010 - Windows

To configure the application service group manually

1. Create a service group by providing the following values:

   • Service group name

   • Systems that will be part of the service group for the Search service application

   • Service group type

     The service group should be of the type Failover.

   • Service group template

     In the SFW HA environment, select the SharepointSearch-VMGroup template.

     In the SFW environment, select SharepointSearch-NetAppGroup template.

2. Launch the SharePoint 2010 Management Shell, and execute the following PowerShell script:

   C:\Program Files\Veritas\Cluster Server\bin\SharePointSearch\SearchServiceAppDetails.ps1

   Provide the application name as input. The script retrieves the details of the Search service application components and displays them on the screen. These details include the property values of the Admin, Crawl, and Query components. Some of these values are to be used as attribute values for the agent resources.

   The following graphic depicts a sample output of the script.

   
3. In the Cluster Explorer, update the attributes of the storage resources (for example, VMDg and MountV in the SFW HA environment) and network resources with appropriate values.
4. Update the Query Share resource (for example, SharePointSearch_VM_Query_Share) attributes by copying over the values of the corresponding Query component properties as follows:

   • PathName = IndexLocation

     Note:

     Do not include the drive letter when copying over this value.

   • ShareName = Name

   • LanmanResName: Leave this attribute value empty.

5. Update the following attributes of the Admin, Crawl, and Query resources with the appropriate values:

   • SPSFarmAdmin

   • Domain

   • Password

   • SearchAppName

   • ComponentID

     The component ID is not required for the Admin resource.

     For the Crawl or Query resource, copy the value of the corresponding Crawl or Query ComponentID property.

6. On the systems that are hosting the Crawl and Query components, back up the registry keys for those components. These registry keys are displayed in the output of the PowerShell script that you ran previously.

   Note:

   It is important to back up these registry keys so that you can use them to restore the Search service application if the need arises.

7. In the Cluster Explorer, update the Keys attribute of all the RegRep resources by copying over the registry key names of the corresponding Crawl or Query component.

   A sample key-value pair for the Query component is as follows:

   HKLM\SOFTWARE\Microsoft\ Office Server\14.0\Search\Applications\ 3c8f51e3-ce82-45c9-bc99-81567c24beae-query-1	3c8f51e3-ce82-45c9-bc99-81567c24beae-query-1_App.reg
   HKLM\SOFTWARE\Microsoft\ Office Server\14.0\Search\Components\ 3c8f51e3-ce82-45c9-bc99-81567c24beae-query-1	3c8f51e3-ce82-45c9-bc99-81567c24beae-query-1_Comp.reg

   Note:

   Make sure that the values are unique by appending a string to indicate the key type.

8. Do not provide any attribute values for the SearchService resource.
9. Enable each resource in the service group.

   • When enabling the SearchService resource, a warning about its empty attributes is displayed. Ignore the warning and proceed.

   • When enabling the Query Share resource, a warning about the LanmanResName attribute is displayed. Ignore the warning and proceed.

10. Bring the service group online.

    The following graphic depicts a sample service group configuration.

    
11. Optionally, you can split the service group depending on the Search service application components that you want to monitor. To do so, retain the resources required for that agent and delete the others.

    Take the following requirements into consideration:

    • For each service group pertaining to Crawl or Query component, make sure that the agent resource is a child of the RegRep resource, and the RegRep resource is a child of the SearchService resource.

    • For the service group pertaining to the Admin component, make sure that the agent resource is a child of the SearchService resource.

    • Make sure that the NIC resource is part of the service group for each component.

    The following graphics depict a sample service group configuration for each Search service application component.