Migrate Indexes to newer version
For EventLog Analyzer version 8.6 and above, you need to migrate older version indexes to the newer version for much faster and efficient log search performance, report generation and scheduling.
You can migrate the indexes in two ways.
- You should run the EventLog Analyzer and MigrateIndex.bat/sh script as same user.
- Apply EventLog Analyzer 8.6 Service pack, start the product and then execute MigrateInde.bat/sh script.
Migrating indexes associated with the scheduled report
If your indexes associated with the scheduled reports pertain to the older version then this might return empty or partial report results. You need to migrate the indexes to the newer version to resolve this issue. Follow the steps to migrate the indexes associated with the scheduled reports:
Go to ~/EventLog Analyzer_HOME/TroubleShooting folder and run MigrateIndex.bat/sh utility script.
In the menu driven interface of the script, select option 1 to migrate the indexes associated to the scheduled reports.
You'll now be notified about the disk space needed for migration and the expected time to complete the migration.
- If you have the required disk space, proceed by typing 'yes'.
Migrating indexes belonging to custom date range
Index migration can also be carried out by specifying particular date range to which the indexes belong. Follow the steps below to migrate indexes belonging to custom date range:
Go to ~/EventLog Analyzer_HOME/TroubleShooting folder and run MigrateIndex.bat/sh script.
Type option 2 to migrate indexes belonging to custom date range.
You will now be displayed with the available date ranges.
Type the start date and end date to start the migration.
Before the migration process starts, you will be notified with the disk space required and the expected time of migration. Make sure that you have the required disk space and start the migration by typing 'yes'.
The migration once started, will be completed within the time range. Do not intervene during the migration process. There is a high possibility of data loss if you abort migration.