Purpose
The backup_daemon command allows you to back up the repository and configuration files of the Data Mover daemon to a directory that you can optionally specify. You then can restore the backed up files with the restore_daemon command. The Data Mover daemon is stopped and then restarted when you run either command. Results of the Teradata ARC script that is used to perform the backup are written to a log file backup_script.output in the backup directory.
Syntax
Parameters
See Parameter Order.
- backup_target_dir
- [Optional] The directory where
- broker.port
- [Optional] You may enter a broker port to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
- broker.url
- [Optional] You may enter a broker URL to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ 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
If you enter repos_bu001 as the relative path, Data Mover writes the backup files to /var/opt/teradata/datamover/daemon_backup/repos_bu001. Never use an initial slash when specifying a relative path.
If you enter /home/myhome/repos_bu001 as the absolute path and if dm_user has write privilege for this path, Data Mover writes the backup files to /home/myhome/repos_bu001. Always use an initial slash when specifying an absolute path.
If you do not specify a directory for the backup, Data Mover creates a directory in the format backup_YYYY-MM-DD_HH.mm.ss under daemon_backup. This format is composed of the word backup, followed by the timestamp of the backup. A backup that occurs for example at 2am on December 3, 2012 is written to the directory backup_2012-12-03_02.00.00.
- A job is running when you execute the backup_daemon command
- You specify an absolute path, but dm_user does not have write privilege for the path
XML File Examples
For the backup_daemon command, type datamove backup_daemon -f parameters.xml.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <dmBackupDaemon xmlns="http://schemas.teradata.com/dataMover/v2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.teradata.com/unity/datamover.xsd"> </dmBackupDaemon>If the backup is successful, the name of the directory that was created for the backup is written to standard output.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <dmBackupDaemon xmlns="http://schemas.teradata.com/dataMover/v2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.teradata.com/unity/datamover.xsd"> <backup_target_dir>repos_bu_001</backup_target_dir> </dmBackupDaemon>If the backup is successful, the name of the directory repos_bu_001 is written to standard output.