-
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:
---------------------------------------------------------------------- | 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 | -------------------------------------------------------------------------
- Stop Data Mover monitoring services on VP1 and VP2 to avoid an automatic failover during the configuration process.
- Verify that no jobs are running on both the master (DM1) and slave (DM2) servers.
- Stop the Data Mover Sync Service on DM1.
- Stop the Data Mover Sync Service on DM2.
- Stop the Data Mover daemon on DM2.
- Start the Data Mover daemon on DM1.
-
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 you analyze the backup files after the command completes to ensure no errors occurred.
- Stop the Data Mover daemon on the master (DM1) server.
- Copy the backup directory on the master (DM1) server to the slave (DM2) server.
- Start the Data Mover daemon on the slave (DM2) server to run the restore command.
- Change the ownership of the backup files on the slave (DM2) server to dmuser.
- Grant 755 permissions to the backup files on the slave (DM2) server.
- Run the restore_daemon command to restore the master backup to the slave (DM2) repository. It is recommended that you analyze the backup files after the command completes to ensure the restore worked properly.
- Delete the working files on the Data Mover Sync Service for the master (DM1) and slave (DM2) servers. Deleting these working files ensures that the Sync Service does not contain old changes when it is restarted later in the failover configuration process.
- Stop the Data Mover daemon on the slave (DM2) server.