Failover implementation allows you to set up both a secondary Control-M/Server and a secondary database, in case of primary database and Control-M/Server disruption. Failover Control-M/Server implementation utilizes the same agents and remote hosts as the primary Control-M/Server installation.
NOTE: This option is not compatible with high availability.
The following procedures describe how to prepare and initialize a failover Control M-Server, what to do in the event of disruption, and how to stop the process:
After you have implemented database mirroring, Control-M keeps the primary and secondary databases synchronized. However, if you run utilities to update the Control-M database, you must perform database initialization again (see Primary and mirror database synchronization).
Parent Topic |