How to migrate Control-M/Enterprise Manager or Control-M/Server to a new machine, when upgrading OS level or upgrading the physical machine.
|
There are few options when moving Control-M/Enterprise Manager or Control-M/Server from one machine to another and keeping the same Control-M release. This knowledge article deals specifically with the following common: when upgrading platform OS level
when upgrading hardware Option A: Using Control-M HA functionality
Works best with External Database
All external databases are supported with this option
BMC provided PG will also work with this option for Control-M/Server but not for EM. EM distributed instances will not work with this option, such as Archiving installation. HA configuration will work with this option Step 1: Perform Control-M HA secondary installation on the new hardware. Even if you have an HA environment when a second "secondary" installation is performed, the new installation will overwrite the existing secondary environment. Prior to starting the secondary install make sure that all components are down on the old Secondary instance including configuration agent and micro-services.
This procedure is performed while the Primary environment is up and running. No "downtime" will be needed during this operation. When dedicated PG is used then a shared drive is required to build and HA. You must initiate PG replication in order to sync the two databases before proceeding. Step 2: Shutdown Primary
Step 3: Set the new secondary installation as the primary. Using CCM High Availability -> Set as Primary option
Step 4: Complete the HA configuration
if originally you started with HA then at this step you will have two old machines with original Primary and Secondary fully down
What is left is to complete building the Secondary on the second new hardware. The first new hardware now contains a Primary Control-M component as completed in step 1. At this time on the new hardware install a Secondary Control-M The advantages of using this Option are several
- Minimum downtime
- Low risk. No databases are built with this option. Existing DB is reused - No moving of data. No export/import is required during migration. Option B: Using Migration tool kit Follow documentation in the migration guide.
The Advantages for using option B is: support for all databases
support for all configurations support for migrating from one DB vendor to a different DB vendor The Disadvantages for Option B
Downtime for migrating the data.
When external database is present then the original database instance is not reused rather a new database is build and the data is exported from the old instances and imported to the new instance. Using migration tool kit supports all environments and databases |