Restart Services as primary | High Availability | Teradata Data Mover - Restarting Services - 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
  1. From the primary or secondary daemon server, run dmcluster status to verify the cluster state.
  2. Log on to the currently primary daemon server and run the following:
    dmcluster setmaster

    The Data Mover components are restarted on the currently primary server and stopped on the standby server. Sync monitor starts when the Data Mover cluster is in primary mode.

    You can use the setmaster command any number of times without modifying the failover.properties file on the server.

  3. From the primary daemon server, run dmcluster status to verify all services are running as expected.
    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.
    If the Data Mover cluster is in standby mode, a failover has occurred. When the cluster is in standby mode, you can only restart services on the secondary daemon server. For more information about switching the Data Mover cluster back to primary mode after a failover, see Switching Back to the Primary Daemon