Back Up DSC Repository/Configuration Before Upgrading | Teradata DSA | DSE | DSU - Backing Up DSC Repository and Configuration Before Upgrading - BAR - Data Stream Architecture - Data Stream Utility

Teradata® DSA - DSU Installation, Configuration, and Upgrade Guide

Product
BAR
Data Stream Architecture
Data Stream Utility
Release Number
17.00
Published
August 2020
Language
English (United States)
Last Update
2020-08-31
dita:mapPath
ypy1575933475765.ditamap
dita:ditavalPath
itl1576617711059.ditaval
dita:id
B035-3153
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities

The DSC repository stores all DSA data, including configuration definitions and settings, job definitions, job status, and job history. Protecting the data in the DSC repository is critical. Without the DSC repository, database backup data sets cannot be restored.

It is very important to save copies of the following configuration information before performing an upgrade.
  • The backup repository configuration
  • The information required by the /tmp/dsainputs template if you are using PUT
Most of this information is in the properties files saved in /etc/opt/teradata/dsa.
Important: If you change the DSC name during the upgrade you must repeat the repository backup when you are done.

Use the following procedure to back up the DSC repository.

  1. Run the config_repository_backup command followed by the parameters to configure a target group for the DSC repository backup and schedule a DSC repository backup.
    Parameter Description
    f|file filename The full path and name of the file containing the necessary configuration parameters.
    u|user_authentication User Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.
    Sample XML file:
    <dscRepositoryBackup dscVersion="dscVersion1" xmlns="http://schemas.teradata.com/v2012/DSC">
       <!-- 'target_name' - Required, max 32 characters -->
       <target_name>SampleBackupRepoTargetGroup</target_name>
    
       <!-- 'frequency_value' - Required, Value between 1-4, Defaults to 1 -->
       <frequency_value>1</frequency_value>
    
       <!-- 'day_selection' - Required, accepted values: Su, Mo, Tu, We, Th, Fr, Sa -->
       <day_selection>Sa,Su</day_selection>
    
       <!-- 'start_time' - Required, Max characters 5, Values 1:00-12:00 -->
       <start_time>12:00</start_time>
    
       <!-- 'start_am_pm' - Required, accepted values: AM/PM -->
       <start_am_pm>AM</start_am_pm>
    
    </dscRepositoryBackup>
    
  2. Type dsc export_repository_backup_config -f export_repository_backup_config.xml .
    You need to run export_repository_backup_config every time the configuration for repository backup is changed.
    Keep export_repository_backup_config.xml in a safe, known location to be imported back into DSC in case of a disaster.
  3. Type dsc run_repository_job -t backup, and press Enter to run a DSC repository backup.
    The run_repository_job command can only be initiated if no operational jobs are running.