Control-M/Server Manual Migration

The following procedures describe how to perform a manual migration by exporting the old data from the old Control-M/Server, copying the file and importing it into the new Control-M/Server:

  1. Migrate Control-M/EM to the new environment, as described in Control-M/EM Migration.

  2. Configure the Control-M/Server migration parameters, including whether to prompt for the number of log days to include in the export, as described in Editing the Control-M/Server Migration Parameters.

  3. Exports the data from the old environment to a file, as described in Exporting the Control-M/Server Old Data.

  4. Import the data into the new environment, as described in Importing the Control-M/Server Exported Data to the New Environment.

  5. Rename the migrated Control-M/Server, connect the Gateway to the New Control-M/Server, and configure the old Agents to work in the new environment, cas described in Post-Control-M/Server Migration Procedures.

Editing the Control-M/Server Migration Parameters

This procedure describes how to review and edit the export/import parameters.

Begin

  1. Navigate to one of the following directories:

    • UNIX: <Server_Home>/ctm_server/upgrade/export/data

    • Windows: <server_home>\ctm_server\upgrade\export\data

  2. Review the Control-M/Server migration parameters in the migration.cfg file, as described in Control-M/Server Migration Parameters.

  3. Change the values as necessary, and save the migration.cfg file.

Control-M/Server Migration Parameters

The following table lists the Control-M/Server migration parameters, which are defined in the migration.cfg file.

Parameter

Description

ASK_LOG_DAYS

 

 

Determines whether the user is prompted for the number of log days to export during the Control-M/Server migration process, as follows:

  • Yes

  • No

Default: No

LOG_DEPTH

 

 

Determines the number of log days that the user exports during the Control-M/Server migration process.

Valid Values: 0–100

Default: 100

LONG_TIMEOUT

 

 

Determines the number of seconds to wait for jobs that are submitted to the old environment during the Control-M/Server Automatic migration.

Valid Values: Any positive number. BMC recommends 180 or higher.

Default: 180

SHORT_TIMEOUT

 

 

Determines the number of seconds to wait for jobs that are submitted to the old environment during the Control-M/Server Automatic migration.

Valid Values: Any positive number. BMC recommends 60 or higher.

Default: 60

Exporting the Control-M/Server Old Data

This procedure describes how to export the Control-M/Server old data to a file that can be then imported to the new environment.

For environments that have a large set of data, you can minimize downtime by performing the export in an incremental manner. Begin with one or more exports of the static data (job definitions and historical data), without the need to shut down Control-M Server processes in the source environment. When you are ready for the final export, shut down Control-M Server processes in the source environment and export the active data.

Before You Begin

Begin

  1. Run one of the following migration commands:

    • UNIX: <server_home>/ctm_server/upgrade/export/upgrade

    • Windows: <server_home>\ctm_server\upgrade\export\upgrade.bat

      The Manual Upgrade Menu for Control-M/Server appears.

  2. Enter 1 (Export - Exports historical, definitions, and active data to a file).

    The export process checks for the existence of files of static data (job definitions and historical data) from a previous export. If you are notified that you have already exported log (historical) and definition data, continue with the next step. Otherwise, skip to step 4.

  3. If you are notified that you have already exported log (historical) and definition data, perform the following actions:

    1. Press ENTER.

    2. In the Export Active Data Menu, choose between a Full Environment export (which includes all data), option 1, or an Active EnvironmentClosed The workflows of jobs and SMART folders that are scheduled to execute on the current Control-M day. export (which includes only active data), option 2.

      Option 2 enables you to complete the export of the remaining data in an incremental export process. However, ensure that no changes were made in the job definitions since the previous export.

    3. If you chose an Active Environment export (option 2), skip to step 6, where you will shut down Control-M Server processes.

  4. For the migration of job definitions, you are prompted to add the new Control-M/Server host to the Authorized Servers list, so that jobs can run in the new environment. Enter Yes.

    This option only appears if the old Control-M/Server is up and running when the export is performed. This may take some time.

  5. For the migration of historical data, you are prompted for the maximum number of log days to export. Do one of the following:

    • If you do not want to migrate historical data at all, enter 0.

    • For all historical data, enter ALL.

    • For a specific number of days of historical data, enter a number between 1 and 100.

      You are prompted for this setting only if ASK_LOG_DAYS is set to Yes in the migration.cfg file. If ASK_LOG_DAYS is set to No, you can still control this number using the LOG_DEPTH parameter in the migration.cfg file. For more information about these migration parameters, see Control-M/Server Migration.

  6. When asked if you want to shut down Control-M Server processes in the source environment to enable the migration of active data, enter one of the following responses:

    • To enable the inclusion of active data in the migration, enter YES.

    • If you are migrating only static data (historical data and job definitions), without active data, enter NO.

      If you do not shut down the production environment, the export does not include the Active Job runtime environment. Such an export can be used to test the export and import process or in an incremental export process. Eventually, on the day of the migration when you can shut down the old Control-M/Server, you can re-run the export to include the Active Job runtime environment.

  7. Follow the remaining on-screen instructions until the export is complete.

    The exported files are saved in the following location:

    • UNIX: <Server_Home>/ctm_server/upgrade/export/output/<Export_Type>_<Timestamp>.tar

    • Windows:<Server_Home>\ctm_server\upgrade\export\output\<Export_Type>_<Timestamp>.tar

      where <Export_Type> represents one of the following strings:

    • LDR: Full export of Logs (Historical data), Definitions data, Runtime (Active data).

    • LD: Export of Logs (Historical data) and Definitions data only.

    • R: Active data export (Runtime), continued from a process that was stopped after historical and definition data were exported.

  8. Copy the exported file to the new Control-M environment.

    Files exported via FTP, must be transmitted in binary mode.

    You are now ready to import the export file to the new environment, as described in Importing the Control-M/Server Exported Data to the New Environment.

Importing the Control-M/Server Exported Data to the New Environment

This procedure describes how to import the Control-M/Server exported data to the new Control-M environment.

Before You Begin:

  • Shut down the Control-M/Server and Control-M/Server Configuration Agent.

  • Verify that you have copied the exported *.tar file to the new environment at the end of the export process, as described in Exporting the Control-M/Server Old Data.

Begin

  1. Run one of the following migration commands:

    • UNIX: <Server_Home>/ctm_server/upgrade/import/upgrade

    • Windows: <Server_Home>\ctm_server\upgrade\import\upgrade.bat

      The Control-M/Server Upgrade Menu appears.

  2. Enter 2) Manual Upgrade.

    The Upgrade Manual Upgrade Menu - Control-M/Server menu appears.

  3. Enter 1) Import.

  4. Follow the prompts until the import is complete.

    The import process converts and imports the data into the new environment.

  5. To load the database with all the statistics that are required for performance, run the ctmdbopt utility.