The Control-M/Server migration exports your Control-M/Server data from the old environment so that you can import the data into the new Control-M/Server environment.
The Control-M/Server migration can be performed in Automatic or Manual mode. The Manual mode is similar to the Control-M/EM migration process.
NOTE: Automatic Control-M/Server Migration is not supported if the Control-M/Server was installed in a clustered OS environment using a virtual host name.
Automatic Control-M/Server Migration: Enables you to perform a full migration process from the new version of Control-M/Server. The new Control-M/Server must connect to the old Control-M/Server using a remote host connection, and it uses jobs to accomplish the task of validating, exporting, and importing. The automatic migration uses the new Control-M/Server to copy the migration tool to the old Control-M/Server and automatically performs the export and copies the data to the new Control-M/Server for import, as described in Migrating Control-M/Server automatically.
Automatic migration uses agentless technology, which requires both the local Control-M/Agent (installed with the Control-M/Server) and the old environment to meet the same conditions as the Control-M/Agent and remote host used for agentless execution. For more information on setting up an SSH or WMI connection, see Defining a remote host.
Manual Control-M/Server Migration: Enables you to migrate data by validating and exporting data from the old environment and importing the data to the new version, as described in Control-M/Server Manual Upgrade. You can export the data from the old environment to a file, and then import the file to the new environment.
Both the Automatic and Manual Control-M/Server migration allow for a two-phase export and import:
Static Phase 1: Export the historical and definition data while the old Control-M/Server is running. The Control-M/Server can continue to run while you export the historical and definition data. This phase can be used to test the export and import process and populate the new environment for testing.
Active Phase 2: Export only the active data. The Control-M/Server cannot be running during this phase. This export is performed if "static" phase 1 export was previously performed and only the active data needs to be copied to the new environment. This can reduce the export/import time on the day of the final migration.
If the Control-M/Server is not running when the export is started, then both the static and active data are exported to a file. If the Control-M/Server is running when the export is started, only static data is exported, and afterwards you are prompted to shut down the Control-M/Server to proceed with exporting the active data.
NOTE: Ensure that you are using the Export/Migration package from the latest fix pack before you export data from the older version. The Import process validates the version of the Export tool to ensure that data is exported in the required format.
