When you restore your system to a different host, you should make some configuration changes on the vRealize Log Insight cluster.
The configuration changes listed are specific to vRealize Log Insight 3.3.0. It is assumed that the restored vRealize Log Insight nodes are assigned different IP addresses and FQDNs than their source counterparts from which the backup was taken.
- List all new IP addresses and FQDNs that were assigned to each vRealize Log Insight node.
- Perform the following configuration changes on the master node:
Note: You can skip steps 3 to 9 for vRealize Log Insight 3.0. These steps are only applicable for vRealize Log Insight 2.5.
- Power on the master node, if it is not ON.
Note: Steps b through e are applicable for vRealize Log Insight 2.5. You can not make changes to the configuration files directly from the appliance console for vRealize Log Insight 3.0 and higher. To make changes to the internal configuration options by using the web UI interface for vRealize Log Insight 3.0 and higher, refer to the Knowledge Base article KB 2123058.
- Use SSH to connect as a root user to the node's virtual appliance.
- If the vRealize Log Insight service is running, stop the service first by running this command service loginsight stop.
- Run cd /storage/core/loginsight/config .
- Run cp loginsight-config.xml#<n> backup-loginsight-config.xml where <n> represents the largest number that is automatically suffixed to loginsight-config.xml during configuration changes.
- Open the copied version of the configuration file in your favorite editor or in the vRealize Log Insight 3.0 web UI and look for lines that resemble the following lines. This configuration change is applicable to both vRealize Log Insight 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 the master node which shows <service-group name=standalone> and the remaining two nodes are worker nodes and show <service-group name="workernode">.
- For the master node, in the newly recovered environment, veerify 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 master node.
- If the DNS entry cannot be reused, replace the master 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.
- Update the worker node IP addresses to reflect the new IP addresses.
- In the same configuration file, look for entries that represent NTP, SMTP and database, and appenders sections.
This applies to vRealize Log Insight 2.5 and 3.0.Note: The <logging><appenders>...</appenders></logging> section is applicable only to the vRealize Log Insight 2.5 and is not available for vRealize Log Insight 3.0.
<ntp> <ntp-servers value="ntp1.domain.com, ntp2.domain.com" /> </ntp> <smtp> <server value="smtp.domain.com" /> <default-sender value="email@example.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 name="RemoteHost" value="vdli-node1.domain.com" /> </appender> </appenders> </logging>
- 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 master node FQDN or IP address.
- In the <logging><appenders>...</appenders></logging> section, change the parameter value for RemoteHost to reflect the new master node FQDN or IP address.
- In the same configuration file, update the vRealize Log Insight ILB configuration section
For a vRealize Log Insight 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>For a vRealize Log Insight 2.5 appliance,
<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" /> </load-balancer>
- Under the <load-balancer>...</load-balancer> section, update the high-availability-ip value if it is different from the current setting.
- In the vRealize Log Insight, make sure to also update the FQDN of the load balancer.
- Rename the updated configuration file to finish the changes.
Note: This step is applicable for vRealize Log Insight 2.5 only. In vRealize Log Insight 3.0 the changes are made through web UI.Run : mv backup-loginsight-config.xml loginsight-config.xml#<n+1> where n represents the current maximum number suffixed to the loginsight-config.xml files.
- For vRealize Log Insight 2.5, restart the vRealize Log Insight service and run : service loginsight start.
For vRealize Log Insight 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.
- Wait for two minutes after the vRealize Log Insight service starts in order to give enough time for Cassandra services to come up before bringing other worker nodes online.
- Power on the master node, if it is not ON.
- SSH onto the first worker node using root credentials.
- Stop the vRealize Log Insight service and run : service loginsight stop.
- Copy the latest loginsight-conig.xml file from the master node to the worker node.
- On the worker node, run : scp root@[master-node-ip]:/storage/core/loginsight/config/loginsight-config.xml#<n> /storage/core/loginsight/config/.
- Run : service loginsight start.
- Wait for 2 minutes after the vRealize Log Insight service starts in order to give enough time for Cassandra service to start completely.
- Repeat the steps for each worker node.