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:
|
Control-M/Server sync files |
The following files are synced to the secondary:
|
Parent Topic |