Example: Synchronizing the Master and Slave Repositories - Teradata Data Mover

Teradata Data Mover Installation, Configuration, and Upgrade Guide for Customers
Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
fsa1467305282096.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4102
Product Category
Analytical Ecosystem
  1. Run /opt/teradata/client/nn.nn/datamover/failover/dmcluster status on either DM1 or DM2 to view current configuration and active components.
    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:
    ----------------------------------------------------------------------
|                         LOCAL CLUSTER                                 | 
-------------------------------------------------------------------------
| COMPONENT                | HOST NAME            | STATUS              |
-------------------------------------------------------------------------
| DM Daemon                | localhost            | STOPPED    	     |
| ActiveMQ                 | localhost			| STOPPED             |
| DM Monitoring Service    | localhost			| STOPPED             |
| DM Sync Service          | localhost			| STOPPED             |
| DM Agent                 | localhost			| STOPPED			 |
|------------------------------------------------------------------------
|                        REMOTE CLUSTER                                 | 
-------------------------------------------------------------------------
| COMPONENT                | HOST NAME              | STATUS            |
-------------------------------------------------------------------------
| DM Daemon                | localhost            | STOPPED             |
| ActiveMQ                 | localhost            | STOPPED			 |
| DM Monitoring Service    | localhost			| STOPPED             |
| DM Sync Service          | localhost			| STOPPED             |
| DM Agent                 | localhost			| STOPPED			 |
-------------------------------------------------------------------------
  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 master (DM1) and slave (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 master (DM1) repository.
    Running the backup command momentarily shuts down the master (DM1) daemon. It is recommended that the backup files are analyzed after the completion of the command to ensure no errors occurred.
  9. Stop the Data Mover daemon on the master (DM1) server.
  10. Copy the backup directory on the master (DM1) server to the slave (DM2) server.
  11. Start the Data Mover daemon on the slave (DM2) server in order to run the restore command.
  12. Change the ownership of the backup files on the slave (DM2) server to dmuser.
  13. Grant 755 permissions t the backup files on the slave (DM2) server.
  14. Run the restore_daemon command to restore the master backup to the slave (DM2) repository. It is recommended the backup files are analyzed after the command completes to make sure the restore worked properly.
  15. Delete the working files on the Data Mover Sync Service for the master (DM1) and slave (DM2) servers. It is important to delete these working files to ensure that the Sync Service does not contain old changes when it is restarted later in the failover configuration process.
  16. Stop the Data Mover daemon on the slave (DM2) server.