When you restore your system to a different host, you should make some configuration changes on the Operations for Logs cluster.

The configuration changes listed are specific to Operations for Logs 3.3.0 and later. It is assumed that the restored Operations for Logs nodes are assigned different IP addresses and FQDNs than their source counterparts from which the backup was taken.

Procedure

  1. List all new IP addresses and FQDNs that were assigned to each Operations for Logs node.
  2. Perform the following configuration changes on the primary node:
    1. Power on the primary node, if it is not ON.
      Note:

      To make changes to the internal configuration options by using the web UI interface for Operations for Logs 3.0 and later, refer to the Knowledge Base article KB 2123058.

    2. Open the copied version of the configuration file in the Operations for Logs web UI and look for lines that resemble the following lines. This configuration change is applicable to all Operations for Logs versions. 
      <distributed overwrite-children="true">
  <daemon host="prod-es-vrli1.domain.com" port="16520" token="c4c4c6a7-f85c-4f28-a48f-43aeea27cd0e">
    <service-group name="standalone" />
  </daemon>
  <daemon host="192.168.1.73" port="16520" token="a5c65b52-aff5-43ea-8a6d-38807ebc6167">
    <service-group name="workernode" />
  </daemon>
  <daemon host="192.168.1.74" port="16520" token="a2b57cb5-a6ac-48ee-8e10-17134e1e462e">
    <service-group name="workernode" />
  </daemon>
</distributed>

      In this code snippet, there are three nodes. The first one is the primary node which shows <service-group name=standalone> and the remaining two nodes are worker nodes and show <service-group name="workernode">.

    3. For the primary node, in the newly recovered environment, verify if the DNS entry that was used in the pre-recovery environment can be reused.

      • If the DNS entry can be reused, you only need to update the DNS entry to point to the new IP address of the primary node.

      • If the DNS entry cannot be reused, replace the primary node entry with the new DNS name, pointing to the new IP address.

      • If the DNS name cannot be assigned, as a last option, update the configuration entry with the new IP address.

    4. Update the worker node IP addresses to reflect the new IP addresses.
    5. In the same configuration file, look for entries that represent NTP, SMTP and database, and appenders sections. 
      <ntp>
  <ntp-servers value="ntp1.domain.com, ntp2.domain.com" />
</ntp>
 
<smtp>
  <server value="smtp.domain.com" />
  <default-sender value="[email protected]" />
</smtp>
 
<database>
  <password value="xserttt" />
  <host value="vrli-node1.domain.com" />
  <port value="12543" />
</database>

      • If the configured NTP server values are not valid in the new environment, update these in the <ntp>...</ntp> section.

      • If the configured SMTP server values are not valid in the new environment, update these in the <smtp>...</smtp> section.

      • Optionally, change the default-sender value in the SMTP section. The value can be any value, but as a good practice, you should represent the source from where the email was sent.

      • In the <database>..</database> section, change the host value to point to the primary node FQDN or IP address.

    6. In the same configuration file, update the Operations for Logs ILB configuration section

      For a Operations for Logs appliance,

      <load-balancer> 
<leadership-lease-renewal-secs value="5" /> 
<high-availability-enabled value="true" /> 
<high-availability-ip value="10.158.128.165" />  
<high-availability-fqdn value="LB-FQDN.eng.vmware.com" />  
<layer4-enabled value="true" />  
<ui-balancing-enabled value="true" /> 
</load-balancer>
    7. Under the <load-balancer>...</load-balancer> section, update the high-availability-ip value if it is different from the current setting.
    8. In the Operations for Logs, make sure to also update the FQDN of the load balancer.
    9. Restart the Operations for Logs service and run.
      Note:

      This can be achieved from the web UI by going to the Cluster tab on the Administration page. For each node listed, select its hostname or IP address to open the details panel and click Restart Log Insight. The configuration changes are automatically applied to all cluster nodes.

    10. Wait for at least two minutes after the Operations for Logs service starts in order to give enough time for Cassandra services to come up before bringing other worker nodes online.