Restore Designated-Active Daemon | High Availability | Teradata Data Mover - 17.11 - Failing Back to the Designated-Active Daemon - Teradata Data Mover

Teradata® Data Mover User Guide

Teradata Data Mover
Release Number
Release Date
October 2021
Content Type
User Guide
Publication ID
English (United States)
After failover, Data Mover does not automatically fail back to the designated-active daemon. To fail back to the designated-active daemon after the root cause of the failover has been identified and fixed on the designated-active components, perform the following:
  1. On the designated-active daemon server, run the dmcluster switchback command and follow the prompts:
    Prompt Action
    Do you need to sync up the two repositories? [y or n] Enter y to sync up.

    Enter 1 to back up the active repository to the standby repository.

    Enter 2 to back up the standby repository to the active repository.

    [1 or 2]

    Provide the direction of sync up by entering either 1 or 2.
    This synchronizes the Data Mover repositories and re-enables the synchronization service. The Data Mover cluster is restored back to active mode and all the components and associated monitoring services are restarted on the designated-active server.
  2. Run dmcluster status to verify the designated-active daemon has restored successfully.
    It may take a few minutes for all services to transition. Run dmcluster status as needed until the results are as expected. Monitor progress in dmFailover.log on the currently active daemon and monitor servers.
    Do not start the daemon on the designated-active daemon server using the dmdaemon service script /etc/init.d/dmdaemon start. This causes the monitoring service to assume that the daemon has incorrectly started on the failed server and shuts it down.