Control-M/EM and Control-M/Server high availability with Oracle/MSSQL

After you have installed a secondary Control-M (see High availability installation), the Control-M/EM or Control-M/Server Configuration Agent on the secondary host monitors the primary Control-M/EM or Control-M/Server based on defined intervals. If there is no response from the primary, you can fail over to the secondary in one of the following modes:

• Automatic failover: The secondary Configuration Agent automatically takes control and resumes production, when it detects that the primary Control-M/EM or Control-M/Server and its primary Configuration Agent has stopped unexpectedly.
• Manual failover: You can perform a manual failover at any time from the CCM if the manual failover option is enabled. After the failover is complete, the production runs on the secondary.

The following procedures describe how to manually fail over to a secondary host, pause Control-M/Server, fall back to a primary host, and set secondary to Primary:

• Failing over a Control-M/EM or Control-M/Server to secondary
• Pausing Control-M/Server
• Falling back Control-M/EM or Control-M/Server to primary
• Setting a Secondary to Primary

NOTE: If you attempt to manually start up components on the secondary when the primary is active, the components shut down automatically. This prevents both the primary and secondary from running components simultaneously.

For a description of configurable Control-M/EM high availability system parameters, see Maintenance parameters. For a description of configurable Control-M/Server high availability system parameters, see High Availability parameters. To receive notifications about Control-M/Server high availability events, see Control-M/Server general parameters. To receive notifications about Control-M/EM high availability events, see Control-M/EM general parameters.