restore_host_config
The Control-M/Server restore_host_config utility automates the recovery process that performs updates in the hostname configuration in the following situations:
-
Hostname data restore in Disaster Recovery sites.
-
Database server communication parameter property updates.
-
Removing the high availability secondary host data.
Restoring Control-M/Server Hostname and Configuration Data During Disaster Recovery
This procedure describes how to restore the Control-M/Server hostname and configuration data in the database during disaster recovery when moving to the stand-by environment.
Before You Begin
-
Shut down Control-M/Server and the Control-M/Server Configuration Agent.
Begin
-
Navigate to the following directory:
<Control-M/Server_Home>\ctm_server\scripts\
-
Run the following command:
restore_host_config -dr [-primary/secondary] [-remove_secondary y|n]
Reconfiguring the Database Server Connection Data
This procedure describes how to reconfigure the database server connection data in the configuration files and database, when the database server connection parameters are changed.
Before You Begin
-
Shut down Control-M/Server and the Control-M/Server Configuration Agent.
Begin
-
Navigate to the following directory:
<Control-M/Server_Home>\ctm_server\scripts\
-
Run the following command:
restore_host_config -reconf_db [-host <New_DB_Hostname>] [-port <New_DB_Port_Number>] [-dbname <New_DB_Schema_Name>] [-service <New_DB_Service_Name>] [-owner <New_DB__Owner_Name>] [[-password <DBO_Password>] [-pg_existing_server <y/n>]
-
You must use -pg_existing_server for PostgreSQL databases.
-
The y value determines that the database server cannot be administered by the installation (existing database mode).
-
The n value determines that the database server can be administered by the installation (dedicated database mode).
-
The source and destination database must from be the same database vendor.
-
-
Start the Control-M/Server Configuration Agent and Control-M/Server.
(UNIX only) The reconfigure steps make changes to the environment. For these changes to take effect, you must execute the start commands on a new shell.
Removing the Secondary High-Availability Installation Component Data from the Control-M/Server Database
This procedure describes how to remove the secondary (inactive) high availability installation component data from the Control-M/Server database.
Before You Begin
-
Shut down Control-M/Server and the Control-M/Server Configuration Agent.
Begin
-
Navigate to the following directory:
<Control-M/Server_home>\ctm_server\scripts\
-
Run the following command:
restore_host_config -remove_secondary