Example: Configuring the Cluster and Starting the Monitoring Service - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
pgy1512683352051.ditamap
dita:ditavalPath
DM_16_20_08_ICUCust_AsterIncluded.ditaval
dita:id
B035-4102
lifecycle
previous
Product Category
Analytical Ecosystem
The dmcluster config command sets up SSH connections between the DM1, DM2, DM3, VP1, and VP2 servers. These connections are used by the Data Mover monitoring service to monitor the active Data Mover components and initiate a failover if any of the active components stop working.
  1. Enter the following changes to the failover.properties file on the active (DM1) server:
    • local.daemon.host=DM1
    • remote.daemon.host=DM2
    • local.monitor.host=VP1
    • remote.monitor.host=VP2
    • local.repository.host=DM1
    • remote.repository.host=DM2
    • local.agents.host=DM1, DM2, DM3
    • remote.agents.host=DM1, DM2, DM3
  2. Run ./dmcluster config as root and follow the following prompts:
    Prompt Action
    Please enter the Root Password for the server running Master Repository: Provide the root Linux password for DM1.
    Please enter the Root Password for the server running Slave Repository: Provide the root Linux password for DM2.
    Please enter the password for root@DM1(MASTER DAEMON): Provide the root Linux password for DM1.
    Please enter the password for root@DM2(SLAVE DAEMON): Provide the root Linux password for DM2.
    Please enter the password for root@VP1(MASTER MONITOR): Provide the root Linux password for VP1.
    Please enter the password for root@VP2(SLAVE MONITOR): Provide the root Linux password for VP1.
    Please enter the password for root@DM3(Master Agent(s)): Provide the root Linux password for DM3.