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

The configuration changes listed are specific to VMware Aria Operations for Logs 3.3.0 and later. It is assumed that the restored VMware Aria 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 VMware Aria Operations for Logs node.
  2. Perform the following configuration changes on thePrimary node:
    1. Power on thePrimary node, if it is not ON.
      Note:

      Steps b through e are applicable for VMware Aria Operations for Logs 2.5. You cannot make changes to the configuration files directly from the appliance console for VMware Aria Operations for Logs 3.0 and later. To make changes to the internal configuration options by using the web UI interface for VMware Aria Operations for Logs 3.0 and later, refer to the article KB 2123058.

    2. Use SSH to connect as a root user to the node's virtual appliance.
    3. If the VMware Aria Operations for Logs service is running, stop the service first by running the service loginsight stop command.
    4. Run cd/storage/core/loginsight/config.
    5. Run cp loginsight-config.xml#<n> backup-loginsight-config.xml where <n> is the largest number that is automatically added to the end of loginsight-config.xml during configuration changes.
    6. Open the copied version of the configuration file in the VMware Aria Operations for Logs 3.0 web UI and look for lines that resemble the following lines. This configuration change is applicable to both VMware Aria Operations for Logs 2.5 and 3.0.
      <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 thePrimary node which shows <service-group name=standalone> and the remaining two nodes are worker nodes and show <service-group name="workernode">.

    7. For thePrimary 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 thePrimary node.

      • If the DNS entry cannot be reused, replace thePrimary 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.

    8. Update the worker node IP addresses to reflect the new IP addresses.
    9. In the same configuration file, look for entries that represent NTP, SMTP and database, and appenders sections.
      Note:

      This applies to VMware Aria Operations for Logs 2.5 and 3.0. The <logging><appenders> ... </appenders></logging> section is only applicable to VMware Aria Operations for Logs 2.5. It is not supported for VMware Aria Operations for Logs 3.0.

      <ntp>
        <ntp-servers value="ntp1.domain.com, ntp2.domain.com" />
      </ntp>
       
      <smtp>
        <server value="smtp.domain.com" />
        <default-sender value="source.domain.com@domain.com" />
      </smtp>
       
      <database>
        <password value="xserttt" />
        <host value="vrli-node1.domain.com" />
        <port value="12543" />
      </database>
      
      <logging> 
         <appenders>
         <appender name= "Remote"
      class="com.vmware.loginsight.commons.logging.ThriftSocketAppender">
          <param mname="RemoteHost" value="vdli-node1.domain.com'/>
        </appender>
      </appenders>
       
       
      • 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.

      • In the <logging><appenders> ... </appenders></logging> section, change the parameter value for RemoteHost to reflect the newPrimary node FQDN or IP address.

    10. In the same configuration file, update the VMware Aria Operations for Logs ILB configuration section

      For a VMware Aria 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" />   
      <layer4-enabled value="true" />  
      <ui-balancing-enabled value="true" /> 
      </load-balancer>

      For VMware Aria Operations for Logs 2.5,

      <load-balancer> 
      <leadership-lease-renewal-secs value="5" /> 
      <high-availability-enabled value="true" /> 
      <high-availability-ip value="192.168.1.75" />   
      <layer4-enabled value="true" />  
      <ui-balancing-enabled value="true" /> 
      </load-balancer>
    11. Under the <load-balancer>...</load-balancer> section, update the high-availability-ip value if it is different from the current setting.
    12. In the VMware Aria Operations for Logs, make sure to also update the FQDN of the load balancer.
    13. Rename the updated configuration file to finish the changes.
      Note:

      This step is applicable for VMware Aria Operations for Logs 2.5 only. In VMware Aria Operations for Logs 3.0 the changes are made in the web UI.

      Run mv backup-loginsight-config.xml loginsight-config.xml#<n+1> where n is the current maximum number added to the loginsight-config.xml files.

    14. For VMware Aria Operations for Logs 2.5, restart the VMware Aria Operations for Logs service by running theservice loginsight start command.
      Note:

      For VMware Aria Operations for Logs 3.0, 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.

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

      Steps 3-9 are not applicable for VMware Aria Operations for Logs 3.0. Continue procedure for VMware Aria Operations for Logs 2.5.

  3. SSH onto the first worker node using root credentials.
  4. Stop the VMware Aria Operations for Logs service by running the service loginsight stop command.
  5. Copy the latest loginsight-config.xml file from thePrimary node to the worker node.
  6. On the worker node, run the scp root@[master-node-ip]:/storage/core/loginsight/config/loginsight-config.xml#<n>/storage/core/loginsight/config/ script.
  7. Run the service loginsight start command to start the VMware Aria Operations for Logs services.
  8. Wait 2 minutes after the VMware Aria Operations for Logs service starts in order to give enough time for the Cassandra service to start completely.
  9. Repeat procedure for each worker node.