Protecting the DSC Repository - Data Stream Architecture

Teradata Data Stream Architecture (DSA) User Guide

Product
Data Stream Architecture
Release Number
16.00
Published
November 2016
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
zgh1474305420348.ditamap
dita:ditavalPath
3150_DSA_UG_1600.ditaval.ditaval
dita:id
B035-3150
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. Therefore it is critical to protect the data in the DSC repository. Without the DSC repository, database backup data sets cannot be restored.

The DSC repository should be backed up every day after all of the daily database backup jobs have completed. The DSC backup data set must also be included in the disaster recovery and data protection policies of the organization. This includes any vaulting or off-site storage of backup datasets.

  1. Configure a target group for your DSC repository backup and schedule a DSC repository backup using one of the following methods:
  2. Type dsc export_config -t SYSTEM -n dscnode_Repository_name -f repository_config_system.xml on the DSC server.
    Keep repository_config_system.xml in a safe, known location to be used in case of a disaster.
  3. Type dsc export_repository_backup_config -f export_repository_backup_config.xml .
    Keep export_repository_backup_config.xml in a safe, known location to be imported back into DSC in case of a disaster.
  4. Run a DSC repository backup.