Example of the Control-M/Server Migration Steps

1. Pre-installation tasks a. Review the Control-M/Server Migration Guide b. Use this Example Steps to create a step by step plan c. Select the migration cutover date. d. Open a new case with BMC support regarding the migration. Include AMIGO and the migration date in the subject. 2. Installation of New Software a. Install the new Control-M/Server and the latest fixpack b. Install the latest Migration toolkit on the <current> Control-M/Server (the ControlM Server being migrated). c. Copy any customized scripts to the new Control-M server. 3. Testing a. Run the Migration Toolkit Validation report on the <current> Control-M/Server until there are no errors. b. If possible, schedule a time to stop the <current> ControlM/Server and run the migration export. This will allow for testing with your environment data. c. Run the migration import into the <new> Control-M/Server(if an export was taken). If not, create sample jobs in the <new> Control-M sever to test with. d. Check the <current> ControlM Server config.dat file to see if there are any customized parameters that need to be manually migrated. e. Test the SMTP configuration (if its being used). 4. Training a. Review the Control-M/Server Release Notes. b. Practice the new features in the <new> Control-M/Server. 5. Create a back out plan a. Determine outage window and back out point b. Create a back out plan 6. Actions just prior to migration to the new environment a. Add new Control-M/Server to agents authorization list b. Synchronize all EM and ControlM scheduling tables. You can use the Control-M Desktop Scheduling Table manager to upload all of the scheduling tables to be sure they are in sync. c. Notify users regarding the outage d. Verify that you have the DBA/DBO password for the migration export/import e. Re-run Validation report f. Perform any needed backups of <current> production environment g. Modify resources to prevent new jobs from starting. h. Shutdown the gateway connected to the Control-M/Server being migrated.

7. Control-M/Server cutover a. Shutdown <current> Control-M/Server b. Run the Migration Export utility to export the <current> production data c. Copy exported migration file to the new Control-M server d. Run Migration Toolkit Import utility to import data into the new Control-M server e. Using ctm_menu, verify the EM parameters and the default Agent parameters are set correctly. Especially note the Agents Default Protocol Value ensure that this is correct for you new environment. f. Run the migrate_dc utility to convert the <previous> ControlM Server definition and job format to the new Control-M server. Only run this command for the Control-M servers that have been migrated. This command is run on the EM side and is documented in the migration guide. g. Using CCM, verify/modify the Control-M/Server and gateway parameters. 8. Verify new environment (example of optional tests) a. Verify gateway is connected b. Start EM GUI client, verify jobs. c. Order new test table/jobs d. Using ControlM Desktop, Load a job, make changes, write job back to EM, upload to ControlM Server and order from the EM GUI. e. Verify all resources have been refreshed and new ones are being added/deleted properly f. Access sysout and log files for a job g. Perform normal AJF actions: hold, update, free, h. Verify global condition definitions i. Verify security: view or add a user j. Verify that the User Daily values are set correctly. 9. Migration Complete

Helpful Hints learned from previous migrations: 1. Verify that the agent Communication Protocol Version (ctm_menu -> 6 - Parameter Customization) is configured to match the corresponding version of the agent. By default, the ControlM Server will set the Communication Protocol Version to the version of the new ControlM Server. 2. The ControlM Server SMTP parameters are not migrated over so you have to configure this after the migration. 3. Remove any NODES that are obsolete or invalid before migrating to the new version. 4. Run the ctmdbcount utility to check to see if there are unusually high counts for any specific database tables.

5. Check to see if the AUTOEDIT VARIABLE %%LIBMEMSYM is being used. This variable will point to a file that has to manually be moved. This is a customer customized list of AUTOEDITS. 6. Verify that the size of the new database is as big or bigger than the previous version database. 7. If the datacenter name is being changed, verify that the Global Conditions prefix is also updated for conditions that are passed between datacenters. 8. Verify the performance of the new environment using the following tools in the Control-M Server toolbox which is installed in the directory <Control-M/Server Home>/ctm_server/toolbox. Run the command toolbox, then run the commands: a. 2 - Environment tests -> 1 - IO check b. 3 - Control-M tests -> 1 - Job ordering 9. If the new and old Control-M/Server will be running concurrently or in parallel for some period of time, the orderno (LAST_ISN) will be different between the 2 running environments. If the switch is made to a ControlM Server with a lower orderno (LAST_ISN) using the same agents as the other ControlM Server, then there could be a problem if the SYSOUT for this orderno is on the Agent.