In a PlateSpin Migration Factory environment, PlateSpin Transformation Manager and PlateSpin Migrate Connector work together to execute planned migrations or to track manual migrations on your PlateSpin Migrate servers
Ensure that your environment meets the deployment requirements for PlateSpin Migration Factory.
Ensure that network communications are properly configured and operational.
Configure the global migration settings that apply to all Migrate Connector instances.
PlateSpin Migrate servers are represented in a project by Migration Server resources. Communications with the Migrate Server require that the resource have the Migrate Server URL and valid login credentials for Migrate.
Planning actions in PTM do not require access to the related PlateSpin Migrate server. Users can set up Migration Server resources with minimal information for planning purposes.
Automation and tracking actions require access to the Migrate server.
A Project Manager or Project Architect typically performs the following tasks for the project.
Configure a Migration Server resource for each Migrate server that is available to the project.
For each workload, use auto-assignment of Migration Server resources, or associate a specific Migration Server resource with the workload.
Ensure that associated Credential resources are valid before you submit the workload for automated execution:
Source workload
Target Platform resource
Target Migration Server resource
Ensure that the workload Transformation Plan is in Automated Mode.
The Mode setting in the workload Transformation Plan must be set to Automated.
Configure required information for the proposed workload.
Automated workload discovery is required prior to submitting the workload for execution. Information added from the Import Spreadsheet is not sufficient for automation.
Ensure that the workload is up and running.
Ensure that the target platform is up and running.
Ensure that the assigned PlateSpin Migrate Server is up and running.
All Migrate Connectors use the global Migrate Connector settings that the Administrator user configures for the PTM application.
Deploy a Migrate Connector instance in the same network as the source workloads.
You need the Project ID to configure a dedicated Migrate Connector for a project.
The Migrate Connector must be up and running.
PlateSpin Transformation Manager supports automated migration in a PlateSpin Migration Factory deployment. Ensure that your migration environment meets the requirements for automation.
PlateSpin Transformation Manager supports automated migration to VMware vCenter and Microsoft Azure target platforms that meet the PlateSpin Migrate requirements. Ensure that the target platforms you create in PTM meet the PlateSpin Migrate requirements for migration to those platforms.
See the following resources in the PlateSpin Migrate 2019.5 User Guide:
Migration to Microsoft Azure
Migration to VMware vCenter Clusters
Before you submit a workload for automated migration:
Ensure that the Credentials resource associated with the target platform contains valid credentials for the target. Credentials are needed for the setup of the target VM on the platform.
Ensure that the target platform is up and running.
Ensure that the network connections are working between the assigned PlateSpin Migrate Server and the target platform.
Before you begin to submit a workload for automated migration:
Deploy PlateSpin Migrate servers in your environment.
See the PlateSpin Migrate 2019.5 Installation and Upgrade Guide.
PlateSpin Migrate servers must be accessible for network communications.
See Access and Communication Requirements across Your Migration Network
in the PlateSpin Migrate 2019.5 User Guide.
Ensure that the Event Messaging port is open on each Migrate Server.
See Enabling Event Messaging for PlateSpin Migration Factory
in the PlateSpin Migrate 2019.5 User Guide.
Ensure that the Migrate servers are up and running.
In PTM, configure a Migration Server resource for each Migrate server that you plan to use for your project.
You can create Migration Server resources without the detailed information for initial planning. Select Automated Migration in the workload’s Transformation Plan to allow the PlateSpin Migrate Connector to manage PlateSpin Migrate server assignments from among the Migration Server resources that you create for the project.
Before you submit the workload for automated execution, ensure that associated Credential resource is valid for each Migrate server.
PlateSpin Transformation Manager supports tracking for external migrations performed in a PlateSpin Migration Factory deployment. Ensure that your migration environment meets the requirements for tracking.
PlateSpin Transformation Manager supports tracking the status of external migrations to any target platform supported by PlateSpin Migrate. External migrations refers to migrations that you configure and execute by using the native Migrate interfaces instead of the PTM interfaces.
For information supported migrations, see Supported Configurations
in the PlateSpin Migrate 2019.5 User Guide.
PlateSpin Transformation Manager supports enhanced tracking of external migrations to the following supported target platforms that have matching platforms in PTM:
VMware vCenter server (clusters)
Microsoft Azure
Amazon Web Services
Enhanced tracking refers to additional workload details and resource associations that you can monitor in PTM. In the Workload dialog, PTM displays richer details about the workload settings. In the Platform dialog, you can view information about the platform resources and their associations with tracked workloads.
Before you begin to submit a workload for automated migration:
Deploy PlateSpin Migrate servers in your environment.
See the PlateSpin Migrate 2019.5 Installation and Upgrade Guide.
PlateSpin Migrate servers must be accessible for network communications.
See Access and Communication Requirements across Your Migration Network
in the PlateSpin Migrate 2019.5 User Guide.
Ensure that the Event Messaging port is open on each Migrate Server.
See Enabling Event Messaging for PlateSpin Migration Factory
in the PlateSpin Migrate 2019.5 User Guide.
Ensure that the Migrate servers are up and running.
Configure and execute migrations by using the native PlateSpin Migrate interfaces.
Configure a Migration Server resource for each PlateSpin Migrate Server that you plan to use for your project.
Deploy a PlateSpin Migrate Connector in each of the source networks for the project. For each Connector, assign one or more Migration Server resources that will be used to migrate workloads in the source network.
Import workloads from the source network. PTM imports them and matches them with the migration workloads on the Migrate Server.
Ensure that the assigned Connectors are up and running.
Configure a target platform in PTM that contains one or more of the target platforms you have configured on your PlateSpin Migrate Servers.
VMware vCenter server
Microsoft Azure
Amazon Web Services