When an export file is created by the Control-M Enterprise Manager (EM ) UTIL utility on the primary High Availability platform, why can't this be imported on a Secondary or Disaster Recovery EM installation?

The Control-M Enterprise Manager version 9.0.00 database contains configuration details for Control-M High Availability (HA). If an export from a primary EM platform is imported into a secondary EM platform, this will bring in components to the secondary Control-M Configuration Manager (CCM) GUI which cannot be edited.  To prevent this, use the following procedure. 

Please note that all Backup and Restore procedures must be verified and properly tested before moving to a production environment.:

1. Export all the Primary Control-M EM data for backup purposes:
   em util -U -P -export -type all -file

2. Export only the CCM data from the Secondary Control-M EM:
    em util -U -P -export -type maint -file

3. Export all the Secondary Control-M EM data for backup purposes:
    em util -U -P -export -type all -file

4. Import the export file from Primary Control-M EM (ALL data from step #1) to the Secondary Control-M EM.  This will restore the Control-M EM Components  defined on the Secondary Control-M EM, to avoid having to delete and redefine the EM Components:
    em util -U -P -import -replace -type all -file <Full directory path and file name of export file>

5. Import the export file from Secondary Control-M EM (only CCM data from step #2) to the Secondary Control-M EM:
    em util -U -P -import -replace -type maint -file

6. Start Secondary Control-M EM