Automatic failover

An automatic failover occurs when the secondary Configuration Agent detects that the primary Control-M/EM or Control-M/Server and its Configuration Agent is not alive and the production on the primary has stopped unexpectedly. This can occur due to a hardware malfunction, machine crash, a network card stops responding, or if all components are down.

Control-M/EM: To ensure that the primary Control-M/EM is not functioning, the following conditions must be met before an automatic failover occurs (default: 60 seconds):

• There are no life check responses from all Control-M/EM components and the primary Configuration Agent (see Maintenance parameters).

EXAMPLE: If HA_LIFECHECK_TRIES is set to 3, and each Check Interval for each Control-M/EM component is set to 20, an automatic failover starts after 60 seconds. The production on the secondary is ready after all the components are up and this time is determined by the operating system, number of Control-M/Servers, and number of jobs.

• There are no transactions recorded in the database from all Control-M/EM components and its primary Configuration Agent.

EXAMPLE: If all components are down and the Configuration Agent is up, an automatic failover does not occur.

• The Oracle, MSSQL, or external PostgreSQL database is up.

Control-M/Server: To ensure that the primary Control-M/Server is not functioning, the following conditions must be met before an automatic failover occurs (default: 60 seconds):

• There is no life check response from the primary Configuration Agent (see High Availability parameters).

  EXAMPLE: If HA_TIME_BETWEEN_LIFECHECKS is set to 15 (default) and HA_LIFE_CHECK_TIMEOUT is set to 5 (default), the primary Configuration Agent is considered not functioning after 20 seconds.

• There are no transactions recorded in the database from all running Control-M/Server processes and its primary Configuration Agent.

  EXAMPLE: If HA_LIFE_CHECK_TRIES is set to 3 (default), HA_TIME_BETWEEN_LIFECHECKS is set to 15 (default) and HA_LIFE_CHECK_TIMEOUT is set to 5 (default), processes are considered not writing to the database after 40 seconds ( (3-1) * (15 +5) )

  EXAMPLE: If all Control-M/Server processes are down but the Configuration Agent is up, an automatic failover does not occur.

• The Oracle, MSSQL, or external PostgreSQL database is up.