Fail Back to Old Active Daemon | High Availability | Teradata Data Mover - Failing Back to the Old-Restored Active Daemon - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
wph1512683331242.ditamap
dita:ditavalPath
4101_UG_dm_1620.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
Once a failover has occurred, Data Mover does not automatically fail back to the old active daemon if it is restarted. To fail back to the old-restored active daemon after a failover has occurred, do the following:
  1. Log on to the old active daemon server and run dmcluster setmaster.
    This starts up the sync service associated with this daemon in active mode and the sync service on the old daemon server in standby mode. Once the sync service is started in standby mode on the old active daemon, it receives all the updates that occurred on the new active repository while the old active was down and catches up with the new active.
  2. Wait a few minutes to allow the old active to catch up with the new active, and then check the dmSync.log on the standby (old active) to determine when the old active has caught up with the new active.
  3. When the old active repository is in sync with the new active repository, set the old active back as the new active by running the dmcluster setmaster command on the old active.
  4. Run the dmcluster status command to verify the old active has been restored successfully.
    Trying to start the daemon on the old-restored active using the dmdaemon service script (/etc/init.d/dmdaemon start) causes the monitoring service to assume that the daemon has incorrectly started on the old active and shut it down.