PlateSpin Transformation Manager tracks the status of external migrations for matching workloads on the Migrate server, whether they are initiated through the Migrate Web Interface or the Migrate Web Client. The Migrate REST APIs return more information for migrations configured and executed using the Migrate Web Interface, as identified in Table 19-1.
Table 19-1 Information Reported by Migrate for External Migrations
|
Information |
Migrate Client |
Migrate Web Interface |
|---|---|---|
|
Proposed configuration |
Not available to PTM |
Displayed as read only in the Workload dialog. |
|
State events |
Limited events. See Table 19-2. |
Same events reported for PTM automated migrations. |
Table 19-2 describes the status events for migrations in the Migrate Client.
Table 19-2 States Reported for Migrations Executed in PlateSpin Migrate Client
|
Migrate Client Migration Job Status |
Description |
|---|---|
|
Added |
The source workload has been added to Migrate Client. |
|
In Progress |
A replication has started. |
|
Replicated |
A replication has ended. |
|
Copied |
A replication has ended. The source is up. |
|
Completed |
The workload has been cut over to the target workload. The source is down. |
|
Removed |
The workload has been removed from Migrate Client. |
|
Stuck |
A recoverable error occurred. |
|
Error |
A non-recoverable error occurred. |
You can import workloads to PTM and the project’s Migrate servers in any order. When you import workloads using the PlateSpin Transformation Manager discovery service, the Connector scans the Migration Server resources to match the workload with external migration jobs you set up using the Migrate Client. It does not match workloads set in Automated Mode.
The Connector checks for matching external workloads on the project’s PlateSpin Migrate servers when the following events occur:
When you import workloads to PTM for a project
When you modify the Mode from Automated to Manual for an individual workload
When you launch or restart the Migrate Connector
When you add a Migrate Server as a Migration Server resource for the project
When the Connector subscribes to event messages from a new Migration Server resource
When the Connector polls for events (every 5 minutes by default)