Restore Primary Daemon | High Availability | Teradata Data Mover - Switching Back to the Primary Daemon - Teradata Data Mover

Teradata® Data Mover User Guide - 20.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
Product Category
Analytical Ecosystem
After failover, Data Mover does not automatically switch back to the primary daemon. To switch back to the primary daemon after the root cause of the failover has been identified and fixed on the primary components, perform the following:
  1. On the primary 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 primary repository (DM1) to the secondary repository (DM2).

    Enter 2 to back up the secondary repository (DM2) to the primary repository (DM1).

    [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 primary server.
  2. Run dmcluster status to verify the primary 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 primary 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.