IBM Operations Analytics - Log Analysis, Version 1.3.0

Backing up and migrating data

You use the same script to back up, restore, and migrate your data.

Before you begin

Read about the limitations that apply to this procedure. For more information, see Backup and migration limitations
If you do not configure a key-based Secure Shell (SSH) authentication as part of the installation, you are prompted for the password during the restoration. For more information about setting up SSH, see Setting up Secure Shell to use key-based authentication
If you use the Overlaps() function in the Annotation Query Language (AQL) for any Insight Packs, you must update your code before you migrate the data. The function used 4 parameters, including 2 null statements in the Insight Packs in versions previous to 1.3. The null statements are no longer required and can be removed. For example, if your code contains a statement such as where Overlaps(D.OrginalDateSpan, T.nonnormative_time, 0, 0);, you must remove the null statements, changing it to where Overlaps(D.OrginalDateSpan, T.nonnormative_time);. If you do not make this correction, the ingestion into datasources that uses these Insight Packs fails.

About this task

These items are backed up and migrated by this procedure:

Saved searches, tags, and Data Sources
Data Types including Source Types, Rule Sets, File Sets, and Collections.
Topology configuration files
Usage statistics
LDAP configuration files
Custom Apps
Insight Packs
Log File Agent (LFA) configuration files
License configuration files
All chart specifications including custom chart specifications

In addition to these files, a number of files that are not required for a new installation are also backed up and maintained for reference purposes. These files include:

Log files that are generated by IBM Operations Analytics - Log Analysis
Log files that have been uploaded in batch mode

Data other than the types of listed previously are not backed up or restored. Any customization that is made outside the files listed here must be migrated manually. For example, user information and changes to passwords for default users are not migrated to the target server.

Procedure

To back up and restore data in IBM Operations Analytics - Log Analysis 1.3:

Back up your data. For more information, see Backing up data.
Restore your data. For more information, see Restoring data.

To migrate data from IBM Operations Analytics - Log Analysis 1.2.0.3 to 1.3:

Back up your data in 1.2.0.3.
Move the backed up compressed files to the <Backup_dir> on the 1.3 server.
Restore the data on the 1.3 server.

What to do next

If you migrate data to a new target server, you must complete the following steps to update the data source with the relevant information for the machine:

Log in to IBM Operations Analytics - Log Analysis and open the Data sources workspace.
Identify the data sources that use Local file as the location in their configuration. For each of these data sources, open the data source and complete the steps in the wizard without changing any data. This action updates the data sources with the relevant information for the new machine.
Identify the data sources that use Custom as the location in their configuration. For each of these data sources, open the data source and complete the steps in the wizard, updating the host name to match the new one.

Feedback