Troubleshoot the Migration Tool Issues
This topic describes how to troubleshoot issues occurred on our migration tool.
This page lists the issues and troubleshooting steps occurred while running the migration tool:
Events Service Data Migration Fails
{HOME}/migration-tool/SERVICE-MIGRATION-STATUS.txt file to verify the Events Service data migration status.
Migration Status - Updated: 2025-12-09 13:24:55
====================================================
EUM | Status: running
SYNTH | Status: running
CONTROLLER | Status: saturated
EVENTS | Status: failed
====================================================
failed, in some logs, you may observe the following pattern:
config_manager - restore_worker - ERROR - Elasticsearch-migration-restore-worker: Restore submit failed: ApiError(500, 'snapshot_restore_exception', '[appdynamics-analytics-backup:<snapshot_name>/<snapshot_id>] cannot restore index [<index_name>] with [<index_shard_count_1>] shards from a snapshot of index [<index_name>] with [<index_shard_count_2>] shards')
config_manager - restore_worker - ERROR - Elasticsearch-migration-restore-worker: Restore submit failed: ApiError(500, 'snapshot_restore_exception', '[appdynamics-analytics-backup:snapshot_20260223_131558/smjrnOQhREWIsKX9R6U7Ag] cannot restore index [appdynamics_schemas] with [1] shards from a snapshot of index [appdynamics_schemas] with [3] shards')
-
Log in to Virtual Appliance and run following command:CODE
appduser@appdva-test7-vm348:~$ kubectl get svc -n esSample output:CODENAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE appd-es-http ClusterIP 10.152.183.210 <none> 9200/TCP 6d19h appd-es-internal-http ClusterIP 10.152.183.56 <none> 9200/TCP 6d19h appd-es-node ClusterIP None <none> 9200/TCP 6d19h appd-es-transport ClusterIP None <none> 9300/TCP 6d19h -
Specify the cluster IP address of tne
<appd-es-http>service and run the command.CODEcurl -u username:password -X DELETE "http://10.152.183.210:9200/<index_name>"Note: Obtain theusernameandpasswordfor this command from theconfig.yamlfile. Go to theservices.eventssection and copy the username and password.CODEusername: va_es_user password: va_es_password
Incorrect Data Migration Status is Displayed for the Controller
Sometimes, the Controller's data migration status may appear as saturated even before the tool completes the initial data backup and restore process.
Wait for the controller_full_backup_restore_completed.marker file to appear in {HOME}/migration-tool to confirm that the Controller's data migration is fully saturated.