Failover Event Simulation and Cluster Restore | Teradata Data Mover - Simulating a Failover Event and Restoring Cluster - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers - 20.03
Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Lake
Product
Teradata Data Mover
Release Number
20.03
Published
July 2024
ft:locale
en-US
ft:lastEdition
2024-07-17
dita:mapPath
vuu1713418923137.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
pqq1467243714524
Product Category
Analytical Ecosystem

Do the following to simulate a failover event and then restore the cluster to the original configuration:

    Simulating a Failover Event

  1. View the current cluster status: ./dmcluster status
  2. On the primary system, shut down the Data Mover repository: /etc/init.d/postgresql stop
  3. Check the cluster status to verify the initiation of failover: ./dmcluster status
    The failover monitor recognizes that the Data Mover repository on the primary system is down. However, the failover monitor makes retry attempts to check the repository status before initiating failover. So the process can take time.
    Stopping the Data Mover services, such as the daemon or agent, does not result in a failover event. The failover monitor instead detects that those services are down and attempts to restart the services before initiating a failover.

    4. Restoring the Cluster to the Original Configuration:

  4. On the primary system, restart the Data Mover repository: /etc/init.d/postgresql stop
  5. On the primary system, run the command: ./dmcluster switchback
  6. Verify the restoration of the original cluster configuration: ./dmcluster status