export_job_metadata - BAR - Data Stream Architecture - Use the export_job_metadata command to export metadata of a job (job definition, save sets, and targets) based on the requested backup version. Learn more here.

Teradata® DSA User Guide

Product
BAR
Data Stream Architecture
Release Number
16.20
Published
November 2019
Language
English (United States)
Last Update
2019-11-27
dita:mapPath
xfr1514490991957.ditamap
dita:ditavalPath
3150_DSA_UG_1650-working-RR-new.ditaval
dita:id
B035-3150
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities

Purpose

The export_job_metadata command exports metadata of a job (job definition, save sets, and targets) based on the requested backup version. In the case of a disaster to the DSC repository, exporting and then importing job metadata enables job migration and restoration to a different DSA environment.

The data must be exported in the following order:
  1. Targets
  2. Job definition
  3. Save sets

Syntax

export_job_metadata -n|-name Name -d|-directory DirectoryPath -v|-backup_version BackupVersion -t|-type Type -u|-user_authentication User

Example

dsc export_job_metadata -n job1 -v latest

Parameters

n|name Name
The name of the job on which to perform the action. Must be unique for each job.
Example:  job1
d|directory DirectoryPath
[Optional] Directory where the files are exported to or imported from.
Example:  var/opt/dsa
v|backup_version BackupVersion
[Optional] Backup version number. Enter latest or 0 for the latest save set.
Example:  latest
t|type Type
[Optional] The type of job metadata. You may enter JOB (for the job definition), SAVESET, or TARGET. If no value is specified, all three types of metadata are included.
Example:  JOB
u|user_authentication User
Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.

Permissions required: User role

Usage Notes

When the export_job_metadata or import_job_metadata command is running, no other operations or commands can run at the same time. In addition, export_job_metadata and import_job_metadata cannot run if an operational job or repository job is running.

XML File Example

This command does not support an XML file.