High availability compatibility

The following table describes how various Control-M components, products, and security settings work in a high availability configuration.

Component

Description

BMC Batch Impact Manager

High availability does not support BMC Batch Impact Manager on a dedicated separate server in a distributed environment.

Control-M Workload Archiving

High availability does not support Control-M Workload Archiving on a dedicated separate server.

Fix packs

If you install a fix pack on the primary, you must manually install it in on the secondary. A failover cannot occur if the fix packs on both hosts are not the same.

Cluster

Control-M high availability is supported in a clustered environment if the primary is installed on a dedicated PostgreSQL database and the Control-M components are not managed by the cluster manager

The failover mode is set to manual and it cannot be changed.

Control-M/EM sync files

The following files are synced to the secondary:

  • etc/site/resource/Defaults.rsc
  • etc/DirectoryServiceType.cfg
  • etc/resource/Defaults.rsc
  • TimeZone.dat
  • etc/ldap.conf
  • etc/log4j.selfservice
  • etc/log4j.wcm

    NOTE: If Advanced Email Configuration (SMTPS) is configured on the primary host, the following configuration files are not synced to the secondary because they contain an encryption key and password and must be configured manually :

  • etc/mail.properites
  • etc/mail_auth.properites
  • etc/aes.key

Control-M/Server sync files

The following files are synced to the secondary:

  • data/Config.dat
  • data/Time_Zone.dat
  • data/AGDEFS/AGDEFS
  • data/AGDEFS/AGUTILS_PERMIT
  • Data/AGENTS_ALIASES.txt
  • data/AGPERMIT_UTILS All files in directory
  • data/REMEDY/Remedy_Conf.xml
  • data/SSL/cert/Remedy,kbd

    NOTE: This file keeps the remedy server hostname, port, and username. These parameters are defined by the remedy_configure utility and are saved in this file. The encrypted file is saved in the remedy.kbd file.

    NOTE: If Advanced Email Configuration (SMTPS) is configured on the primary host, the following configuration files are not synced to the secondary because they contain an encryption key and password and must be configured manually :

  • data/mail.properites
  • data/mail_auth.properites
  • data/aes.key

Parent Topic

High availability installation