How to export log sources from a TIBCO LogLogic LMI appliance
Article ID: KB0077225
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Log Management Intelligence | all versions |
Description
There are situations where you don't need a full database or table dump but rather you just want to export device configurations from one appliance to another, such as to preload sources on destination appliances that will have syslog data forwarded to them and you don't want to wait for all the sources to be auto-identified. This procedure shows how to export just the device configuration in XML format rather than in a database dump. This XML data can then be used to restore the log source configuration data onto the same appliance from which it came or it can be used to import the configuration data onto another LogLogic appliance. And just in case you want to know how to export the entire configuration from the database the procedure is included for that.
Issue/Introduction
This article shows how to export log sources from an LMI appliance without performing a database dump.
Resolution
1. Login to the LogLogic appliance web GUI.
2. Go to Administration->Import/Export.
3. Click the Export tab.
4. Select Devices from the Entities pull-down list.
5. Move all devices to Selected Entities.
6. Select InsertOrUpdate from Export Mode.
7. Click the Export button.
This will export the details into an XML file which can then be imported into any LMI version because it's not dependent on any database schema details.
This method can also can be used for alerts, users, search filters, custom reports and packages.
To import the data use the Import tab.
An alternate method to backup the configuration data via command line involves performing a database dump. This restricts the import to being on an appliance with the exact same LMI version.
1. SSH to the appliance and login as ”toor".
2. Save the database configuration:
$ cd /loglogic/tmp
$ mysqldump --database logappconfig > logappconfig.dump
To restore the configuration database via command line:
1. Use WinSCP and login as toor to move the logappconfig.dump to the destination LogLogic appliance.
2. SSH to the appliance and login as ”toor”.
3. Change to the directory where you moved logappconfig.dump and run the following commands:
$ cd /loglogic/tmp
$ mtask stop
$ /etc/init.d/mysql start
$ mysql -D logappconfig < logappconfig.dump
$ /etc/init.d/mysql stop
$ mtask start
$ watchqueue <<< You may have to execute watchqueue two or three times until it can connect to mtask
Restoring the configuration database successfully restores all configuration information with the exception of the Network Configuration and Time Tabs under Administration->System Settings.
2. Go to Administration->Import/Export.
3. Click the Export tab.
4. Select Devices from the Entities pull-down list.
5. Move all devices to Selected Entities.
6. Select InsertOrUpdate from Export Mode.
7. Click the Export button.
This will export the details into an XML file which can then be imported into any LMI version because it's not dependent on any database schema details.
This method can also can be used for alerts, users, search filters, custom reports and packages.
To import the data use the Import tab.
An alternate method to backup the configuration data via command line involves performing a database dump. This restricts the import to being on an appliance with the exact same LMI version.
1. SSH to the appliance and login as ”toor".
2. Save the database configuration:
$ cd /loglogic/tmp
$ mysqldump --database logappconfig > logappconfig.dump
To restore the configuration database via command line:
1. Use WinSCP and login as toor to move the logappconfig.dump to the destination LogLogic appliance.
2. SSH to the appliance and login as ”toor”.
3. Change to the directory where you moved logappconfig.dump and run the following commands:
$ cd /loglogic/tmp
$ mtask stop
$ /etc/init.d/mysql start
$ mysql -D logappconfig < logappconfig.dump
$ /etc/init.d/mysql stop
$ mtask start
$ watchqueue <<< You may have to execute watchqueue two or three times until it can connect to mtask
Restoring the configuration database successfully restores all configuration information with the exception of the Network Configuration and Time Tabs under Administration->System Settings.
Feedback
Yes
No
Powered by
