Restore a Migrated Job | Teradata DSA - 17.20 - Restoring a Migrated Job - BAR - Data Stream Architecture

Teradata® DSA User Guide

Product
BAR
Data Stream Architecture
Release Number
17.20
Release Date
October 2021
Content Type
User Guide
Publication ID
B035-3150-101K
Language
English (United States)
When creating a restore job from the migrated save set, the restore job must specify the target group that was mapped in the source and destination domains.

If the save set is being restored to a database system that is different than the source, set the run_as_copy option to true. The database object must exist on the destination system with perm space allocated before the copy job runs.

  1. Type dsc create_job followed by the parameters, and press Enter.
    Parameter Description
    n|name Name The name of the job on which to perform the action. Must be unique for each job.
    d|description Description A meaningful description of the job. To allow a multiword description, add \" before and after the description string. \"A description of Job 1\"
    t|type Type restore
    run_as_copy true
    b|backup_name BackupName [Optional] An existing backup job name. For restore, analyze_read, and analyze_validate jobs only.
    v|backup_version BackupVersion

    [Optional] Backup version number. For restore, analyze_read, and analyze_validate jobs only. Enter latest or 0 for the latest save set.

    f|file filename The full file path and file name of the file containing the necessary parameters to create the job. If the same parameters are provided both in the file and on the command line, Teradata DSA uses the values specified in the command line.
    u|user_authentication User Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.
  2. Type the user name and password, and press Enter.
  3. Type dsc run_job and press Enter.

Restoring a Migrated Job

The following example restores a migrated job called SDBA_Weekly.

Note the following restrictions on job options:
  • If single_object_locking is true and online is true, the backup job fails.
  • If single_object_locking is true and data_phase is DICTIONARY, the backup job fails.
  • If single_object_locking is true, a DBC-only backup job is rejected.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dscCreateJob xmlns="http://schemas.teradata.com/v2012/DSC">
    <job_instance>
        <job_name>rstr_air_job</job_name>
        <job_description></job_description>
        <job_type>RESTORE</job_type>
        <job_owner>dscuser</job_owner>
        <job_state>ACTIVE</job_state>
        <auto_retire>false</auto_retire>
        <backup_name>SDBA_Weekly</backup_name>
        <backup_version>0</backup_version>
        <all_backup_objects>true</all_backup_objects>
    </job_instance>
    <source_media>tg_cbar3</source_media>
    <target_tdpid>recall</target_tdpid>
    <job_options>
        <enable_temperature_override>false</enable_temperature_override>
        <temperature_override>DEFAULT</temperature_override>
        <block_level_compression>DEFAULT</block_level_compression>
        <disable_fallback>false</disable_fallback>
        <query_band></query_band>
        <dsmain_logging_level>Error</dsmain_logging_level>
   	<reblock>false</reblock>
        <run_as_copy>true</run_as_copy>
    </job_options>
</dscCreateJob>