The Control-M Upgrade process requires that you prepare for the next production environment by installing the new Control-M version in the new environment while the old environment continues to run. First, you install the new release of Control-M and apply the latest fix pack in the new environment. After preparing the new installation, you can upgrade all of the static data such as definitions, configurations, and more, from the old environment to the new environment.
Before transferring the active data, you must test the environment.
The setup is performed while the old production continues to run, which enables you to reduce the amount of data to transfer, and the amount of downtime. When it is time to transfer the active data, you bring the production environment down for a short time, because all the static data has been transferred and the environment has already been tested.
Control-M Upgrade comprises the following tools:
Control-M/EM Upgrade Tool: Upgrades your Control-M/EM data from a source environment to version 8.0.00, which enables you to continue working in a new version of Control-M/EM. The supported source versions include 6.3.01, 6.4.01, and 7.0.00.
You can upgrade Control-M/EM and continue working with older versions of Control-M/Server. For more information on setting your plan for your site, see Migration planning process.
The steps include:
Installing the Control-M/EM Upgrade Export Pack on the source version
Control-M/Server Upgrade Tool: Upgrades your Control-M/Server data from a source environment to version 8.0.00, including job definitions, configurations, and active jobs. To minimize Control-M/Server down time, you can upgrade the historical data (logs) and definitions data during the preparation phase, and keep the Control-M/Server running the active jobs until the later phase when you are prompted to bring down the Control-M/Server. You are also prompted to set the number of log days to include when you export from the source environment, which reduces the transfer if you do not need the data. The supported source versions include 6.3.01, 6.4.01, 7.0.00, and 8.0.00.
You can only upgrade Control-M/Server if you have already upgraded Control-M/EM to version 8.0.00. For more information on setting your plan for your site, see Migration planning process. There are two types of Control-M/Server upgrades, as described in Control-M/Server Migration:
Automatic Control-M/Server upgrade process: Enables you to perform a full upgrade process from the destination version of Control-M/Server. The destination Control-M/Server must connect to the source Control-M/Server using a remote host connection, and uses jobs to accomplish the task of validating, exporting, and importing. The automatic upgrade uses the destination Control-M/Server to copy the upgrade tool to the source Control-M/Server and automatically performs the export and copies the data to the destination for import, as described in Migrating Control-M/Server automatically.
Manual Control-M/Server upgrade process: Enables you to perform Control-M/Server upgrade by installing Control-M/Server Upgrade Export Pack on the source environment (if it is not version 8.0.00), validating and correcting the data, exporting the data in the source environment, and then importing the data to the destination version. For more information on the steps for Control-M/Server Manual Upgrade, see Control-M/Server Manual Upgrade.
