TIBCO LogLogic LMI - Where is logappconfig.sql file located inside LMI backups?

TIBCO LogLogic LMI - Where is logappconfig.sql file located inside LMI backups?

book

Article ID: KB0077410

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Enterprise Virtual Appliance Any

Description

TIBCO LogLogic LMI can be configured to perform backups automatically to an NFS share. There are times when users may not want to perform a whole restore of the system but in some circumstances, if the database has issues, it is easier to just restore the database to an older working/stable version from the backups. This process is not recommended to be done without a TIBCO LogLogic Support Engineers supervision as this can cause additional issues if the database is not imported correctly. Backup for LMI creates several folders inside directories with naming convention such as:

ll_bkup_::ffff:1.1.1.1/ll_bkup_session_x.x.x_1552068000_0/

Where everything after ll_bkup is the IP address of the LMI server which is followed by session of the backup and the datetime stamp of the backup. Depending on the settings for backups, there could be incremental backups where a single backup is overwritten by the next iteration of the backup, or independent backups that are performed at a set time, creating a whole new directory structure with that session files.

Environment

Users must be running NFS backups and should have access to the backup file structure.

Resolution

To find the database files users will have to navigate to the following location in the file structure:

ll_bkup_::ffff:1.1.1.1/ll_bkup_session_x.x.x_1552068000_0/midnight_backup/database

Under this folder users will find three files that can be used to restore corresponding database in LMI. 

  1. logappconfig.sql 
  2. logapplogu.sql 
  3. logapprtrpt.sql
To perform an import of these files, users will first have to secure copy the files onto the LogLogic LMI's disk, then perform the following MySQL command to import the database and overwrite the existing version: 

For example, if users would like to import 'logappconfig' database then the command would be:

  • $ mysql -D logappconfig < /pathtofile/logappconfig.sql
This will then overwrite the current database with the older database file.

Note: Due to the nature of database import being an overwriting process, we do not recommend performing these steps unless it is absolutely necessary to do so. Please contact TIBCO LogLogic Support before resorting to this step. 

Issue/Introduction

This article provides the location of the backup file for database 'logappconfig' on the backup disk. LMI's backup directory structure is complex and can be tough to traverse through. One of the files users commonly have trouble finding is 'logappconfig.sql', which is used to restore that database manually should it be necessary.
Powered by Wolken Software