How can a Control-M/Server with Oracle / MSSQL be failed-over and/or failed-back to/from a DR (Disaster Recovery) Site?
 

How to failover the Control-M/Server to the DR Site when using Oracle / MSSQL (for Postgres see article number 000157687 ):

1. Prerequisites for moving Site A (the original non-DR Control-M/Server) to Site B (the new DR Control-M/Server):

    (1.1). The database was replicated to the database used in Site B.
    (1.2). No Control-M/Server components are running on Site A.
    (1.3). No Control-M/Server components on Site B are running.
    (1.4). The Control-M/Server Version and Fix Pack levels are the same on both Site A and Site B.

2. Actions on the Control-M/Server account on Site B:

*Only perform the first step below if the hostname or port of the database needs to be changed (for example, when a dummy database with a different host or port was used for setting up the Control-M/Server on the DR Site).

    (2.1). If the Control-M/Server was configured to run on another database host or port , execute: restore_host_config -reconf_db (please see KA 000150657 for more information on this command)
    (2.2). Execute: restore_host_config -dr
    (2.3). Start the Control-M/Server configuration agent and then the Control-M/Server

Note 1: You must verify that the server was not started after the data base replication and before executing the “restore_host_config” command.
Note 2: If Site B was setup without a Control-M/Secondary server for High Availability running, the “restore_host_config -dr” command will remove its entry (please see KA 000155186 for more information on this).

How to failback the Control-M/Server from Site B (DR failover site) to Site A (original site):

3. Option 1: If the Control-M/Server installation(s) do not exist on Site A due to the cause of the DR failover:

    (3.1). Install a new Control-M/Server with the same FixPack Level as the Control-M/Server running on Site B.
    (3.2). Shut down the server on Site A.
    (3.3). Replicate the database from Site B to Site A.
    (3.4). Execute: restore_host_config -dr
    (3.5). Start the Control-M/Server configuration agent and then the Control-M/Server
    (3.6). (Optional) Install a Secondary Control-M/Server if you are using a Control-M/High Availability Environment.

4. Option 2: If the Site A Control-M/Server installation(s) exist:

    (4.1). Verify Control-M/Server is down on the primary account.
    (4.2). Replicate the database from Site B to Site A.
    (4.3). Execute: restore_host_config -dr
    (4.4). Start the Control-M/Server configuration agent and then the Control-M/Server
    (4.5). If you are using a Control-M/High Availability Environment, and Site B was setup without a Control-M/Secondary High Availability Server, the Secondary HA server will need to be uninstalled and then re-installed if the Control-M version was lower than 9.0.18.200 before the DR failover to Site B (please see KA 000159051 for more information on this).