Verify the Cluster Status | Teradata Data Mover - Verify Cluster Status - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Published
October 2021
Language
English (United States)
Last Update
2021-10-14
dita:mapPath
cai1626458602965.ditamap
dita:ditavalPath
cai1626458602965.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Use the dmcluster status command to check the status of a failover cluster.

Active Mode

When Data Mover services run on the designated-active servers and are monitored by the designated-active monitor, the cluster is in active mode. When checking the status of an active cluster with the dmcluster status command, the following displays:
------------------------------------------------------------------------
                        | 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'

When the designated-active Data Mover sync monitor is running and monitoring the synchronization progress from the active to standby repository, the standby Data Mover sync monitor is not in use.

Standby Mode

When failover occurs, Data Mover services run on the designated-standby server and monitored by the standby monitor, the cluster is in standby mode. When checking the status of a standby cluster with the dmcluster status command, the following displays:
------------------------------------------------------------------------
                        | LOCAL CLUSTER       |
------------------------------------------------------------------------
| COMPONENT             |         HOST NAME   |         STATUS         |
------------------------------------------------------------------------
| DM Daemon             |         DM1         |         STOPPED        |
| ActiveMQ              |         DM1         |         STOPPED        |
| DM Monitoring Service |         VP1         |         STOPPED        |
| DM Sync Monitor       |         DM1         |         STOPPED        |
| DM REST Service       |         DM1         |         STOPPED        |
| DSC                   |         DM1         |         STOPPED        |
| DSA REST              |         DM1         |         STOPPED        |
| DM Agent              |         DM1         |         RUNNING        |
| DM Agent              |         DM2         |         RUNNING        |
| DM Agent              |         DM3         |         RUNNING        |
------------------------------------------------------------------------
                        | REMOTE CLUSTER      |
------------------------------------------------------------------------
| COMPONENT             | HOST NAME           |              STATUS    |
------------------------------------------------------------------------
| DM Daemon             |         DM2         |         RUNNING        |
| ActiveMQ		|         DM2         |         RUNNING        |
| DM Monitoring Service |         VP2         |         RUNNING        |
| DM Sync Monitor       |         DM2         |         STOPPED        |
| DM REST Service       |         DM2         |         RUNNING        |
| DSC                   |         DM2         |         RUNNING        |
| DSA REST              |         DM2         |         RUNNING        |
| DM Agent              |         DM1         |         RUNNING        |
| DM Agent              |         DM2         |         RUNNING        |
| DM Agent              |         DM3         |         RUNNING        |
------------------------------------------------------------------------

Cluster Mode: DM Cluster is in 'Standby Mode'.
WARNING: Data Mover will not do failover in 'Standby Mode'. Please run 'dmcluster switchback' on primary DM server to go back to 'Active Mode' as soon as possible.

The Data Mover cluster runs in a downgraded state when in standby more. After failover, the sync monitor stops running and the synchronization service from the active to standby repository is disabled. Since an additional failover cannot occur, it is important to switch the cluster back to active mode as soon as possible. For instructions on switching from standby back to active mode, see Failing Back to the Designated-Active Daemon.