Issue/Introduction

In Cloud Platforms in the ZMigrate migration console, after an administrator manually deletes a connected destination ZSphere platform connection such as ZSphere-<platform-id>#<platform-address>, destination-platform data cannot be retrieved when another migration task is created in ZSphere.

Symptoms

• UI exception: In Cloud Platforms for the ZMigrate migration service, the destination ZSphere platform is displayed abnormally and its host resources/details cannot be loaded.
• Audit log records: The system audit log (_LOGS) records a manual deletion:

  {"action":"Delete cloud","description":{"Name":"ZSphere-<platform-id>","Msg":"Cloud connection deleted."},"type":"auth_zsphere","status":true}
  {"action":"Delete cloud","description":{"Name":"ZSphere-<platform-id>","Msg":"Cloud connection deleted."},"type":"ZSphere","status":true}
  {"action":"Delete server","description":{"Name":"null","Msg":"Server deleted."},"type":"General Purpose","status":true}

• Business impact: Recovery/migration tasks can no longer be created for the destination platform, and running tasks cannot synchronize destination-platform metadata.

Environment

• Product: ZVF / ZSphere with the ZMigrate migration service
• Components: ZMigrate console (trekercontrol), ZSphere API authentication module (auth_zsphere), and Data Gateway
• Diagnostic bundles: DiagnosticsReport_Management_*.zip / DiagnosticsReport_VMware_*.zip

Possible causes

This symptom is usually caused by one of the following:

1. Cascade residue and inconsistent metadata: Manually deleting the cloud-platform connection removes only the upper-layer authorization relationship (auth_zsphere / Delete cloud), while lower-layer cache or host-service mappings (General Purpose Server / Data Gateway) are not completely removed.
2. Machine ID/node unique-identifier conflict: The ZMigrate local database, such as pixiu.sqlite, retains the original platform's machine-id or tenant account (_ACCT_UUID) binding, causing Duplicated machine ID validation to reject re-adding it.
3. Migration-service cache not refreshed: Background trekercontrol / httpd processes retain an old session or connection pool, so the frontend retrieves stale data or encounters a null-pointer exception after deletion.

Resolution

1. Check the audit log and operation sequence

• Location: Sign in to the ZMigrate administration interface and view operation logs, or export and extract DiagnosticsReport_Management_*.zip and inspect the _LOGS table in pixiu.sqlite.
• Check: Confirm whether Delete cloud or Delete server operations occurred before the failure.
• Expected result: Compare the deletion's _ACCT_UUID with the current tenant and determine whether this was an accidental deletion or an incomplete cascade deletion.

2. Check the underlying Data Gateway and server registration state

• Check: In Data Gateway and Cloud Platforms, confirm current bindings among the Data Gateway and source/destination cloud platforms.
• Exception handling: If the cloud platform associated with a Data Gateway was deleted but the gateway remains registered, first delete the associated Data Gateway in the UI, and then fully unbind the platform.

3. Clear residual Machine IDs and duplicate registrations

• If re-adding the platform reports Duplicated machine ID:

1. Check whether the destination ZSphere platform address or AccessKey changed.
2. On the ZMigrate management node, check the /usr/local/trekercontrol cache directory and the corresponding platform registration in the SQLite database.
3. After completely removing the residual associated Server record, use Setup wizard or Cloud Platforms > Add to add it again.

4. Restart core ZMigrate services to refresh connection pools

• Commands (run in the ZMigrate VM terminal):

  systemctl restart trekercontrol
  systemctl restart apache2 # or httpd

• Expected result: Restarting the services releases the old cloud-platform connection cache.

Additional information

• Related functions: ZMigrate cloud-platform integration, ZSphere destination management, and Data Gateway (NBD) distribution
• Best practice: For Data Gateways, platform connections, and associated resources automatically managed or bound by ZMigrate, avoid bypassing the standard workflow to delete them directly in the ZMigrate UI. Before deletion, confirm that no migration/recovery task is running and retain the operation time, platform-connection name, and diagnostic bundle.