PowerProtect Data Manager 19.10 Administration and User Guide

Set up and manage indexing

Set up a Search Engine node and configure indexing.

1. From the PowerProtect Data Manager UI, select Infrastructure > Search Engine, and then click Add Node.
2. In the Add Search Engine Node wizard, provide the required parameters.
   • Hostname, IP Address, Gateway, DNS, and Netmask—Note that only IPv4 addresses are supported.
   • vCenter—If you have added multiple vCenter server instances, select the vCenter server on which to deploy the Search Engine node.
     NOTE Ensure that you do not select the internal vCenter server.
   • ESX Host/Cluster—Select on which cluster or ESXi host you want to deploy the Search Engine node.
   • Network—Displays all the networks that are available under the selected ESXi Host/Cluster. For virtual networks (VLANs), this network carries management traffic.
   • Data Store—Displays all datastores that are accessible to the selected ESXi Host/Cluster.
3. Click Next.
   The Networks Configuration page displays.
4. On the Networks Configuration page:

   The Networks Configuration page configures the virtual network (VLAN) to use for Data for Management Components traffic. To continue without virtual network configuration, leave the Preferred Network Portgroup selection blank and then click Next.

   1. From the Preferred Network Portgroup list, select a Virtual Guest Tagging (VGT) group.
      VST (Virtual Switch Tagging) groups are not supported.

      The list displays all virtual networks within the trunk range. If you select a portgroup that contains multiple networks, PowerProtect Data Manager automatically selects all networks. Individual networks cannot be selected.

      A Search Engine node requires an IP address from the static IP pool for each selected virtual network. If there are not enough IP addresses in a pool, the wizard prompts you to supply additional addresses for that network.

      Ensure that the selected virtual networks support a traffic type that is compatible with Search Engine nodes.

   2. If required, type an available static IP address or IP address range in the Additional IP Addresses column for the indicated virtual network.

      For convenience when working with multiple virtual networks, you can also use one of the Auto Expand options:

      • Expand Last IP—The wizard increments the host portion of the last IP address in the static IP pool. Click Apply.
      • Same Last Digit—The wizard adds the network portion of the IP address to the specified value. Type the host portion of the IP address and then click Apply.

      The wizard updates the value in the Additional IP addresses column for each network. Verify the proposed IP addresses.

   3. Click Next.
5. On the Summary page, review the information and then click Finish.
   The new Search Engine node is deployed, and details are displayed in the lower panel.
6. (Optional) Repeat the previous steps to deploy additional Search Engine nodes to the cluster.
   NOTE Ensure that the previous Search Engine node successfully deploys before you add another.
7. In the Configure Search Engine dialog box, enable or disable indexing, accept or change the expiration period, and then click OK.
   NOTE

   • When the index cluster reaches 70 percent, an alert is generated. When it reaches 90 percent, an alert is generated and indexing is suspended. Specify a global index expiry interval to periodically clean up indexes, which frees up space.
   • To turn off or modify indexing, select Infrastructure > Search Engine, select the cluster, and click Configure Cluster. From the Configure Search Cluster dialog box, you can enable/disable the service or change the number of expiration days.
   • Indexes expire according to the global setting or when the associated copies expire, whichever occurs first.
   • To stop indexing assets that have been added to a protected protection policy, disable the indexing option during protection policy configuration.
   • You can add up to a maximum of 5 Search Engine nodes.