The Control-M/Server high availability solution with a PostgreSQL database supports both a manual failover of the Control-M server along with PostgreSQL database replication. Control-M/Server is installed on the same host as the PostgreSQL database on the primary and on the secondary.
After the data replication is turned on and initialized successfully, the Control-M/Server database data is replicated, synchronously to the secondary database server. However, if there are network communication problems, the replication mode switches to Asynchronous. The data is replicated as well to a shared drive, which is used if the primary or secondary are temporarily unavailable (see High availability installation).
The secondary Configuration Agent monitors the primary to verify life check responses from Control-M/Server and the primary Configuration Agent is working, based on defined intervals. You can perform a manual failover at any time from the CCM if the manual failover option is enabled, based on the conditions described in Manual failover.
The following procedures describe how to start database replication, manually fail over to secondary, set secondary as primary, pause Control-M/Server, and manually fall back to primary:
For a description of configurable Control-M/Server high availability system parameters and to receive notifications about high availability events, see High Availability parameters.
Parent Topic |
See Also |