Migrating Control-M Workload Archiving

This procedure describes how to migrate Control-M Workload Archiving data from a source archive database on a Control-M/EM Distributed computer to a target archive database. Migration of Workload Archiving Migration data is supported from a PostgreSQL database to another PostgreSQL database or from an Oracle database to another Oracle database.

The migration may take several hours or even days, depending on the amount of data and the network latency between the source and the target database. If migration fails in the middle of the process, it can be restarted from the point of failure.

NOTE: Control-M/EM may finish migrating and be up and running well before Control-M Workload Archiving is. To ensure that the archiving process does not miss job log and job output data, you can adjust retention parameters as described in Configuring retention parameters to prevent loss of archive data.

Before you begin

• Ensure that you have successfully completed Control-M Workload Archiving installation.
• Verify that there are no job definitions or Archive policies in the new environment. The utility overwrites all previous data.
• Ensure that Control-M Workload Archiving is down in both the source environment and the target environment. Through the CCM, set the desired state of the Workload Archiving Server to Down. In addition, ensure that both the source database and target database are up.

To migrate Control-M Workload Archiving:

1. In the new Distributed environment, navigate to the following directory:

   <Control-M/EM home dir>\archive\CopyDataUtil

2. Run the following script:

   run_archive_migration

3. Follow the on-screen instructions or type the following command:

   -host <source db host> -port <source db port> -username <source db username> -password <source db password> -name <source db name>

   The script migrates the data from the old environment to the new environment. For a full list, see Workload Archiving migration parameters.

   NOTE: If the Workload Archiving server was up on the new computer before migration, it is restarted automatically. If not, you can restart the server when the following message appears:

   Starting migration from source's DB to target's DB

4. Activate all the required rules, and click Save, as described in Defining Workload Archiving policies in the Control-M Administration Guide.