The following table describes the main tasks in setting and implementing your Control-M Migration plan.
Tasks |
Description |
---|---|
Install the new environment |
Review the following sources to prepare your new environment so that you can work in parallel with the old environment while you prepare your installation. Note that migration of Control-M data is supported only when the source environment and the target environment both have the same version of Control-M (both major and minor version level, v.v.rr.mxx).
|
Migration |
Select the relevant workflow and schedule the migration for your site:
Agents can be migrated after the Control-M/Server is migrated to minimize application changes. NOTE: Along with the migration of Control-M/EM, plan for the migration of Control-M Workload Archiving data. Migration of archived job data might take a long time and might necessitate adjustments to retention parameters. For more information, see Migrating Control-M Workload Archiving. |
Test the migration process |
Export both the (old) EM and Control-M/Server data and import this into the new environments for testing before the Migration cutover date. The export and import process can be repeated as necessary. |
Troubleshooting |
For more information about troubleshooting your migration, see Troubleshooting Control-M Migration or contact Customer Support http://www.bmc.com/support. |
Verify new environment |
Verify that the migrated data exists in the new environment. |