Initializing failover on the primary and secondary computers

This procedure describes how to initialize failover on the primary and secondary computers.

When you move servers, jobs that are executing on the default local agent are not recognized by the other server. If there are jobs without an owner, both the primary and the secondary servers must have the same account name. To avoid this, define a specific hostid for a job.

NOTE: Do not start the failover (secondary) Control-M/Server while the primary Control-M/Server is running.

To initialize failover on the primary and secondary computers:

  1. Ensure that you have complied with the relevant Database parameters.
  2. On the host computer, shut down the failover (secondary) Configuration Agent and Control-M/Server by typing the following commands:
  3. On the failover (secondary) Control-M/Server database, verify that mirroring is disabled as follows:
    1. In the Control-M/Server, type the ctm_menu command.
    2. The Control-M Main Menu appears.
    3. Type the number for the Database Mirroring.
    4. The Database Mirroring Menu appears.
    5. From the Database Mirroring Menu, type the number for Check Mirroring Status.
  4. From the Database Mirroring Menu, type the number for Initialize Failover.
  5. On the host computer, shut down the primary Configuration Agent and Control-M/Server by typing the following commands:
  6. On the primary Control-M/Server do the following:
    1. Ensure that mirroring is disabled by repeating steps 3a to 3e.
    2. From the Database Mirroring Menu, type the number for Initialize Mirroring.
    3. Do one of the following:
      • To build a new database, type b
      • To copy an existing database, type c.
    4. At the prompts, type the relevant Mirroring parameters.
    5. If you need to install, type i and confirm.
    6. Perform any post-processing that the interactive utility instructs.
    7. To check that mirroring is enabled, repeat steps 3a to 3d and type the number for Check Mirroring Status.
  7. On the host computer, restart the primary Configuration Agent and Control-M/Server by entering the following commands:

    NOTE: Parameters in the config.dat file are not copied from the primary to secondary server or from the secondary to primary server. For example, if SMTP communication parameters are not updated on the secondary database, all domail actions fail.

Parent Topic

Failover implementation