Example of Active and Standby Component Status | Data Mover - Example: Checking the Status of the Active and Standby Components - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Data Mover
Release Number
17.10
Published
June 2021
Language
English (United States)
Last Update
2021-06-16
dita:mapPath
ivp1619423229496.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
B035-4102
lifecycle
previous
Product Category
Analytical Ecosystem
  1. View the newly configured cluster status:
    ./dmcluster status

    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.

    ------------------------------------------------------------------------
                            | LOCAL CLUSTER       |
    ------------------------------------------------------------------------
    | COMPONENT             |         HOST NAME   |         STATUS         |
    ------------------------------------------------------------------------
    | DM Daemon             |         DM1         |         RUNNING        |
    | ActiveMQ              |         DM1         |         RUNNING        |
    | DM Monitoring Service |         VP1         |         RUNNING        |
    | DM Sync Monitor       |         DM1         |         RUNNING        |
    | DM REST Service       |         DM1         |         RUNNING        |
    | DSC                   |         DM1         |         RUNNING        |
    | DSA REST              |         DM1         |         RUNNING        |
    | DM Agent              |         DM1         |         RUNNING        |
    | DM Agent              |         DM2         |         RUNNING        |
    | DM Agent              |         DM3         |         RUNNING        |
    ------------------------------------------------------------------------
                            | REMOTE CLUSTER      |
    ------------------------------------------------------------------------
    | COMPONENT             | HOST NAME           |              STATUS    |
    ------------------------------------------------------------------------
    | DM Daemon             |         DM2         |         STOPPED        |
    | ActiveMQ		|         DM2         |         STOPPED        |
    | DM Monitoring Service |         VP2         |         STOPPED        |
    | DM Sync Monitor       |         DM2         |         STOPPED        |
    | DM REST Service       |         DM2         |         STOPPED        |
    | DSC                   |         DM2         |         STOPPED        |
    | DSA REST              |         DM2         |         STOPPED        |
    | DM Agent              |         DM2         |         STOPPED        |
    | DM Agent              |         DM1         |         RUNNING        |
    | DM Agent              |         DM2         |         RUNNING        |
    | DM Agent              |         DM3         |         RUNNING        |
    ------------------------------------------------------------------------
    
    Cluster Mode: DM Cluster is in 'Active Mode'
    In the example output, only the Data Mover sync monitor on the active system is running to monitor synchronization progress from the designated-active to the designated-standby repositories. The sync monitor on the standby system is never used.
    If you configure Data Mover to use DSC on its host, the status for DSC and DSA REST is either RUNNING or STOPPED. If you configured Data Mover to use an external DSC, the status for DSC and DSA REST is EXTERNAL. See DSA Failover Configurations for more details.