...
The upgrade process checks the existence of ElasticSearch Store indices that were created in early versions of the product.
In case that early version indices exist, the upgrade process will stop and notify you of a manual step that you will need to run :
...
Running the Data Migration Tool
Run To run the data-migration-tool manually:
| Code Block | ||
|---|---|---|
| ||
/installs/data-migration-tool/data-migration-tool.sh |
...
Make sure not to interrupt SSH session during the Data-Migration operation.
Alternatively, you can run
...
the tool in a "no hang-up" mode, which will cause the process to continue running even after the SSH session is closed. In this mode, the console output will be written to the nohup.log file in the local directory.
...
| Code Block |
|---|
nohup /installs/data-migration-tool/data-migration-tool.sh & |
The data migration process may take anywhere between a few minutes and a few days, depending on the amount of data and the server load.
A rough estimation of the time left will be calculated and presented on the console output during the process run. These estimations will also be written to the log file.
The estimation is based on current server load, so it may change significantly between peak and quiet hours.
Please review the Data-Migration log file if the console displays any error messages.
When the Data - Migration completes, check the console or log file for will display the following line :
| Code Block | ||
|---|---|---|
| ||
Data migration tool finished successfully |
...
Pressing ctrl+C or setting duration.limit in the configuration file will stop the tool during the migration process.
Stopping the tool will cause it to re-process the last index that was migrated on the next run.
While this is usually not an issue, note that on some cases it may cause complications, for example:
1. The user wants the tool to run during a nightly maintenance window, between 2-4 AM.
2. The tool is scheduled using cron to 2 AM and the duration.limit setting is set to 120 minutes.
3. For this specific user, depending on its hardware and data sizes, processing of each index takes about 3 hours.
4. Since the tool is interrupted after 2 hours, on the next runnight, the tool will try to migrate the same index again and againwill never advance to the next index.
Resuming Software Update
...