restore_daemon | Commands | Teradata Data Mover - restore_daemon - Teradata Data Mover

Teradata® Data Mover User Guide - 20.01
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
Product Category
Analytical Ecosystem

Purpose

The restore_daemon command allows you to restore the previously backed up daemon configuration from a repository in to a configuration file.

As of Data Mover 17.05, the restore_daemon command uses the repository_backup.sh scripts located in the /opt/teradata/datamover/daemon/nn.nn directory to restore daemon configurations from the repository. The script uses the Postgres pg_restore command for restoring.
The repository_backup.sh script can be used independently for restoring the daemon. Avoid restoring the daemon while jobs are running.
Where nn.nn in the path refers to the version numbers of Data Mover.

Syntax

Data Mover XML Schemas

Parameters

See Parameter Order.

backup_target_dir
The directory from which Data Mover restores the backup files. The location you specify can be:
  • A path relative to the daemon_backup directory. This is a directory reserved for all backup snapshots.

    If the path is relative, enter the name of the directory that contains the backup files. Never use an initial slash when specifying a relative path.

  • An absolute path. This is any location on the system for which dm_user has write privilege. restore_daemon runs under the dm_user account.

    If the path is absolute, enter the full path to the backup files. Always use an initial slash when specifying an absolute path.

Example: repos_bu_001 is a relative path.
Example: /home/myhome/repos_bu001 is an absolute path.
dm.rest.endpoint
[Optional] Enter a Data Mover REST server URL to overwrite the default value specified in the commandline.properties file in order to connect to a different REST server (and therefore a different daemon) at runtime.
https://dm-server1:1443/datamover
security_password
[Optional] Password for the super user or authorized Viewpoint user.
Example: 53cUr17y
Required if security management is enabled on the Data Mover daemon. Not a valid parameter if -security_password_encrypted is also specified.
security_password_encrypted
[Optional] Encrypted password for the super user.
Example: 052c7aabd14c7770141ac3c0137ab98ae0d3f0f7cddf588981206b010c0c1b2f
Required if security management is enabled on the Data Mover daemon. Not a valid parameter if -security_password is also specified.
security_username
[Optional] User ID of the super user or authorized Viewpoint user. The user ID of the super user is dmcl_admin and cannot be changed.
Required if security management is enabled on the Data Mover daemon.

Usage Notes

The following scenarios result in an error:
  • A job is running when you execute the restore_daemon command
  • You do not specify a directory where the backup files are stored
  • You specify an absolute path, but dm_user does not have write privilege for the path
  • You specify a relative or absolute path that does not exist
  • The Data Mover repository being restored does not have the same hash algorithm as the Data Mover repository that was backed up by the backup_daemon command

XML File Example

To use an XML file such as parameters.xml with the restore_daemon command to restore previously backed up repository and configuration files of the Data Mover daemon, type datamove restore_daemon -f parameters.xml.

In the following example, parameters.xml specifies repos_bu_001 as the directory under daemon_backup relative to the install location for the Data Mover daemon on your system where the previous backup was written. 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 <dmRestoreDaemon xmlns="http://schemas.teradata.com/dataMover/v2009//
  http://schemas.teradata.com/unity/datamover.xsd">
   <backup_target_dir>repos_bu_001</backup_target_dir>
 </dmRestoreDaemon>"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="