Synchronize the Active and Standby Repositories | Example | Teradata Data Mover - 17.00 - Example: Synchronizing the Active and Standby Repositories - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
17.00
Release Date
November 30, 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-4102-030K
Language
English (United States)
  1. View current configuration and active components on DM1 or DM2:
    /opt/teradata/client/nn.nn/datamover/failover/dmcluster status
    Where nn.nn in the path refers to the major and minor version numbers of Data Mover.
    Example output when environment has not been configured previously:
    ERROR: The following error may indicate incorrect configuration of high availability in Data Mover. Check the Data Mover Customer Installation guide for high availability setup
     Cause: java.lang.Exception: The following properties are incorrect:
            The hostname/IP address for local daemon is set to localhost in the properties file
            The hostname/IP address for remote daemon is set to localhost in the properties file
            The hostname/IP address for local monitor is set to localhost in the properties file
            The hostname/IP address for remote monitor is set to localhost in the properties file
            The hostname/IP address for local repository is set to localhost in the properties file
            The hostname/IP address for remote repository is set to localhost in the properties file
            The hostname/IP address for local agent is set to localhost in the properties file
            The hostname/IP address for remote agent is set to localhost in the properties file
    Error running status
  2. Stop Data Mover monitoring services on VP1 and VP2 to avoid an automatic failover during the configuration process.
  3. Verify that no jobs are running on both the active (DM1) and standby (DM2) servers.
  4. Stop the Data Mover Sync service on DM1.
  5. Stop the Data Mover Sync service on DM2.
  6. Stop the Data Mover daemon on DM2.
  7. Start the Data Mover daemon on DM1.
  8. Run the backup_daemon command to create a backup of the active (DM1) repository.
    Running the backup command momentarily shuts down the active (DM1) daemon. Teradata recommends that you analyze the backup files after the command completes to make sure no errors occurred.
  9. Stop the Data Mover daemon on the active (DM1) server.
  10. Copy the backup directory on the active (DM1) server to the standby (DM2) server.
  11. Start the Data Mover daemon on the standby (DM2) server to run the restore command.
  12. Change the ownership of the backup files on the standby (DM2) server to dmuser.
  13. Grant 755 permissions to the backup files on the standby (DM2) server.
  14. Run the restore_daemon command to restore the active backup to the standby (DM2) repository.
    Teradata recommends that you analyze the backup files after the command completes to make sure the restore worked properly.
  15. Delete the working files on the Data Mover Sync service for the active (DM1) and standby (DM2) servers.
    Deleting these working files makes sure that the Sync service does not contain old changes when the service restarted later during the failover configuration process.
  16. Stop the Data Mover daemon and ActiveMQ on the standby (DM2) server.