Restoring hostname and configuration data during Disaster Recovery

This procedure describes how to restore the hostname and configuration data in the database during disaster recovery when moving to the stand-by Control-M/EM environment, which contains replicated data. Even though production and user data are up-to-date, the host and environment configuration data refers to the original environment, which is not in use at recovery time. This data contains the original hostname in various database tables, such as CONFIG_HA, and must be updated to the post installation values of the stand-by machine.

EXAMPLE: Before replication, the hostname value is ORIG_HOST in the original environment and STDBY_HOST in the stand-by environment. After replication, the hostname value in the stand-by host is ORIG_HOST and Control-M/EM cannot function. At recovery time, the hostname value in the stand-by environment must be reset to STDBY_HOST.

To restore the hostname and configuration data:

1. Stop all Control-M/EM processes in the secondary intallation environment and then in the primary and distributed installation environments.
2. From a command line type one of the following:
   • UNIX: em restore_host_config [-silent] -dr [[-old_host <old (Site A) host name>] or [-primary/secondary]] [[-password <dbo password>] or [-password_file [<file_path>]]]
   • Windows: restore_host_config [-silent] -dr [[-old_host <old (Site A) host name>] or [-primary/secondary]] [[-password <dbo password>] or [-password_file [<file_path>]]]

   NOTE:

   • <old (Site A) host name> is the host name of the disaster site. (Multiple distributed environments)
   • If the script cannot detect the old configuration in the template file, the -primary or -secondary flags can be used alternatively (instead of <-old_host>).
   • If the -silent flag is not specified and optional parameters are not defined in the command line, the script asks for the relevant input interactively.
   • The -old_host flag is not required in the following configurations:
     • A single Control-M/EM installation
     • Control-M/EM High Availability environment
     • Control-M/EM Distributed environment
   • The -old_host flag must be used when there are more than one additional environments (distributed) installed on several different computers.
   • The script must be executed on all different installations (primary/secondary/distributed) and always start with the active installation.
   • After you move Control-M/EM to the disaster recovery site and run the restore_host_config utility, you must copy the file <EM_HOME>/ini/fips/db_enc_key.txt from the main site to the disaster recovery site, into the same path.