...
You may edit the configuration file /installs/data-migration-tool/data-migration-tool.conf before running the tool, there . There are two entries of interest:
- duration.limit (default: 999999) - limit limits the execution time in minutes, this .
This option is useful if you want to schedule the tool to run at nightsduring off-peak time. In such a case, you can limit it the tool to run for a few hours each time and schedule it to start when off-peak time starts, so performance will not suffer during normal working be impacted during peak time hours. - delete.kibana_indices (default: true) -
"true" determined whether Kibana indices should be deleted or not.
true - delete old Kibana indices - all exiting Kibana dashboards and other settings will be deleted.
"false" - keep and migrate Kibana indices to the new store version - Note: Even when migrating the Kibana indices to the new version, the however Kibana version that comes with DPOD 1.0.9 will not be able .0 is unable to read the old indices format, so it is up to you to fix the indices manually according to Kibana's documentation. - Leave the other settings in data-migration-tool.conf as they are, unless advised otherwise by support.
Running the Data Migration Tool
To run the data - migration - tool manually:
| Code Block | ||
|---|---|---|
| ||
/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, the server load and the server loadhardware.
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 off-peak hours.
Please review the Data-Migration data migration tool log file if the console displays any error messagesmessage.
When the Data Migration data migration completes, the console or log file will display the following line message:
| Code Block | ||
|---|---|---|
| ||
Data migration tool finished successfully |
Interrupting the Data Migration Tool
Pressing ctrlCtrl+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 night, the tool will try to migrate the same index again and will never advance to the next index.
...
Admin Console -> Utilities -> Store -> Store Allocation
Run the update_store_allocation process Update Store Allocation utility:
Confirm the operation :
...