Purpose
The restore_daemon command allows you to restore the previously backed up repository and configuration files of the Data Mover daemon from a directory that you specify. The Data Mover daemon is stopped and then restarted when you run the restore_daemon command. Results of the Teradata ARC script that is used to perform the backup are written to a log file restore_script.output in the backup directory. The restore_daemon command can only be used if restoring a Data Mover repository that has the same hash algorithm as the Data Mover repository that was backed up by the backup_daemon command.
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.
- A path relative to the daemon_backup directory. This is a directory reserved for all backup snapshots.
- 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.
- security_password
- [Optional] Password for the super user or authorized Viewpoint user.
- security_password_encrypted
- [Optional] Encrypted password for the super user.
- 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.
Usage Notes
- 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.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <dmRestoreDaemon xmlns="http://schemas.teradata.com/dataMover/v2009http://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="